Con QVC guardi, scegli, compri comodamente da casa tua moltissimi prodotti dei più prestigiosi brand nazionali e internazionali. Ogni giorno tante novità tra Bellezza, Moda e Accessori, Gioielli e Bijoux, Casa, Cucina, Elettronica. ...

qvc.it
  • Domain Name
    qvc.it
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #50094
  • Page Size
    142.5 KB
  • Ip Address
    46.38.177.241
  • Heading
    H1: 3, H2: 28, H3: 4, H4: 1, H5: 0, H6: 0
  • Images
    22 GIF, 56 JPG, 36 PNG

Website Meta Analysis

  • Title
    Il canale per chi ama lo shopping - QVC Italia
  • Meta Keyword
    QVC, QVC Italia, eCommerce, Shopping, TV, Il canale per chi ama lo shopping
  • Meta Description
    Con QVC guardi, scegli, compri comodamente da casa tua moltissimi prodotti dei più prestigiosi brand nazionali e internazionali. Ogni giorno tante novità tra Bellezza, Moda e Accessori, Gioielli e Bijoux, Casa, Cucina, Elettronica. Una grande realtà già presente in America, Gran Bretagna, Giappone e Germania.

Technical Analysis

  • Webserver
    Varnish (HIT: 7)
  • Ip Address
    46.38.177.241
  • Domain Age
  • Javascript Library
    jquery, prototype
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from qvc.it.

HTML Analysis

  • x-powered-by: PHP/5.3.13
  • p3p: CP="CAO PSA OUR"
  • x-magento-action: cms_index_index
  • x-magento-lifetime: 86400
  • aoestatic: cache
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-type: text/html; charset=UTF-8
  • x-cacheable: YES
  • cache-control: max-age=60
  • last-modified: Sun, 03 Mar 2013 04:13:13 GMT
  • content-length: 18922
  • date: Sun, 03 Mar 2013 04:23:56 GMT
  • x-varnish: 1542957678 1542956638
  • via: 1.1 varnish
  • connection: keep-alive
  • x-age: 160
  • age: 0
  • x-cache: HIT (7)
  • server: Varnish (HIT: 7)
  • x-google-cache-control: remote-fetch

*********************************************************************
* Please note that the following result could be a subgroup of *
* the data contained in the database. *
* *
* Additional information can be visualized at: *
* http://www.nic.it/cgi-bin/Whois/whois.cgi *
*********************************************************************

Domain: qvc.it
Status: ok
Created: 2003-04-04 00:00:00
Last Update: 2012-03-22 02:54:33
Expire Date: 2013-03-06

Registrant
Name: General Counsel
Organization: QVC Italia S.r.l.
ContactID: 5399274A2B1BA812
Address: Via Guzzina, 18
Brugherio
20861
MB
IT
Created: 2011-06-18 00:04:57
Last Update: 2011-06-18 00:04:57

Admin Contact
Name: General Counsel
Organization: QVC, Inc.
ContactID: 9853154A2AD17325
Address: 1200 Wilson DriveMS 205
West Chester
19380
PA
US
Created: 2011-06-18 00:04:57
Last Update: 2011-06-18 00:04:57

Technical Contacts
Name: Tim McMullen
Organization: QVC, Inc.
ContactID: 3120553A2B0D8327
Address: 1200 Wilson DriveMS 205
West Chester
19380
PA
US
Created: 2011-06-18 00:04:57
Last Update: 2011-06-18 00:04:57

Registrar
Organization: CSC Corporate Domains, Inc.
Name: CSCDOMAINS-REG
Web: https://www.cscglobal.com/global/web/csc/home

Nameservers
ns1.qvc.com
ns2.qvc.com
ns3.qvc.com

IP 46.38.177.241 Analysis

  • Country Code
    GB
  • Country Code3
    GBR
  • Country Name
    United Kingdom
  • City
    EU
  • Continent Code
    54° North
  • Latitude
    2.
  • Longitude
  • No whois ip data for 46.38.177.241

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 112 Errors
  • 19 Warnings
Ratio Text/Html
  • 0.6289178426762987
