Кинотеатр-ОНЛАЙН:Фильмы и сериалы Онлайн ,ВИДЕО ОНЛАЙН,СЕРИАЛЫ ОНЛАЙН,КЛИПЫ ОНЛАЙН,ТВ ОНЛАЙН,ИГРЫ ОНЛАЙН ...

limon-online.ru
  • Domain Name
    limon-online.ru
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #38757
  • Page Size
    117.4 KB
  • Ip Address
    193.109.247.156
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    5 GIF, 18 JPG, 19 PNG

Website Meta Analysis

  • Title
    Фильмы онлайн - Главная страница
  • Meta Keyword
    Смотреть фильмы онлайн,DivX фильмы,качество,фильмы онлайн,filmi online,сериалы онлайн,комедии,боевик,триллер,драма,мелодрама,ужасы,фантистика,приключения,документальные,видео онлайн,клипы онлайн,Movies Online,Фильмы он-лайн,ПОРНО ОНЛАЙН,СЕКС ОНЛАЙН,онлайн фильмы,бесплатно смотреть
  • Meta Description
    Кинотеатр-ОНЛАЙН:Фильмы и сериалы Онлайн ,ВИДЕО ОНЛАЙН,СЕРИАЛЫ ОНЛАЙН,КЛИПЫ ОНЛАЙН,ТВ ОНЛАЙН,ИГРЫ ОНЛАЙН

Technical Analysis

  • Webserver
    uServ/3.2.2
  • Ip Address
    193.109.247.156
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from limon-online.ru.

HTML Analysis

  • server: uServ/3.2.2
  • date: Sun, 10 Mar 2013 22:53:21 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
% By submitting a query to RIPN's Whois Service
% you agree to abide by the following terms of use:
% http://www.ripn.net/about/servpol.html#3.2 (in Russian)
% http://www.ripn.net/about/en/servpol.html#3.2 (in English).

domain: LIMON-ONLINE.RU
nserver: ns1.ucoz.ru.
nserver: ns2.ucoz.ru.
state: REGISTERED, DELEGATED, UNVERIFIED
person: Private Person
registrar: RU-CENTER-REG-RIPN
admin-contact: https://www.nic.ru/whois
created: 2008.01.20
paid-till: 2013.01.20
free-date: 2013.02.20
source: TCI

Last updated on 2012.08.28 10:01:36 MSK

IP 193.109.247.156 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 193.109.247.156

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 91 Errors
  • 26 Warnings
Ratio Text/Html
  • 0.41821856623609943
