С Audiko очень просто нарезать мелодии на телефон из любимых песен! ...

audiko.ru
  • Domain Name
    audiko.ru
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #112729
  • Page Size
    43.3 KB
  • Ip Address
    74.86.2.194
  • Heading
    H1: 1, H2: 1, H3: 6, H4: 3, H5: 0, H6: 0
  • Images
    0 GIF, 13 JPG, 2 PNG

Website Meta Analysis

  • Title
    Скачать бесплатные мелодии для телефона и iPhone - Audiko
  • Meta Keyword
    Ringtone, realtone, iphone, blackberry, cell, mobile, mp3, SMS, text, custom ringtones iphone, ringtone maker, free ringtone, download, ringtones for us cellular, virgin mobile ringtones, cricket ringtones, tmobile ringtones, ringtones cingular
  • Meta Description
    С Audiko очень просто нарезать мелодии на телефон из любимых песен!

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    74.86.2.194
  • Domain Age
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from audiko.ru.

HTML Analysis

  • server: nginx
  • date: Fri, 01 Mar 2013 22:42:43 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • vary: Accept-Encoding
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for audiko.ru

DNS Analysis


DNS servers
ns2.9o8.com [64.237.45.34]
ns1.9o8.com [64.94.136.11]


DNS Records

Answer records
audiko.ru A 74.86.2.194 3600s
audiko.ru NS  dns2.nettica.com 3600s
audiko.ru NS  dns3.nettica.com 3600s
audiko.ru NS  dns4.nettica.com 3600s
audiko.ru NS  dns5.nettica.com 3600s
audiko.ru NS  dns1.nettica.com 3600s
audiko.ru SOA
server: dns1.nettica.com
email: hostmaster@nettica.com
serial: 33
refresh: 21600
retry: 7200
expire: 604800
minimum ttl: 3600
3600s

Authority records

Additional records
dns2.nettica.com A 64.237.45.34 43200s
dns3.nettica.com A 64.94.136.13 43200s
dns4.nettica.com A 69.41.170.223 43200s
dns5.nettica.com A 212.100.247.15 43200s
dns1.nettica.com A 64.94.136.11 43200s

IP 74.86.2.194 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Dallas
  • Continent Code
    75207
  • Latitude
    214
  • Longitude
    623
  • %rwhois V-1.5:003fff:00 rwhois.softlayer.com (by Network Solutions, Inc. V-1.5.9.5)
    network:Class-Name:network
    network:ID:NETBLK-SOFTLAYER.74.86.0.0/19
    network:Auth-Area:74.86.0.0/19
    network:Network-Name:SOFTLAYER-74.86.0.0
    network:IP-Network:74.86.2.192/29
    network:IP-Network-Block:74.86.2.192-74.86.2.199
    network:Organization;I:908
    network:Street-Address:950 Page Mill Road
    network:City:Palo Alto
    network:State:CA
    network:Postal-Code:94304
    network:Country-Code:US
    network:Tech-Contact;I:sysadmins@softlayer.com
    network:Abuse-Contact;I:abuse@audiko.net
    network:Admin-Contact;I:IPADM258-ARIN
    network:Created:2012-04-11 14:04:35
    network:Updated:2012-04-11 14:44:41
    network:Updated-By:ipadmin@softlayer.com

    %ok

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 65 Errors
  • 26 Warnings
Ratio Text/Html
  • 0.684206961939591