Message Error
  • Error Line 10, Column 16: there is no attribute "property"
    <meta property="og:site_name" content="QVC Italia" />

    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 166, Column 59: cannot generate system identifier for general entity "appId"
    …  js.src = "//connect.facebook.net/it_IT/all.js#xfbml=1&appId=279754025438357";

    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 166, Column 59: general entity "appId" not defined and no default entity
    …  js.src = "//connect.facebook.net/it_IT/all.js#xfbml=1&appId=279754025438357";

    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 166, Column 64: reference not terminated by REFC delimiter
    …  js.src = "//connect.facebook.net/it_IT/all.js#xfbml=1&appId=279754025438357";

    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 166, Column 64: reference to entity "appId" for which no system identifier could be generated
    …  js.src = "//connect.facebook.net/it_IT/all.js#xfbml=1&appId=279754025438357";

    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 166, Column 58: entity was defined here
    …  js.src = "//connect.facebook.net/it_IT/all.js#xfbml=1&appId=279754025438357";
  • Error Line 172, Column 141: document type does not allow element "img" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "address", "fieldset", "ins", "del" start-tag
    …=0Pwuf1a0mz00Wq" style="display:none" height="1" width="1" alt="" /></noscript>

    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 109: required attribute "alt" not specified
    …vc.it/skin/frontend/enterprise/qvc/images/logo-og.jpg" style="display:none;" />

    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 193, Column 143: required attribute "alt" not specified
    …/qvc/images/il-canale-per-chi-ama-lo-shopping.png" style="margin-top:-27px;" />

    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 194, Column 126: required attribute "alt" not specified
    …ise/qvc/images/phone.png" style="margin-top: -21px; margin-left: 40px;" /></h1>

    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 198, Column 55: there is no attribute "rel"
                            <div class="placeholder"  rel="cart_sidebar">

    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 201, Column 103: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …<div id="up-top-number-in-cart" style="display:inline">0</div></span>)</strong>

    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 213, Column 69: end tag for element "h4" which is not open
    	<li class="last"><a href="/customer/account/create/">Registrati</h4></a></li>

    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 218, Column 122: duplicate specification of attribute "class"
    …solr_pi1[querystring]" value="" class="input-text" />&nbsp;<button type="submi…

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

  • Error Line 228, Column 40: document type does not allow element "ul" here; assuming missing "li" start-tag
    …       <ul class="nav-bottom" id="nav"><li class="level0 nav-1 level-top first…
  • Error Line 228, Column 4409: ID "manufacturer_list" already defined
    …></div><div class="menu-list"><ul id="manufacturer_list"><li class="list-title…

    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 228, Column 1522: ID "manufacturer_list" first defined here
    …></div><div class="menu-list"><ul id="manufacturer_list"><li class="list-title…
  • Error Line 228, Column 8027: ID "manufacturer_list" already defined
    …></div><div class="menu-list"><ul id="manufacturer_list"><li class="list-title…

    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 228, Column 1522: ID "manufacturer_list" first defined here
    …></div><div class="menu-list"><ul id="manufacturer_list"><li class="list-title…
  • Error Line 228, Column 10717: ID "manufacturer_list" already defined
    …></div><div class="menu-list"><ul id="manufacturer_list"><li class="list-title…

    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 228, Column 1522: ID "manufacturer_list" first defined here
    …></div><div class="menu-list"><ul id="manufacturer_list"><li class="list-title…
  • Error Line 228, Column 13665: ID "manufacturer_list" already defined
    …></div><div class="menu-list"><ul id="manufacturer_list"><li class="list-title…

    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 228, Column 1522: ID "manufacturer_list" first defined here
    …></div><div class="menu-list"><ul id="manufacturer_list"><li class="list-title…
  • Error Line 228, Column 15895: ID "manufacturer_list" already defined
    …></div><div class="menu-list"><ul id="manufacturer_list"><li class="list-title…

    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 228, Column 1522: ID "manufacturer_list" first defined here
    …></div><div class="menu-list"><ul id="manufacturer_list"><li class="list-title…
  • Warning Line 236, Column 112: character "&" is the first character of a delimiter but occurred as data
    …www.qvc.it/outlet/moda-e-accessori.html"><span>Moda & Accessori</span></a></li>

    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 251, Column 129: end tag for "li" omitted, but OMITTAG NO was specified
    …"http://www.qvc.it/tv" class="level-top"><span>TV</span></a></li></ul>    </ul>

    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 228, Column 9: start tag was here
            <ul class="nav-bottom" id="nav"><li class="level0 nav-1 level-top first…
  • Error Line 258, Column 20: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id="slideshow">

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

  • Error Line 289, Column 7: document type does not allow element "style" here
    <style>

    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 308, Column 245: required attribute "alt" not specified
    …c.it/skin/frontend/enterprise/qvc/images/prev280.jpg" class="prev" /></a></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>.

  • Error Line 379, Column 10: ID "rating_container" already defined
    <div id="rating_container">

    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 317, Column 10: ID "rating_container" first defined here
    <div id="rating_container">
  • Error Line 441, Column 10: ID "rating_container" already defined
    <div id="rating_container">

    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 317, Column 10: ID "rating_container" first defined here
    <div id="rating_container">
  • Error Line 654, Column 10: ID "rating_container" already defined
    <div id="rating_container">

    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 317, Column 10: ID "rating_container" first defined here
    <div id="rating_container">
  • Error Line 713, Column 306: required attribute "alt" not specified
    …c.it/skin/frontend/enterprise/qvc/images/next280.jpg" class="next" /></a></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>.

  • Error Line 738, Column 25: document type does not allow element "div" here; assuming missing "li" start-tag
    <div style="clear:both;"></div>
  • Error Line 739, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

    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 738, Column 1: start tag was here
    <div style="clear:both;"></div>
  • Error Line 744, Column 236: required attribute "alt" not specified
    …c.it/skin/frontend/enterprise/qvc/images/prev280.jpg" class="prev" /></a></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>.

  • Error Line 753, Column 10: ID "rating_container" already defined
    <div id="rating_container">

    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 317, Column 10: ID "rating_container" first defined here
    <div id="rating_container">
  • Error Line 815, Column 10: ID "rating_container" already defined
    <div id="rating_container">

    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 317, Column 10: ID "rating_container" first defined here
    <div id="rating_container">
  • Error Line 878, Column 10: ID "rating_container" already defined
    <div id="rating_container">

    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 317, Column 10: ID "rating_container" first defined here
    <div id="rating_container">
  • Error Line 940, Column 10: ID "rating_container" already defined
    <div id="rating_container">

    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 317, Column 10: ID "rating_container" first defined here
    <div id="rating_container">
  • Error Line 1002, Column 10: ID "rating_container" already defined
    <div id="rating_container">

    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 317, Column 10: ID "rating_container" first defined here
    <div id="rating_container">
  • Error Line 1064, Column 10: ID "rating_container" already defined
    <div id="rating_container">

    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 317, Column 10: ID "rating_container" first defined here
    <div id="rating_container">
  • Error Line 1123, Column 297: required attribute "alt" not specified
    …c.it/skin/frontend/enterprise/qvc/images/next280.jpg" class="next" /></a></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>.

  • Error Line 1141, Column 236: required attribute "alt" not specified
    …c.it/skin/frontend/enterprise/qvc/images/prev280.jpg" class="prev" /></a></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>.

  • Error Line 1150, Column 10: ID "rating_container" already defined
    <div id="rating_container">

    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 317, Column 10: ID "rating_container" first defined here
    <div id="rating_container">
  • Error Line 1212, Column 10: ID "rating_container" already defined
    <div id="rating_container">

    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 317, Column 10: ID "rating_container" first defined here
    <div id="rating_container">
  • Error Line 1274, Column 10: ID "rating_container" already defined
    <div id="rating_container">

    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 317, Column 10: ID "rating_container" first defined here
    <div id="rating_container">
  • Error Line 1336, Column 10: ID "rating_container" already defined
    <div id="rating_container">

    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 317, Column 10: ID "rating_container" first defined here
    <div id="rating_container">
  • Error Line 1398, Column 10: ID "rating_container" already defined
    <div id="rating_container">

    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 317, Column 10: ID "rating_container" first defined here
    <div id="rating_container">
  • Error Line 1461, Column 10: ID "rating_container" already defined
    <div id="rating_container">

    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 317, Column 10: ID "rating_container" first defined here
    <div id="rating_container">
  • Error Line 1520, Column 297: required attribute "alt" not specified
    …c.it/skin/frontend/enterprise/qvc/images/next280.jpg" class="next" /></a></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>.

  • Error Line 1538, Column 236: required attribute "alt" not specified
    …c.it/skin/frontend/enterprise/qvc/images/prev280.jpg" class="prev" /></a></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>.

  • Error Line 1547, Column 10: ID "rating_container" already defined
    <div id="rating_container">

    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 317, Column 10: ID "rating_container" first defined here
    <div id="rating_container">
  • Error Line 1609, Column 10: ID "rating_container" already defined
    <div id="rating_container">

    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 317, Column 10: ID "rating_container" first defined here
    <div id="rating_container">
  • Error Line 1671, Column 10: ID "rating_container" already defined
    <div id="rating_container">

    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 317, Column 10: ID "rating_container" first defined here
    <div id="rating_container">
  • Error Line 1719, Column 93: ID "product-price-116032" already defined
    …                         <span class="regular-price" id="product-price-116032">

    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 988, Column 93: ID "product-price-116032" first defined here
    …                         <span class="regular-price" id="product-price-116032">
  • Error Line 1734, Column 10: ID "rating_container" already defined
    <div id="rating_container">

    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 317, Column 10: ID "rating_container" first defined here
    <div id="rating_container">
  • Error Line 1796, Column 10: ID "rating_container" already defined
    <div id="rating_container">

    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 317, Column 10: ID "rating_container" first defined here
    <div id="rating_container">
  • Error Line 1859, Column 10: ID "rating_container" already defined
    <div id="rating_container">

    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 317, Column 10: ID "rating_container" first defined here
    <div id="rating_container">
  • Error Line 1929, Column 297: required attribute "alt" not specified
    …c.it/skin/frontend/enterprise/qvc/images/next280.jpg" class="next" /></a></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>.

  • Error Line 2010, Column 214: required attribute "alt" not specified
    …s/Headshots/94x/Vera_Castagna.jpg" style="height: 94px; width: 93px;"/></a></p>

    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 2011, Column 182: required attribute "alt" not specified
    …ttp://cdn.qvc.it/media//presenters/Headshots/94x/Silvia_Cavalca.jpg" /></a></p>

    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 2012, Column 178: required attribute "alt" not specified
    …"http://cdn.qvc.it/media//presenters/Headshots/94x/Sara_Celeste.jpg" /></a></p>

    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 2013, Column 184: required attribute "alt" not specified
    …tp://cdn.qvc.it/media//presenters/Headshots/94x/Chiara_Centioni.jpg" /></a></p>

    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 2014, Column 191: required attribute "alt" not specified
    …//cdn.qvc.it/media//presenters/Headshots/94x/Chiara_Contu_Farci.jpg" /></a></p>

    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 2015, Column 191: required attribute "alt" not specified
    …//cdn.qvc.it/media//presenters/Headshots/94x/Teresa_Dalessandro.jpg" /></a></p>

    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 2016, Column 187: required attribute "alt" not specified
    …p://cdn.qvc.it/media//presenters/Headshots/94x/Cristina_Dragano.jpg" /></a></p>

    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 2017, Column 213: required attribute "alt" not specified
    …rs/Headshots/94x/Chiara_Ferre.jpg" style="height: 94px; width: 93px;"/></a></p>

    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 2018, Column 220: required attribute "alt" not specified
    …eadshots/94x/Roberta_Galiazzo.jpg" style="height: 94px; width: 93px;"/></a></p>

    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 2019, Column 182: required attribute "alt" not specified
    …ttp://cdn.qvc.it/media//presenters/Headshots/94x/Franco_Gandini.jpg" /></a></p>

    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 2020, Column 180: required attribute "alt" not specified
    …http://cdn.qvc.it/media//presenters/Headshots/94x/Marco_Granati.jpg" /></a></p>

    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 2021, Column 186: required attribute "alt" not specified
    …p://cdn.qvc.it/media//presenters/Headshots/94x/Lidia_Longobardi.jpg" /></a></p>

    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 2022, Column 187: required attribute "alt" not specified
    …p://cdn.qvc.it/media//presenters/Headshots/94x/Roberta_Mandelli.jpg" /></a></p>

    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 2023, Column 181: required attribute "alt" not specified
    …http://cdn.qvc.it/media//presenters/Headshots/94x/Roberta_Nanni.jpg" /></a></p>

    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 2024, Column 179: required attribute "alt" not specified
    …"http://cdn.qvc.it/media//presenters/Headshots/94x/Iaia_De_Rose.jpg" /></a></p>

    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 2032, Column 48: document type does not allow element "a" here; assuming missing "li" start-tag
      <a href="http://www.qvc.it/bestsellers.html/"><li>Bestsellers</li></a>
  • Error Line 2032, Column 52: document type does not allow element "li" here
      <a href="http://www.qvc.it/bestsellers.html/"><li>Bestsellers</li></a>

    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 2033, Column 47: document type does not allow element "li" here
      <a href="http://www.qvc.it/marchi.html/"><li>Marca</li></a>

    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 2034, Column 66: document type does not allow element "li" here
    …f="http://www.qvc.it/nuovi-arrivi.html?filter=month/"><li>Nuovi arrivi</li></a>

    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 2036, Column 7: end tag for "li" omitted, but OMITTAG NO was specified
      </ul>	<h3>OGGI SHOPPING</h3>

    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 2032, Column 3: start tag was here
      <a href="http://www.qvc.it/bestsellers.html/"><li>Bestsellers</li></a>
  • Error Line 2038, Column 35: document type does not allow element "script" here; assuming missing "li" start-tag
    		  <script type="text/javascript"> 
  • Error Line 2059, Column 124: document type does not allow element "li" here
    …-e-accessorio-grattugia-con-6-cilindri.html"><li>Today's Special Value</li></a>

    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 2060, Column 64: document type does not allow element "li" here
    …="#" onclick="openLivePopup();return false;"><li>Guarda QVC in diretta</li></a>

    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 2061, Column 31: document type does not allow element "li" here
    		  <a href="/tv/guida-tv"><li>Guida TV</li></a>

    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 2062, Column 9: end tag for "li" omitted, but OMITTAG NO was specified
    		  </ul>

    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 2038, Column 5: start tag was here
    		  <script type="text/javascript"> 
  • Error Line 2065, Column 39: document type does not allow element "a" here; assuming missing "li" start-tag
      <a href="http://www.qvc.it/informa/"><li>QVC informa: AiFOS</li></a>
  • Error Line 2065, Column 43: document type does not allow element "li" here
      <a href="http://www.qvc.it/informa/"><li>QVC informa: AiFOS</li></a>

    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 2066, Column 73: document type does not allow element "li" here
    …ww.qvc.it/speciali/giallo-zafferano-i-vincitori/"><li>Giallo Zafferano</li></a>

    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 2067, Column 46: document type does not allow element "li" here
      <a href="http://www.qvc.it/scopri-qvc/"><li>Scopri QVC</li></a>

    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 2068, Column 78: document type does not allow element "li" here
    …/speciali/gran-gala-della-cucina-le-ricette/"><li>Galà cucina: ricette</li></a>

    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 2069, Column 59: document type does not allow element "li" here
    …a href="http://www.qvc.it/speciali/ricette-easiyo/"><li>Ricette EasiYo</li></a>

    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 2070, Column 61: document type does not allow element "li" here
    …"http://www.qvc.it/speciali/diamonique-week2/"><li>Speciale Diamonique</li></a>

    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 2071, Column 56: document type does not allow element "li" here
    …<a href="http://www.qvc.it/speciali/kipling-faq/"><li>Speciale Kipling</li></a>

    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 2072, Column 54: document type does not allow element "li" here
      <a href="http://www.qvc.it/speciali/ecommerce/"><li>Acquista Online</li></a>

    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 2073, Column 65: document type does not allow element "li" here
    …w.qvc.it/speciali/bonifico-domiciliato/"><li>Rimborsi tramite Poste IT</li></a>

    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 2074, Column 6: end tag for "li" omitted, but OMITTAG NO was specified
     </ul></div>

    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 2065, Column 3: start tag was here
      <a href="http://www.qvc.it/informa/"><li>QVC informa: AiFOS</li></a>
  • Error Line 2077, Column 56: there is no attribute "target"
    …://www.facebook.com/QVCItalia" target="_blank"><img src="http://cdn.qvc.it/ski…

    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 2077, Column 164: required attribute "alt" not specified
    …it/skin/frontend/enterprise/qvc/images/facebook.png" class="facebookimg" /></a>

    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 2078, Column 40: there is no attribute "data-site"
    …   <div class="fb-activity" data-site="qvc.it" data-app-id="279754025438357" d…

    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 2078, Column 61: there is no attribute "data-app-id"
    …ivity" data-site="qvc.it" data-app-id="279754025438357" data-action="like" dat…

    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 2078, Column 91: there is no attribute "data-action"
    …-app-id="279754025438357" data-action="like" data-width="201" data-height="350…

    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 2078, Column 109: there is no attribute "data-width"
    …438357" data-action="like" data-width="201" data-height="350" data-header="fal…

    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 2078, Column 127: there is no attribute "data-height"
    …n="like" data-width="201" data-height="350" data-header="false" data-font="tah…

    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 2078, Column 145: there is no attribute "data-header"
    …h="201" data-height="350" data-header="false" data-font="tahoma" data-border-c…

    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 2078, Column 163: there is no attribute "data-font"
    …t="350" data-header="false" data-font="tahoma" data-border-color="#F3EBDE" dat…

    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 2078, Column 190: there is no attribute "data-border-color"
    … data-font="tahoma" data-border-color="#F3EBDE" data-recommendations="false" s…

    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 2078, Column 221: there is no attribute "data-recommendations"
    …-color="#F3EBDE" data-recommendations="false" style="padding-left: 3px;"></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 2080, Column 23: document type does not allow element "style" here
    <style type="text/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).

  • Error Line 2172, Column 15: there is no attribute "width"
    				<td width="135" align="center" valign="top" style="text-align: center;">

    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 2173, Column 97: cannot generate system identifier for general entity "size"
    …sign.com/getseal?host_name=www.qvc.it&size=S&use_flash=NO&use_transparent=NO&l…

    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 2173, Column 97: general entity "size" not defined and no default entity
    …sign.com/getseal?host_name=www.qvc.it&size=S&use_flash=NO&use_transparent=NO&l…

    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 2173, Column 101: reference not terminated by REFC delimiter
    ….com/getseal?host_name=www.qvc.it&size=S&use_flash=NO&use_transparent=NO&lang=…

    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 2173, Column 101: reference to external entity in attribute value
    ….com/getseal?host_name=www.qvc.it&size=S&use_flash=NO&use_transparent=NO&lang=…

    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 2173, Column 101: reference to entity "size" for which no system identifier could be generated
    ….com/getseal?host_name=www.qvc.it&size=S&use_flash=NO&use_transparent=NO&lang=…

    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 2173, Column 96: entity was defined here
    …isign.com/getseal?host_name=www.qvc.it&size=S&use_flash=NO&use_transparent=NO&…
  • Warning Line 2173, Column 104: cannot generate system identifier for general entity "use_flash"
    …m/getseal?host_name=www.qvc.it&size=S&use_flash=NO&use_transparent=NO&lang=it"…

    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 2173, Column 104: general entity "use_flash" not defined and no default entity
    …m/getseal?host_name=www.qvc.it&size=S&use_flash=NO&use_transparent=NO&lang=it"…

    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 2173, Column 113: reference not terminated by REFC delimiter
    …?host_name=www.qvc.it&size=S&use_flash=NO&use_transparent=NO&lang=it"></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 2173, Column 113: reference to external entity in attribute value
    …?host_name=www.qvc.it&size=S&use_flash=NO&use_transparent=NO&lang=it"></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 2173, Column 113: reference to entity "use_flash" for which no system identifier could be generated
    …?host_name=www.qvc.it&size=S&use_flash=NO&use_transparent=NO&lang=it"></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 2173, Column 103: entity was defined here
    …om/getseal?host_name=www.qvc.it&size=S&use_flash=NO&use_transparent=NO&lang=it…
  • Warning Line 2173, Column 117: cannot generate system identifier for general entity "use_transparent"
    …t_name=www.qvc.it&size=S&use_flash=NO&use_transparent=NO&lang=it"></script><br…

    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 2173, Column 117: general entity "use_transparent" not defined and no default entity
    …t_name=www.qvc.it&size=S&use_flash=NO&use_transparent=NO&lang=it"></script><br…

    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 2173, Column 132: reference not terminated by REFC delimiter
    …name=www.qvc.it&size=S&use_flash=NO&use_transparent=NO&lang=it"></script><br />

    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 2173, Column 132: reference to external entity in attribute value
    …name=www.qvc.it&size=S&use_flash=NO&use_transparent=NO&lang=it"></script><br />

    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 2173, Column 132: reference to entity "use_transparent" for which no system identifier could be generated
    …name=www.qvc.it&size=S&use_flash=NO&use_transparent=NO&lang=it"></script><br />

    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 2173, Column 116: entity was defined here
    …st_name=www.qvc.it&size=S&use_flash=NO&use_transparent=NO&lang=it"></script><b…
  • Warning Line 2173, Column 140: reference not terminated by REFC delimiter
    …name=www.qvc.it&size=S&use_flash=NO&use_transparent=NO&lang=it"></script><br />

    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 2202, Column 114: cannot generate system identifier for general entity "ADFPageName"
    …form.net/Serving/TrackPoint/?pm=86642&ADFPageName=Default Store View|QVC Itali…

    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 2202, Column 114: general entity "ADFPageName" not defined and no default entity
    …form.net/Serving/TrackPoint/?pm=86642&ADFPageName=Default Store View|QVC Itali…

    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 2202, Column 125: reference not terminated by REFC delimiter
    …rving/TrackPoint/?pm=86642&ADFPageName=Default Store View|QVC Italia|Il canale…

    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 2202, Column 125: reference to external entity in attribute value
    …rving/TrackPoint/?pm=86642&ADFPageName=Default Store View|QVC Italia|Il canale…

    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 2202, Column 125: reference to entity "ADFPageName" for which no system identifier could be generated
    …rving/TrackPoint/?pm=86642&ADFPageName=Default Store View|QVC Italia|Il canale…

    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 2202, Column 113: entity was defined here
    …dform.net/Serving/TrackPoint/?pm=86642&ADFPageName=Default Store View|QVC Ital…
  • Warning Line 2202, Column 190: cannot generate system identifier for general entity "ADFdivider"
    …lia|Il canale per chi ama lo shopping&ADFdivider=|" width="1" height="1" alt="…

    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 2202, Column 190: general entity "ADFdivider" not defined and no default entity
    …lia|Il canale per chi ama lo shopping&ADFdivider=|" width="1" height="1" alt="…

    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 2202, Column 200: reference not terminated by REFC delimiter
    …ale per chi ama lo shopping&ADFdivider=|" width="1" height="1" alt="" /></p></…

    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 2202, Column 200: reference to external entity in attribute value
    …ale per chi ama lo shopping&ADFdivider=|" width="1" height="1" alt="" /></p></…

    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 2202, Column 200: reference to entity "ADFdivider" for which no system identifier could be generated
    …ale per chi ama lo shopping&ADFdivider=|" width="1" height="1" alt="" /></p></…

    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 2202, Column 189: entity was defined here
    …alia|Il canale per chi ama lo shopping&ADFdivider=|" width="1" height="1" alt=…

Visitor Analysis

Daily Visitor
  • 2.683 visits
Daily Visitor