Message Error
  • Error Line 2, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <html><head>

    The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

  • Error Line 14, Column 7: required attribute "TYPE" not specified
    <style>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 18, Column 81: NET-enabling start-tag requires SHORTTAG YES
    …ink type="text/css" rel="StyleSheet" href="http://s46.ucoz.net/src/base.css" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 19, Column 82: NET-enabling start-tag requires SHORTTAG YES
    …k type="text/css" rel="StyleSheet" href="http://s46.ucoz.net/src/layer1.css" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 19, Column 82: document type does not allow element "LINK" here
    …k type="text/css" rel="StyleSheet" href="http://s46.ucoz.net/src/layer1.css" />

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 21, Column 95: NET-enabling start-tag requires SHORTTAG YES
    …css" rel="stylesheet" type="text/css" /><script type="text/javascript" src="ht…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 21, Column 95: document type does not allow element "LINK" here
    …css" rel="stylesheet" type="text/css" /><script type="text/javascript" src="ht…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 22, Column 103: document type does not allow element "STYLE" here
    ….js?2"></script><style type="text/css">.UhideBlock {display:none}</style><scri…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 23, Column 7: end tag for element "HEAD" which is not open
    </head>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 25, Column 349: document type does not allow element "BODY" here
    …ackground-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;"> 

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 29, Column 17: there is no attribute "BACKGROUND"
     <td background="http://limon-online.ru/images/1.gif" height="87" width="100%">

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 36, Column 83: required attribute "ALT" not specified
    …="http://limon-online.ru/images/2.gif" border="0" height="87" width="460"></td>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 41, Column 83: required attribute "ALT" not specified
    …="http://limon-online.ru/images/4.gif" border="0" height="77" width="460"></td>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 53, Column 83: required attribute "ALT" not specified
    …="http://limon-online.ru/images/6.gif" border="0" height="40" width="460"></td>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 84, Column 10: element "NOINDEX" undefined
     <noindex><a target="_blank" href="http://www.adobe.com/shockwave/download/down…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 84, Column 298: required attribute "ALT" not specified
    …=BPCLE"> <img src="/img/e04c0dd27647.gif"> <br>Adobe Flash Player </a><br><br> 

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 85, Column 313: required attribute "ALT" not specified
    …p://limon-online.ru/images/mozzzilllaaaa.PNG"><br>MoZiLLa FiReFoX</a></noindex>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 111, Column 17: there is no attribute "SIZE"
    <g:plusone size="tall"></g:plusone>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 111, Column 23: element "G:PLUSONE" undefined
    <g:plusone size="tall"></g:plusone>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 131, Column 66: element "NOINDEX" undefined
    …ent" valign="top" width="200"><noindex><div align="center"><div id="bn_ENHrfWs…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 144, Column 43: element "NOINDEX" undefined
     <div id="yoblako" align="center"><noindex>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 192, Column 37: end tag for element "A" which is not open
     + '\'>' + eTagz[i].innerHTML + '</a>'; 

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 194, Column 31: end tag for element "TAGS" which is not open
     flashvars.tagcloud += '</tags>'; 

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 215, Column 86: element "NOINDEX" undefined
    …nt" valign="top" width="200"><div align="center"><noindex></noindex></div></td>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 233, Column 66: element "NOINDEX" undefined
    …ent" valign="top" width="200"><noindex><div align="center"><div id="bn_UTS4dP2…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 243, Column 28: element "NOINDEX" undefined
     <p align="center"><noindex>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 252, Column 66: element "NOINDEX" undefined
    …ent" valign="top" width="200"><noindex><div align="center"><script type="text/…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 266, Column 73: element "NOINDEX" undefined
    …valign="top" width="100%"><br><noindex><div align="center"><script type="text/…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 266, Column 169: cannot generate system identifier for general entity "f"
    …ript" src="http://c.am11.ru/code/bn/js.php?u=3388&f=1"></script></div><br></td>

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 266, Column 169: general entity "f" not defined and no default entity
    …ript" src="http://c.am11.ru/code/bn/js.php?u=3388&f=1"></script></div><br></td>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Error Line 266, Column 170: reference to entity "f" for which no system identifier could be generated
    …ript" src="http://c.am11.ru/code/bn/js.php?u=3388&f=1"></script></div><br></td>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 266, Column 168: entity was defined here
    …ript" src="http://c.am11.ru/code/bn/js.php?u=3388&f=1"></script></div><br></td>
  • Error Line 269, Column 34: element "NOINDEX" undefined
     <div align="center"><br><noindex><span style="font-size: 12pt;"><b></b></span>…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 269, Column 556: NET-enabling start-tag requires SHORTTAG YES
    …f" border="0" width="220" height="19" /></div></div><script type="text/javascr…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 269, Column 1147: duplicate specification of attribute "ALIGN"
    …align="right" class="catPages1" align="center" style="clear:both;" id="pagesBl…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 278, Column 639: syntax of attribute value does not conform to declared value
    …line.ru/_nw/131/s93218851.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 278, Column 639: value of attribute "ALIGN" cannot be ""; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"
    …line.ru/_nw/131/s93218851.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 278, Column 641: NET-enabling start-tag requires SHORTTAG YES
    …ne.ru/_nw/131/s93218851.jpg" align="" /></a><!--IMG1--><br></td><td style="bor…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 294, Column 56: required attribute "ALT" not specified
    |<img src="http://limon-online.ru/images/reiting/0.png">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 309, Column 639: syntax of attribute value does not conform to declared value
    …line.ru/_nw/131/s23684374.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 309, Column 639: value of attribute "ALIGN" cannot be ""; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"
    …line.ru/_nw/131/s23684374.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 309, Column 641: NET-enabling start-tag requires SHORTTAG YES
    …ne.ru/_nw/131/s23684374.jpg" align="" /></a><!--IMG1--><br></td><td style="bor…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 324, Column 56: required attribute "ALT" not specified
    |<img src="http://limon-online.ru/images/reiting/0.png">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 339, Column 639: syntax of attribute value does not conform to declared value
    …line.ru/_nw/131/s51752995.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 339, Column 639: value of attribute "ALIGN" cannot be ""; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"
    …line.ru/_nw/131/s51752995.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 339, Column 641: NET-enabling start-tag requires SHORTTAG YES
    …ne.ru/_nw/131/s51752995.jpg" align="" /></a><!--IMG1--><br></td><td style="bor…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 350, Column 56: required attribute "ALT" not specified
    |<img src="http://limon-online.ru/images/reiting/0.png">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 365, Column 639: syntax of attribute value does not conform to declared value
    …line.ru/_nw/131/s77603837.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 365, Column 639: value of attribute "ALIGN" cannot be ""; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"
    …line.ru/_nw/131/s77603837.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 365, Column 641: NET-enabling start-tag requires SHORTTAG YES
    …ne.ru/_nw/131/s77603837.jpg" align="" /></a><!--IMG1--><br></td><td style="bor…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 371, Column 56: required attribute "ALT" not specified
    |<img src="http://limon-online.ru/images/reiting/0.png">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 386, Column 499: syntax of attribute value does not conform to declared value
    …nline.ru/_nw/131/10140339.jpg" align="" /><!--IMG1--><br></td><td style="borde…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 386, Column 499: value of attribute "ALIGN" cannot be ""; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"
    …nline.ru/_nw/131/10140339.jpg" align="" /><!--IMG1--><br></td><td style="borde…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 386, Column 501: NET-enabling start-tag requires SHORTTAG YES
    …ine.ru/_nw/131/10140339.jpg" align="" /><!--IMG1--><br></td><td style="border:…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 398, Column 56: required attribute "ALT" not specified
    |<img src="http://limon-online.ru/images/reiting/0.png">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 413, Column 639: syntax of attribute value does not conform to declared value
    …line.ru/_nw/131/s26393072.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 413, Column 639: value of attribute "ALIGN" cannot be ""; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"
    …line.ru/_nw/131/s26393072.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 413, Column 641: NET-enabling start-tag requires SHORTTAG YES
    …ne.ru/_nw/131/s26393072.jpg" align="" /></a><!--IMG1--><br></td><td style="bor…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 425, Column 56: required attribute "ALT" not specified
    |<img src="http://limon-online.ru/images/reiting/4.png">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 440, Column 639: syntax of attribute value does not conform to declared value
    …line.ru/_nw/130/s03424044.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 440, Column 639: value of attribute "ALIGN" cannot be ""; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"
    …line.ru/_nw/130/s03424044.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 440, Column 641: NET-enabling start-tag requires SHORTTAG YES
    …ne.ru/_nw/130/s03424044.jpg" align="" /></a><!--IMG1--><br></td><td style="bor…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 452, Column 56: required attribute "ALT" not specified
    |<img src="http://limon-online.ru/images/reiting/0.png">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 467, Column 639: syntax of attribute value does not conform to declared value
    …line.ru/_nw/131/s71940836.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 467, Column 639: value of attribute "ALIGN" cannot be ""; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"
    …line.ru/_nw/131/s71940836.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 467, Column 641: NET-enabling start-tag requires SHORTTAG YES
    …ne.ru/_nw/131/s71940836.jpg" align="" /></a><!--IMG1--><br></td><td style="bor…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 484, Column 56: required attribute "ALT" not specified
    |<img src="http://limon-online.ru/images/reiting/0.png">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 499, Column 639: syntax of attribute value does not conform to declared value
    …line.ru/_nw/131/s24899898.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 499, Column 639: value of attribute "ALIGN" cannot be ""; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"
    …line.ru/_nw/131/s24899898.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 499, Column 641: NET-enabling start-tag requires SHORTTAG YES
    …ne.ru/_nw/131/s24899898.jpg" align="" /></a><!--IMG1--><br></td><td style="bor…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 513, Column 56: required attribute "ALT" not specified
    |<img src="http://limon-online.ru/images/reiting/0.png">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 528, Column 639: syntax of attribute value does not conform to declared value
    …line.ru/_nw/130/s38906973.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 528, Column 639: value of attribute "ALIGN" cannot be ""; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"
    …line.ru/_nw/130/s38906973.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 528, Column 641: NET-enabling start-tag requires SHORTTAG YES
    …ne.ru/_nw/130/s38906973.jpg" align="" /></a><!--IMG1--><br></td><td style="bor…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 540, Column 56: required attribute "ALT" not specified
    |<img src="http://limon-online.ru/images/reiting/0.png">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 555, Column 639: syntax of attribute value does not conform to declared value
    …line.ru/_nw/131/s39500312.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 555, Column 639: value of attribute "ALIGN" cannot be ""; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"
    …line.ru/_nw/131/s39500312.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 555, Column 641: NET-enabling start-tag requires SHORTTAG YES
    …ne.ru/_nw/131/s39500312.jpg" align="" /></a><!--IMG1--><br></td><td style="bor…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 573, Column 56: required attribute "ALT" not specified
    |<img src="http://limon-online.ru/images/reiting/0.png">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 588, Column 639: syntax of attribute value does not conform to declared value
    …line.ru/_nw/130/s48801874.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 588, Column 639: value of attribute "ALIGN" cannot be ""; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"
    …line.ru/_nw/130/s48801874.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 588, Column 641: NET-enabling start-tag requires SHORTTAG YES
    …ne.ru/_nw/130/s48801874.jpg" align="" /></a><!--IMG1--><br></td><td style="bor…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 604, Column 56: required attribute "ALT" not specified
    |<img src="http://limon-online.ru/images/reiting/3.png">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 619, Column 639: syntax of attribute value does not conform to declared value
    …line.ru/_nw/128/s86536746.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 619, Column 639: value of attribute "ALIGN" cannot be ""; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"
    …line.ru/_nw/128/s86536746.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 619, Column 641: NET-enabling start-tag requires SHORTTAG YES
    …ne.ru/_nw/128/s86536746.jpg" align="" /></a><!--IMG1--><br></td><td style="bor…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 634, Column 56: required attribute "ALT" not specified
    |<img src="http://limon-online.ru/images/reiting/4.png">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 649, Column 639: syntax of attribute value does not conform to declared value
    …line.ru/_nw/131/s04144901.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 649, Column 639: value of attribute "ALIGN" cannot be ""; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"
    …line.ru/_nw/131/s04144901.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 649, Column 641: NET-enabling start-tag requires SHORTTAG YES
    …ne.ru/_nw/131/s04144901.jpg" align="" /></a><!--IMG1--><br></td><td style="bor…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 658, Column 56: required attribute "ALT" not specified
    |<img src="http://limon-online.ru/images/reiting/0.png">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 673, Column 639: syntax of attribute value does not conform to declared value
    …line.ru/_nw/131/s05627205.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 673, Column 639: value of attribute "ALIGN" cannot be ""; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"
    …line.ru/_nw/131/s05627205.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 673, Column 641: NET-enabling start-tag requires SHORTTAG YES
    …ne.ru/_nw/131/s05627205.jpg" align="" /></a><!--IMG1--><br></td><td style="bor…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 689, Column 56: required attribute "ALT" not specified
    |<img src="http://limon-online.ru/images/reiting/3.png">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 704, Column 639: syntax of attribute value does not conform to declared value
    …line.ru/_nw/131/s53584535.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 704, Column 639: value of attribute "ALIGN" cannot be ""; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"
    …line.ru/_nw/131/s53584535.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 704, Column 641: NET-enabling start-tag requires SHORTTAG YES
    …ne.ru/_nw/131/s53584535.jpg" align="" /></a><!--IMG1--><br></td><td style="bor…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 717, Column 56: required attribute "ALT" not specified
    |<img src="http://limon-online.ru/images/reiting/0.png">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 732, Column 637: syntax of attribute value does not conform to declared value
    …nline.ru/_nw/74/s86643701.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 732, Column 637: value of attribute "ALIGN" cannot be ""; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"
    …nline.ru/_nw/74/s86643701.jpg" align="" /></a><!--IMG1--><br></td><td style="b…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 732, Column 639: NET-enabling start-tag requires SHORTTAG YES
    …ine.ru/_nw/74/s86643701.jpg" align="" /></a><!--IMG1--><br></td><td style="bor…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 738, Column 56: required attribute "ALT" not specified
    |<img src="http://limon-online.ru/images/reiting/5.png">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 786, Column 95: there is no attribute "ENCODING"
    …t/js/l/i/limon-online.ru.i3.js" encoding="utf-8"></script><!--/U1ADVR1Z--></td>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 794, Column 9: element "NOINDEX" undefined
    <noindex>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 808, Column 30: required attribute "TYPE" not specified
    <script language="Javascript">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 815, Column 223: delimiter "'" invalid: only S separators and TAGC allowed here
    …tizw+'&nobg='+nobg+'&vref='+vref+'&vopis='+vopis+'&ref='+ref+'"></scr'+'ipt>');
  • Error Line 815, Column 223: end tag for element "SCR" which is not open
    …tizw+'&nobg='+nobg+'&vref='+vref+'&vopis='+vopis+'&ref='+ref+'"></scr'+'ipt>');

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 820, Column 30: required attribute "TYPE" not specified
    <script language="Javascript">

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 827, Column 223: delimiter "'" invalid: only S separators and TAGC allowed here
    …tizw+'&nobg='+nobg+'&vref='+vref+'&vopis='+vopis+'&ref='+ref+'"></scr'+'ipt>');
  • Error Line 827, Column 223: end tag for element "SCR" which is not open
    …tizw+'&nobg='+nobg+'&vref='+vref+'&vopis='+vopis+'&ref='+ref+'"></scr'+'ipt>');

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

Visitor Analysis

Daily Visitor
  • 3.850 visits
Daily Visitor