Message Error
  • Error Line 2, Column 13: there is no attribute "class"
    <html class="no-js" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">

    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 5, Column 44: there is no attribute "property"
    …                       <meta property="og:image" content="http://css.cdn.audik…

    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 29, Column 49: there is no attribute "sizes"
    …="apple-touch-icon-precomposed" sizes="144x144" href="http://css.cdn.audiko.ne…

    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.

  • Warning Line 140, Column 71: cannot generate system identifier for general entity "zid"
    …rc="http://g.adspeed.net/ad.php?do=js&zid=23804&wd=-1&ht=-1&target=_top"></scr…

    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 140, Column 71: general entity "zid" not defined and no default entity
    …rc="http://g.adspeed.net/ad.php?do=js&zid=23804&wd=-1&ht=-1&target=_top"></scr…

    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.

  • Warning Line 140, Column 74: reference not terminated by REFC delimiter
    …"http://g.adspeed.net/ad.php?do=js&zid=23804&wd=-1&ht=-1&target=_top"></script…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 140, Column 74: reference to external entity in attribute value
    …"http://g.adspeed.net/ad.php?do=js&zid=23804&wd=-1&ht=-1&target=_top"></script…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 140, Column 74: reference to entity "zid" for which no system identifier could be generated
    …"http://g.adspeed.net/ad.php?do=js&zid=23804&wd=-1&ht=-1&target=_top"></script…

    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 140, Column 70: entity was defined here
    …src="http://g.adspeed.net/ad.php?do=js&zid=23804&wd=-1&ht=-1&target=_top"></sc…
  • Warning Line 140, Column 81: cannot generate system identifier for general entity "wd"
    …"http://g.adspeed.net/ad.php?do=js&zid=23804&wd=-1&ht=-1&target=_top"></script>

    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 140, Column 81: general entity "wd" not defined and no default entity
    …"http://g.adspeed.net/ad.php?do=js&zid=23804&wd=-1&ht=-1&target=_top"></script>

    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.

  • Warning Line 140, Column 83: reference not terminated by REFC delimiter
    …"http://g.adspeed.net/ad.php?do=js&zid=23804&wd=-1&ht=-1&target=_top"></script>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 140, Column 83: reference to external entity in attribute value
    …"http://g.adspeed.net/ad.php?do=js&zid=23804&wd=-1&ht=-1&target=_top"></script>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 140, Column 83: reference to entity "wd" for which no system identifier could be generated
    …"http://g.adspeed.net/ad.php?do=js&zid=23804&wd=-1&ht=-1&target=_top"></script>

    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 140, Column 80: entity was defined here
    …"http://g.adspeed.net/ad.php?do=js&zid=23804&wd=-1&ht=-1&target=_top"></script>
  • Warning Line 140, Column 87: cannot generate system identifier for general entity "ht"
    …"http://g.adspeed.net/ad.php?do=js&zid=23804&wd=-1&ht=-1&target=_top"></script>

    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 140, Column 87: general entity "ht" not defined and no default entity
    …"http://g.adspeed.net/ad.php?do=js&zid=23804&wd=-1&ht=-1&target=_top"></script>

    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.

  • Warning Line 140, Column 89: reference not terminated by REFC delimiter
    …"http://g.adspeed.net/ad.php?do=js&zid=23804&wd=-1&ht=-1&target=_top"></script>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 140, Column 89: reference to external entity in attribute value
    …"http://g.adspeed.net/ad.php?do=js&zid=23804&wd=-1&ht=-1&target=_top"></script>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 140, Column 89: reference to entity "ht" for which no system identifier could be generated
    …"http://g.adspeed.net/ad.php?do=js&zid=23804&wd=-1&ht=-1&target=_top"></script>

    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 140, Column 86: entity was defined here
    …"http://g.adspeed.net/ad.php?do=js&zid=23804&wd=-1&ht=-1&target=_top"></script>
  • Warning Line 140, Column 93: cannot generate system identifier for general entity "target"
    …"http://g.adspeed.net/ad.php?do=js&zid=23804&wd=-1&ht=-1&target=_top"></script>

    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 140, Column 93: general entity "target" not defined and no default entity
    …"http://g.adspeed.net/ad.php?do=js&zid=23804&wd=-1&ht=-1&target=_top"></script>

    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.

  • Warning Line 140, Column 99: reference not terminated by REFC delimiter
    …"http://g.adspeed.net/ad.php?do=js&zid=23804&wd=-1&ht=-1&target=_top"></script>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 140, Column 99: reference to external entity in attribute value
    …"http://g.adspeed.net/ad.php?do=js&zid=23804&wd=-1&ht=-1&target=_top"></script>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 140, Column 99: reference to entity "target" for which no system identifier could be generated
    …"http://g.adspeed.net/ad.php?do=js&zid=23804&wd=-1&ht=-1&target=_top"></script>

    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 140, Column 92: entity was defined here
    …"http://g.adspeed.net/ad.php?do=js&zid=23804&wd=-1&ht=-1&target=_top"></script>
  • Error Line 154, Column 109: ID "back_auth_url" already defined
    …>&nbsp;или&nbsp;<a rel="nofollow" id="back_auth_url" href="/user/login?back=%2…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 147, Column 110: ID "back_auth_url" first defined here
    …>&nbsp;или&nbsp;<a rel="nofollow" id="back_auth_url" href="/user/login?back=%2…
  • Error Line 169, Column 21: there is no attribute "size"
    				<g:plusone size="medium" href="http://audiko.net"></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 169, Column 35: there is no attribute "href"
    				<g:plusone size="medium" href="http://audiko.net"></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 169, Column 54: element "g:plusone" undefined
    				<g:plusone size="medium" href="http://audiko.net"></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 183, Column 110: document type does not allow element "input" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
    …or:#495b6a" name="q" value="Найти рингтоны" class="search_input shadow-inner"/>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 184, Column 45: document type does not allow element "button" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
    …button class="button light" type="submit"><span>Искать в Audiko</span></button>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 185, Column 64: document type does not allow element "a" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "pre", "address", "fieldset" start-tag
    		<a href="?stype=google" class="search__switch" rel="nofollow"></a>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 190, Column 39: there is no attribute "results"
    		<input type="text" value="" results="10" size="45" name="q" id="q" autocomple…

    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 190, Column 83: there is no attribute "autocomplete"
    …ize="45" name="q" id="q" autocomplete="off" class="search_input shadow-inner" …

    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 190, Column 134: there is no attribute "spellcheck"
    …="q" autocomplete="off" class="search_input shadow-inner" spellcheck="false" />

    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 190, Column 143: document type does not allow element "input" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
    …="q" autocomplete="off" class="search_input shadow-inner" spellcheck="false" />

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 191, Column 45: document type does not allow element "button" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
    …button class="button light" type="submit"><span>Искать в Google</span></button>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 192, Column 64: document type does not allow element "a" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "pre", "address", "fieldset" start-tag
    		<a href="?stype=native" class="search__switch" rel="nofollow"></a>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 195, Column 84: document type does not allow element "input" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
    …type="hidden" name="cx" value="partner-pub-0282315043770273:w4zt1-lya5u" />    

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 196, Column 53: document type does not allow element "input" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
    		<input type="hidden" name="cof" value="FORID:10" />

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 197, Column 49: document type does not allow element "input" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
    		<input type="hidden" name="ie" value="UTF-8" />

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 304, Column 125: end tag for "param" omitted, but OMITTAG NO was specified
    …"movie" value="http://st.audiko.net/static/flash/audiko_mp3_widget.v12573.swf">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 304, Column 34: start tag was here
    			                						        <param name="movie" value="http://st.audiko.ne…
  • Error Line 305, Column 62: end tag for "param" omitted, but OMITTAG NO was specified
    						        <param name="allowScriptAccess" value="always">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 305, Column 15: start tag was here
    						        <param name="allowScriptAccess" value="always">
  • Error Line 306, Column 59: end tag for "param" omitted, but OMITTAG NO was specified
    						        <param name="allowFullScreen" value="false">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 306, Column 15: start tag was here
    						        <param name="allowFullScreen" value="false">
  • Warning Line 307, Column 109: cannot generate system identifier for general entity "sid"
    …net/static/flashvars/lang.ru.xml?v=w5&sid=6btoar0c5asn95lc4s7lkrgge2&domain=ht…

    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 307, Column 109: general entity "sid" not defined and no default entity
    …net/static/flashvars/lang.ru.xml?v=w5&sid=6btoar0c5asn95lc4s7lkrgge2&domain=ht…

    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.

  • Warning Line 307, Column 112: reference not terminated by REFC delimiter
    …/static/flashvars/lang.ru.xml?v=w5&sid=6btoar0c5asn95lc4s7lkrgge2&domain=http:…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 307, Column 112: reference to external entity in attribute value
    …/static/flashvars/lang.ru.xml?v=w5&sid=6btoar0c5asn95lc4s7lkrgge2&domain=http:…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 307, Column 112: reference to entity "sid" for which no system identifier could be generated
    …/static/flashvars/lang.ru.xml?v=w5&sid=6btoar0c5asn95lc4s7lkrgge2&domain=http:…

    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 307, Column 108: entity was defined here
    ….net/static/flashvars/lang.ru.xml?v=w5&sid=6btoar0c5asn95lc4s7lkrgge2&domain=h…
  • Warning Line 307, Column 140: cannot generate system identifier for general entity "domain"
    …s/lang.ru.xml?v=w5&sid=6btoar0c5asn95lc4s7lkrgge2&domain=http://s2.audiko.net">

    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 307, Column 140: general entity "domain" not defined and no default entity
    …s/lang.ru.xml?v=w5&sid=6btoar0c5asn95lc4s7lkrgge2&domain=http://s2.audiko.net">

    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.

  • Warning Line 307, Column 146: reference not terminated by REFC delimiter
    …s/lang.ru.xml?v=w5&sid=6btoar0c5asn95lc4s7lkrgge2&domain=http://s2.audiko.net">

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 307, Column 146: reference to external entity in attribute value
    …s/lang.ru.xml?v=w5&sid=6btoar0c5asn95lc4s7lkrgge2&domain=http://s2.audiko.net">

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 307, Column 146: reference to entity "domain" for which no system identifier could be generated
    …s/lang.ru.xml?v=w5&sid=6btoar0c5asn95lc4s7lkrgge2&domain=http://s2.audiko.net">

    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 307, Column 139: entity was defined here
    …s/lang.ru.xml?v=w5&sid=6btoar0c5asn95lc4s7lkrgge2&domain=http://s2.audiko.net">
  • Error Line 307, Column 169: end tag for "param" omitted, but OMITTAG NO was specified
    …s/lang.ru.xml?v=w5&sid=6btoar0c5asn95lc4s7lkrgge2&domain=http://s2.audiko.net">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 307, Column 15: start tag was here
    						        <param name="flashvars" value="langxml=http://st.audiko.net/stati…
  • Error Line 308, Column 50: end tag for "param" omitted, but OMITTAG NO was specified
    						        <param name="quality" value="high">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 308, Column 15: start tag was here
    						        <param name="quality" value="high">
  • Error Line 309, Column 50: end tag for "param" omitted, but OMITTAG NO was specified
    						        <param name="wmode" value="opaque">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 309, Column 15: start tag was here
    						        <param name="wmode" value="opaque">
  • Error Line 310, Column 46: end tag for "param" omitted, but OMITTAG NO was specified
    						        <param name="bgcolor" value="">  

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 310, Column 15: start tag was here
    						        <param name="bgcolor" value="">  
  • Error Line 313, Column 26: there is no attribute "id"
    							        <embed id="flash-widget" type="application/x-shockwave-flash" da…

    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 313, Column 46: there is no attribute "type"
    …        <embed id="flash-widget" type="application/x-shockwave-flash" data="ht…

    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 313, Column 83: there is no attribute "data"
    …="application/x-shockwave-flash" data="http://st.audiko.net/static/flash/audik…

    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 313, Column 154: there is no attribute "width"
    ….audiko.net/static/flash/audiko_mp3_widget.v12573.swf" width="820" height="280"

    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 313, Column 167: there is no attribute "height"
    ….audiko.net/static/flash/audiko_mp3_widget.v12573.swf" width="820" height="280"

    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 314, Column 21: there is no attribute "src"
    								        src="http://st.audiko.net/static/flash/audiko_mp3_widget.v12573…

    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 315, Column 39: there is no attribute "allowScriptAccess"
    		    					         allowScriptAccess="always" 

    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 316, Column 37: there is no attribute "allowFullScreen"
    		    					         allowFullScreen="false" 

    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 317, Column 31: there is no attribute "flashvars"
    		    					         flashvars="langxml=http://st.audiko.net/static/flashvars/la…

    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.

  • Warning Line 317, Column 98: reference not terminated by REFC delimiter
    …/static/flashvars/lang.ru.xml?v=w5&sid=6btoar0c5asn95lc4s7lkrgge2&domain=http:…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 317, Column 98: reference to external entity in attribute value
    …/static/flashvars/lang.ru.xml?v=w5&sid=6btoar0c5asn95lc4s7lkrgge2&domain=http:…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 317, Column 98: reference to entity "sid" for which no system identifier could be generated
    …/static/flashvars/lang.ru.xml?v=w5&sid=6btoar0c5asn95lc4s7lkrgge2&domain=http:…

    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 307, Column 108: entity was defined here
    ….net/static/flashvars/lang.ru.xml?v=w5&sid=6btoar0c5asn95lc4s7lkrgge2&domain=h…
  • Warning Line 317, Column 132: reference not terminated by REFC delimiter
    …s/lang.ru.xml?v=w5&sid=6btoar0c5asn95lc4s7lkrgge2&domain=http://s2.audiko.net" 

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 317, Column 132: reference to external entity in attribute value
    …s/lang.ru.xml?v=w5&sid=6btoar0c5asn95lc4s7lkrgge2&domain=http://s2.audiko.net" 

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 317, Column 132: reference to entity "domain" for which no system identifier could be generated
    …s/lang.ru.xml?v=w5&sid=6btoar0c5asn95lc4s7lkrgge2&domain=http://s2.audiko.net" 

    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 307, Column 139: entity was defined here
    …s/lang.ru.xml?v=w5&sid=6btoar0c5asn95lc4s7lkrgge2&domain=http://s2.audiko.net">
  • Error Line 318, Column 29: there is no attribute "quality"
    		    					         quality="high" 

    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 319, Column 27: there is no attribute "wmode"
    		    					         wmode="opaque"

    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 320, Column 22: element "embed" undefined
    	    					         	/>

    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 354, Column 34: there is no attribute "href"
    			<div class="fb-like-box" href="http://www.facebook.com/Audiko" width="732" h…

    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 354, Column 73: there is no attribute "width"
    …http://www.facebook.com/Audiko" width="732" height="180" show_faces="true" bor…

    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 354, Column 86: there is no attribute "height"
    …cebook.com/Audiko" width="732" height="180" show_faces="true" border_color="#f…

    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 354, Column 103: there is no attribute "show_faces"
    …" width="732" height="180" show_faces="true" border_color="#ffffff" stream="fa…

    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 354, Column 123: there is no attribute "border_color"
    …="180" show_faces="true" border_color="#ffffff" stream="false" header="false">…

    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 354, Column 140: there is no attribute "stream"
    … show_faces="true" border_color="#ffffff" stream="false" header="false"></div>	

    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 354, Column 155: there is no attribute "header"
    … show_faces="true" border_color="#ffffff" stream="false" header="false"></div>	

    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.

  • Warning Line 414, Column 140: character "&" is the first character of a delimiter but occurred as data
    …g=24345464">Thrift Shop (feat. Wanz)</a> Macklemore & Ryan Lewis									</div>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 544, Column 96: required attribute "alt" not specified
    …-icon"><img src="http://css.cdn.audiko.net/static/gfx/flags/32/us.png" /></div>

    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 642, Column 99: character "&" is the first character of a delimiter but occurred as data
    …lake/Suit+%26+Tie+%28feat.+JAY+Z%29?ring=25422348">Suit & Tie (feat. JAY Z)</a>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 760, Column 38: cannot generate system identifier for general entity "B"
    											<a href="/genres/R%26B">R&B</a>

    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 760, Column 38: general entity "B" not defined and no default entity
    											<a href="/genres/R%26B">R&B</a>

    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.

  • Warning Line 760, Column 39: reference not terminated by REFC delimiter
    											<a href="/genres/R%26B">R&B</a>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Error Line 760, Column 39: reference to entity "B" for which no system identifier could be generated
    											<a href="/genres/R%26B">R&B</a>

    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 760, Column 37: entity was defined here
    											<a href="/genres/R%26B">R&B</a>
  • Error Line 916, Column 19: there is no attribute "language"
    	<script language=javascript>eval(unescape('%64%6F%63%75%6D%65%6E%74%2E%77%72%6…

    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 916, Column 19: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<script language=javascript>eval(unescape('%64%6F%63%75%6D%65%6E%74%2E%77%72%6…
  • Error Line 916, Column 29: required attribute "type" not specified
    	<script language=javascript>eval(unescape('%64%6F%63%75%6D%65%6E%74%2E%77%72%6…

    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>.

Visitor Analysis

Daily Visitor
  • 1.050 visits
Daily Visitor