SALDOS - Roupa mulher, homem, lingerie sexy, desporto, acessórios, criança, bebé; pequenos electrodomesticos, artigos lar, decoração e utilidades casa, outlet: La Redoute propõe a venda roupas online. ...

laredoute.pt
  • Domain Name
    laredoute.pt
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #32669
  • Page Size
    204.6 KB
  • Ip Address
    195.24.247.33
  • Heading
    H1: 1, H2: 0, H3: 7, H4: 0, H5: 2, H6: 1
  • Images
    1 GIF, 19 JPG, 10 PNG

Website Meta Analysis

  • Title
    Promoções, Descontos - La Redoute - Catálogo & Loja online de Roupa e Moda mulher, criança, homem, Desporto, marcas
  • Meta Keyword
    Roupa mulher, roupa pré mamã, lingerie, desporto, marcas, homem, acessórios, calçado, bebé, criança, tamanhos grandes, moda, tendências, utilidades, pequenos electrodomesticos; roupas online, têxtil-lar, decoração, La Redoute
  • Meta Description
    SALDOS - Roupa mulher, homem, lingerie sexy, desporto, acessórios, criança, bebé; pequenos electrodomesticos, artigos lar, decoração e utilidades casa, outlet: La Redoute propõe a venda roupas online.

Technical Analysis

  • Webserver
  • Ip Address
    195.24.247.33
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from laredoute.pt.

HTML Analysis

  • cache-control: private
  • content-type: text/html; charset=utf-8
  • x-aspnet-version: 2.0.50727
  • x-ua-compatible: IE=edge
  • content-length: 213252
  • date: Sun, 10 Feb 2013 16:41:23 GMT
  • age: 0
  • connection: keep-alive
  • x-cache: MISS
  • x-server: zzsrpc10
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for laredoute.pt

DNS Analysis


DNS servers
pdns2.cscdns.net [69.36.145.33]
pdns1.cscdns.net [209.112.114.33]


DNS Records

Answer records
laredoute.pt SOA
server: pdns1.cscdns.net
email: hostmaster@cscdns.net
serial: 2005052022
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 1800
1800s
laredoute.pt NS  pdns2.cscdns.net 1800s
laredoute.pt NS  pdns1.cscdns.net 1800s
laredoute.pt A 195.24.247.33 1800s
laredoute.pt MX
preference: 100
exchange: mailhub.francenet.fr
1800s
laredoute.pt MX
preference: 10
exchange: mail.la-redoute.pt
1800s

Authority records

Additional records

IP 195.24.247.33 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 70 Errors
  • 34 Warnings
Ratio Text/Html
  • 0.8481978326251969
Message Error
  • Error Line 5, Column 50: there is no attribute "class"
    <html xmlns="http://www.w3.org/1999/xhtml" class="htmlMain">

    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 17, Column 47: character "&" is the first character of a delimiter but occurred as data
    …es, Descontos - La Redoute - Catálogo & Loja online de Roupa e Moda mulher, cr…

    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 22, Column 14: there is no attribute "name"
    		<form name="aspnetForm" method="post" action="index.aspx" id="aspnetForm">

    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 32, Column 11: required attribute "type" not specified
    			<script>(function(d, s, id) {

    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 102, Column 119: there is no attribute "autocomplete"
    …sletter" class="textBox" autocomplete="off" value="Subscreva a Newsletter" onk…

    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 108, Column 95: cannot generate system identifier for general entity "condições"
    …Terms('500');">Concordo com os termos&condições e subscrevo a Newsletter La Re…

    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 108, Column 95: general entity "condições" not defined and no default entity
    …Terms('500');">Concordo com os termos&condições e subscrevo a Newsletter La Re…

    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 108, Column 104: reference not terminated by REFC delimiter
    …0');">Concordo com os termos&condições e subscrevo a Newsletter La Redoute.</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 108, Column 104: reference to entity "condições" for which no system identifier could be generated
    …0');">Concordo com os termos&condições e subscrevo a Newsletter La Redoute.</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 108, Column 94: entity was defined here
    …sTerms('500');">Concordo com os termos&condições e subscrevo a Newsletter La R…
  • Error Line 113, Column 160: element "center" undefined
    …doPostBack('ctl00$ctl07$lnkNewsletter','')"><center>CONFIRMO</center></a></div>

    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 207, Column 181: there is no attribute "target"
    …tters/pontos_entrega_ah10.pdf" target="_blank">Encontro o meu ponto "Pick me!"…

    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 1190, Column 167: character "&" is the first character of a delimiter but occurred as data
    …yOut_repColumn2_ctl04_hypLink" href="/categories/cat-1811.aspx">Bebé & Mamã</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 1730, Column 199: character "&" is the first character of a delimiter but occurred as data
    …/categories/cat-3345.aspx" style="color:#000000;">Capas de sofá & companhia</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 3021, Column 185: character "&" is the first character of a delimiter but occurred as data
    …pLink" href="/outlet-calcado-acessorios/cat-1402.aspx">Calçado & Acessórios</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 3031, Column 190: character "&" is the first character of a delimiter but occurred as data
    …k" href="/outlet-textil-lar-decoracao/cat-1388.aspx">Têxtil-lar & Decoração</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.
  • Error Line 3157, Column 154: document type does not allow element "link" here
    …recos_baixos/hp_small_prices.css" rel="stylesheet" type="text/css" media="all">

    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 3157, Column 155: end tag for "link" omitted, but OMITTAG NO was specified
    …recos_baixos/hp_small_prices.css" rel="stylesheet" type="text/css" media="all">

    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 3157, Column 1: start tag was here
    <link href="http://media.laredoute.fr/INTL/Chameleon/pt/pt/pe13/opeco/SPE_preco…
  • Error Line 3158, Column 111: document type does not allow element "link" here
    …pis.com/css?family=Titillium+Web:300,400,600' rel='stylesheet' 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 3158, Column 112: end tag for "link" omitted, but OMITTAG NO was specified
    …pis.com/css?family=Titillium+Web:300,400,600' rel='stylesheet' type='text/css'>

    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 3158, Column 1: start tag was here
    <link href='http://fonts.googleapis.com/css?family=Titillium+Web:300,400,600' r…
  • Warning Line 3161, Column 62: cannot generate system identifier for general entity "lid"
    …cat-649.aspx" class="link_all" name="&lid=pe13:hp:zsa:precos-baixos-spe"><img …

    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 3161, Column 62: general entity "lid" not defined and no default entity
    …cat-649.aspx" class="link_all" name="&lid=pe13:hp:zsa:precos-baixos-spe"><img …

    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 3161, Column 65: reference not terminated by REFC delimiter
    …-649.aspx" class="link_all" name="&lid=pe13:hp:zsa:precos-baixos-spe"><img src…

    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 3161, Column 65: reference to external entity in attribute value
    …-649.aspx" class="link_all" name="&lid=pe13:hp:zsa:precos-baixos-spe"><img src…

    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 3161, Column 65: reference to entity "lid" for which no system identifier could be generated
    …-649.aspx" class="link_all" name="&lid=pe13:hp:zsa:precos-baixos-spe"><img src…

    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 3161, Column 61: entity was defined here
    …/cat-649.aspx" class="link_all" name="&lid=pe13:hp:zsa:precos-baixos-spe"><img…
  • Error Line 3161, Column 65: character "=" is not allowed in the value of attribute "name"
    …-649.aspx" class="link_all" name="&lid=pe13:hp:zsa:precos-baixos-spe"><img src…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 3161, Column 212: there is no attribute "border"
    …/pe13/opeco/SPE_precos_baixos/HPZSA_small-prix.jpg" border="0" usemap="#Map" />

    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 3161, Column 231: required attribute "alt" not specified
    …/pe13/opeco/SPE_precos_baixos/HPZSA_small-prix.jpg" border="0" usemap="#Map" />

    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 3162, Column 103: there is no attribute "name"
    …6" href="/category/cat-649.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe" /><…

    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 3162, Column 108: reference not terminated by REFC delimiter
    …ef="/category/cat-649.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe" /><area …

    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 3162, Column 108: reference to external entity in attribute value
    …ef="/category/cat-649.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe" /><area …

    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 3162, Column 108: reference to entity "lid" for which no system identifier could be generated
    …ef="/category/cat-649.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe" /><area …

    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 3161, Column 61: entity was defined here
    …/cat-649.aspx" class="link_all" name="&lid=pe13:hp:zsa:precos-baixos-spe"><img…
  • Error Line 3162, Column 141: required attribute "alt" not specified
    …"&lid=pe13:hp:zsa:precos-baixos-spe" /><area shape="rect" coords="750,3,976,37…

    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 3162, Column 261: reference not terminated by REFC delimiter
    …e-70-mulher/cat-63117.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe" /></map>…

    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 3162, Column 261: reference to external entity in attribute value
    …e-70-mulher/cat-63117.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe" /></map>…

    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 3162, Column 261: reference to entity "lid" for which no system identifier could be generated
    …e-70-mulher/cat-63117.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe" /></map>…

    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 3161, Column 61: entity was defined here
    …/cat-649.aspx" class="link_all" name="&lid=pe13:hp:zsa:precos-baixos-spe"><img…
  • Error Line 3162, Column 294: required attribute "alt" not specified
    …0-mulher/cat-63117.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe" /></map></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>.

  • Warning Line 3166, Column 51: reference not terminated by REFC delimiter
    …ef="/category/cat-649.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe">> Mulher…

    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 3166, Column 51: reference to external entity in attribute value
    …ef="/category/cat-649.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe">> Mulher…

    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 3166, Column 51: reference to entity "lid" for which no system identifier could be generated
    …ef="/category/cat-649.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe">> Mulher…

    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 3161, Column 61: entity was defined here
    …/cat-649.aspx" class="link_all" name="&lid=pe13:hp:zsa:precos-baixos-spe"><img…
  • Error Line 3166, Column 51: character "=" is not allowed in the value of attribute "name"
    …ef="/category/cat-649.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe">> Mulher…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Warning Line 3167, Column 66: reference not terminated by REFC delimiter
    …rianca-menino/cat-377.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe">> Crian&…

    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 3167, Column 66: reference to external entity in attribute value
    …rianca-menino/cat-377.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe">> Crian&…

    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 3167, Column 66: reference to entity "lid" for which no system identifier could be generated
    …rianca-menino/cat-377.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe">> Crian&…

    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 3161, Column 61: entity was defined here
    …/cat-649.aspx" class="link_all" name="&lid=pe13:hp:zsa:precos-baixos-spe"><img…
  • Error Line 3167, Column 66: character "=" is not allowed in the value of attribute "name"
    …rianca-menino/cat-377.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe">> Crian&…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Warning Line 3168, Column 91: reference not terminated by REFC delimiter
    …lusas-tunicas/cat-578.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe">> Tamanh…

    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 3168, Column 91: reference to external entity in attribute value
    …lusas-tunicas/cat-578.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe">> Tamanh…

    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 3168, Column 91: reference to entity "lid" for which no system identifier could be generated
    …lusas-tunicas/cat-578.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe">> Tamanh…

    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 3161, Column 61: entity was defined here
    …/cat-649.aspx" class="link_all" name="&lid=pe13:hp:zsa:precos-baixos-spe"><img…
  • Error Line 3168, Column 91: character "=" is not allowed in the value of attribute "name"
    …lusas-tunicas/cat-578.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe">> Tamanh…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Warning Line 3169, Column 65: reference not terminated by REFC delimiter
    …homem-camisas/cat-271.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe">> Homem<…

    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 3169, Column 65: reference to external entity in attribute value
    …homem-camisas/cat-271.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe">> Homem<…

    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 3169, Column 65: reference to entity "lid" for which no system identifier could be generated
    …homem-camisas/cat-271.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe">> Homem<…

    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 3161, Column 61: entity was defined here
    …/cat-649.aspx" class="link_all" name="&lid=pe13:hp:zsa:precos-baixos-spe"><img…
  • Error Line 3169, Column 65: character "=" is not allowed in the value of attribute "name"
    …homem-camisas/cat-271.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe">> Homem<…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Warning Line 3170, Column 76: reference not terminated by REFC delimiter
    …alcado-mulher/cat-499.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe">> Cal&cc…

    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 3170, Column 76: reference to external entity in attribute value
    …alcado-mulher/cat-499.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe">> Cal&cc…

    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 3170, Column 76: reference to entity "lid" for which no system identifier could be generated
    …alcado-mulher/cat-499.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe">> Cal&cc…

    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 3161, Column 61: entity was defined here
    …/cat-649.aspx" class="link_all" name="&lid=pe13:hp:zsa:precos-baixos-spe"><img…
  • Error Line 3170, Column 76: character "=" is not allowed in the value of attribute "name"
    …alcado-mulher/cat-499.aspx" name="&lid=pe13:hp:zsa:precos-baixos-spe">> Cal&cc…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Warning Line 3178, Column 52: reference not terminated by REFC delimiter
    …aco-lookbook-lingerie.aspx" name="&lid=ah12:hp:module:spe-lingerie"><img src="…

    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 3178, Column 52: reference to external entity in attribute value
    …aco-lookbook-lingerie.aspx" name="&lid=ah12:hp:module:spe-lingerie"><img src="…

    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 3178, Column 52: reference to entity "lid" for which no system identifier could be generated
    …aco-lookbook-lingerie.aspx" name="&lid=ah12:hp:module:spe-lingerie"><img src="…

    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 3161, Column 61: entity was defined here
    …/cat-649.aspx" class="link_all" name="&lid=pe13:hp:zsa:precos-baixos-spe"><img…
  • Error Line 3178, Column 52: character "=" is not allowed in the value of attribute "name"
    …aco-lookbook-lingerie.aspx" name="&lid=ah12:hp:module:spe-lingerie"><img src="…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 3178, Column 233: required attribute "alt" not specified
    …ook_lingerie/hp_module_lingerie.jpg" width="982" height="202" border="0" /></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 3182, Column 141: document type does not allow element "link" here
    …3/opeco/saint_valentin/zsb-hp-stvalentin.css" rel="stylesheet" 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 3182, Column 142: end tag for "link" omitted, but OMITTAG NO was specified
    …3/opeco/saint_valentin/zsb-hp-stvalentin.css" rel="stylesheet" type="text/css">

    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 3182, Column 1: start tag was here
    <link href="http://media.laredoute.fr/INTL/Chameleon/pt/pt/pe13/opeco/saint_val…
  • Error Line 3183, Column 130: document type does not allow element "link" here
    …n/pt/pt/pe13/opeco/ellos_v1/zsb_hp_ellos.css" rel="stylesheet" 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 3183, Column 131: end tag for "link" omitted, but OMITTAG NO was specified
    …n/pt/pt/pe13/opeco/ellos_v1/zsb_hp_ellos.css" rel="stylesheet" type="text/css">

    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 3183, Column 1: start tag was here
    <link href="http://media.laredoute.fr/intl/Chameleon/pt/pt/pe13/opeco/ellos_v1/…
  • Error Line 3184, Column 140: document type does not allow element "link" here
    …edoute.fr/INTL/Chameleon/pt/pt/pe13/opeco/Taillissime/V1/nc_hp_zsb_pe13.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 3185, Column 130: document type does not allow element "link" here
    …t/pt/pe13/opeco/anne_weyburn/zsb_hp.css" rel="stylesheet" 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).

  • Warning Line 3190, Column 54: reference not terminated by REFC delimiter
    …="/category/cat-66059.aspx" name="&lid=pe13:hp:zsb1:saint-valentin"><img src="…

    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 3190, Column 54: reference to external entity in attribute value
    …="/category/cat-66059.aspx" name="&lid=pe13:hp:zsb1:saint-valentin"><img src="…

    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 3190, Column 54: reference to entity "lid" for which no system identifier could be generated
    …="/category/cat-66059.aspx" name="&lid=pe13:hp:zsb1:saint-valentin"><img src="…

    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 3161, Column 61: entity was defined here
    …/cat-649.aspx" class="link_all" name="&lid=pe13:hp:zsa:precos-baixos-spe"><img…
  • Error Line 3190, Column 54: character "=" is not allowed in the value of attribute "name"
    …="/category/cat-66059.aspx" name="&lid=pe13:hp:zsb1:saint-valentin"><img src="…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 3190, Column 191: there is no attribute "name"
    …aint_valentin/HP-zsb.jpg" alt="" name="HP_zsb" width="314" height="447" border…

    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 3196, Column 52: reference not terminated by REFC delimiter
    …ef="/category/cat-101.aspx" name="&lid=pe13:hp:zsb2:taillissime"><img src="htt…

    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 3196, Column 52: reference to external entity in attribute value
    …ef="/category/cat-101.aspx" name="&lid=pe13:hp:zsb2:taillissime"><img src="htt…

    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 3196, Column 52: reference to entity "lid" for which no system identifier could be generated
    …ef="/category/cat-101.aspx" name="&lid=pe13:hp:zsb2:taillissime"><img src="htt…

    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 3161, Column 61: entity was defined here
    …/cat-649.aspx" class="link_all" name="&lid=pe13:hp:zsa:precos-baixos-spe"><img…
  • Error Line 3196, Column 52: character "=" is not allowed in the value of attribute "name"
    …ef="/category/cat-101.aspx" name="&lid=pe13:hp:zsb2:taillissime"><img src="htt…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 3196, Column 227: required attribute "alt" not specified
    …ssime/V1/zsb_nc_secret_seduction.jpg" width="314" height="447" border="0"/></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>.

  • Warning Line 3203, Column 57: reference not terminated by REFC delimiter
    …search.aspx?keyword=670213" name="&lid=ah12:hp:zsb3:ellos-v1"><img src="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 3203, Column 57: reference to external entity in attribute value
    …search.aspx?keyword=670213" name="&lid=ah12:hp:zsb3:ellos-v1"><img src="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 3203, Column 57: reference to entity "lid" for which no system identifier could be generated
    …search.aspx?keyword=670213" name="&lid=ah12:hp:zsb3:ellos-v1"><img src="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 3161, Column 61: entity was defined here
    …/cat-649.aspx" class="link_all" name="&lid=pe13:hp:zsa:precos-baixos-spe"><img…
  • Error Line 3203, Column 57: character "=" is not allowed in the value of attribute "name"
    …search.aspx?keyword=670213" name="&lid=ah12:hp:zsb3:ellos-v1"><img src="http:/…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 3203, Column 213: required attribute "alt" not specified
    …e13/opeco/ellos_v1/zsb_hp_ellos.jpg" width="314" height="447" border="0" /></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 3303, Column 53: there is no attribute "src"
    …"ctl00_ctl09_divFBIFrame"><iframe src="//www.facebook.com/plugins/like.php?hre…

    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 3303, Column 273: there is no attribute "scrolling"
    …&amp;height=20&amp;locale=pt_PT" scrolling="no" frameborder="0"></iframe></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 3303, Column 290: there is no attribute "frameborder"
    …&amp;height=20&amp;locale=pt_PT" scrolling="no" frameborder="0"></iframe></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 3303, Column 293: element "iframe" undefined
    …&amp;height=20&amp;locale=pt_PT" scrolling="no" frameborder="0"></iframe></div>

    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 3324, Column 221: required attribute "alt" not specified
    …_ctl09_repColumn3Top_ctl00_imgImage" /></a></li><li><a href="http://twitter.co…

    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 3324, Column 431: required attribute "alt" not specified
    …_ctl09_repColumn3Top_ctl01_imgImage" /></a></li><li><a href="http://pinterest.…

    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 3324, Column 646: required attribute "alt" not specified
    …/pt-PT/pinterest.png" id="ctl00_ctl09_repColumn3Top_ctl02_imgImage" /></a></li>

    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 3327, Column 56: end tag for "br" omitted, but OMITTAG NO was specified
    					<br id="ctl00_ctl09_brCol3Top" class="clearFloat">			

    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 3327, Column 6: start tag was here
    					<br id="ctl00_ctl09_brCol3Top" class="clearFloat">			
  • Error Line 3329, Column 249: required attribute "alt" not specified
    …/pt-PT/onlineTrust.png" id="ctl00_ctl09_repColumn3Bottom_ctl00_imgImage" /></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 3341, Column 10: document type does not allow element "h6" here; missing one of "object", "ins", "del", "map", "button" start-tag
    						<h6>Inscrição na Newsletter</h6>

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

  • Warning Line 3352, Column 103: reference not terminated by REFC delimiter
    …0');">Concordo com os termos&condições e subscrevo a Newsletter La Redoute.</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 3352, Column 103: reference to entity "condições" for which no system identifier could be generated
    …0');">Concordo com os termos&condições e subscrevo a Newsletter La Redoute.</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 108, Column 94: entity was defined here
    …sTerms('500');">Concordo com os termos&condições e subscrevo a Newsletter La R…
  • Warning Line 3372, Column 96: character "&" is the first character of a delimiter but occurred as data
    …es, Descontos - La Redoute - Catálogo & Loja online de Roupa e Moda mulher, cr…

    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 3410, Column 162: document type does not allow element "a" here; missing one of "object", "ins", "del", "span", "bdo", "tt", "i", "b", "big", "small", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label" start-tag
    … gerais de venda | <a href="/recrutamento.aspx">Recrutamento La Redoute</a></p>

    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 3410, Column 193: end tag for "a" omitted, but OMITTAG NO was specified
    … gerais de venda | <a href="/recrutamento.aspx">Recrutamento La Redoute</a></p>

    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 3410, Column 75: start tag was here
    …emap/sitemap.aspx">Mapa do site</a> | <a href="/sellconditions.aspx">Condições…
  • Error Line 3468, Column 25: there is no attribute "language"
    			    <script language="JavaScript" type="text/javascript" src="/omniture/s_co…

    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 3535, Column 70: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    				<noscript><a href="http://www.omniture.com" title="Web Analytics"><img

    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 3558, Column 140: there is no attribute "width"
    …67;cat=homek955;ord=' + a + '?" width="1" height="1" frameborder="0" style="di…

    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 3558, Column 151: there is no attribute "height"
    …k955;ord=' + a + '?" width="1" height="1" frameborder="0" style="display:none"…

    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 3558, Column 177: there is no attribute "style"
    … a + '?" width="1" height="1" frameborder="0" style="display:none"></iframe>');

    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 3558, Column 191: element "iframe" undefined
    … a + '?" width="1" height="1" frameborder="0" style="display:none"></iframe>');

    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 3562, Column 167: element "iframe" undefined
    …955;ord=1?" width="1" height="1" frameborder="0" style="display:none"></iframe>

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

Visitor Analysis

Daily Visitor
  • 4.783 visits
Daily Visitor