Nasza oferta | Praca & przedsiębiorstwo | Nieruchomości Nasza oferta Taniej Asortyment Informacje Przepisy Odpowiedzialność społeczna TV aktualneod poniedziałkuod poniedziałkuod czwartkuod czwartkuod soboty www.lidl.pl / Nasza oferta © Lidl ... ...

lidl.pl
  • Domain Name
    lidl.pl
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #10871
  • Page Size
    39.7 KB
  • Ip Address
    94.127.75.220
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 3, H5: 0, H6: 0
  • Images
    1 GIF, 13 JPG, 1 PNG

Website Meta Analysis

  • Title
    LIDL sklepy spożywcze – gazetka, promocje, przepisy, praca
  • Meta Keyword
  • Meta Description
      Nasza oferta | Praca & przedsiębiorstwo | Nieruchomości Nasza oferta Taniej Asortyment Informacje Przepisy Odpowiedzialność społeczna TV aktualneod poniedziałkuod poniedziałkuod czwartkuod czwartkuod soboty www.lidl.pl / Nasza oferta © Lidl ...

Technical Analysis

  • Webserver
    Microsoft-IIS/7.5
  • Ip Address
    94.127.75.220
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from lidl.pl.

HTML Analysis

  • content-type: text/html;charset=UTF-8
  • server: Microsoft-IIS/7.5
  • lsrequestid: 1074773034
  • x-powered-by: ASP.NET
  • date: Sun, 24 Feb 2013 15:07:06 GMT
  • content-length: 41497
  • accept-ranges: bytes
  • cache-control: private, max-age=2700
  • age: 0
  • expires: Sun, 24 Feb 2013 15:52:06 GMT
  • x-cdn: LIDL PL
  • connection: Keep-Alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for lidl.pl

DNS Analysis


DNS servers
dns11.cotdns.net [208.93.136.11]
dns13.cotdns.net [98.142.96.13]
dns12.cotdns.net [208.93.136.12]
dns14.cotdns.net [98.142.96.14]


DNS Records

Answer records
lidl.pl MX
preference: 10
exchange: mail2.enc99-int.com
3600s
lidl.pl MX
preference: 10
exchange: mail3.enc99-int.com
3600s
lidl.pl MX
preference: 10
exchange: mail1.enc99-int.com
3600s
lidl.pl NS  dns11.cotdns.net 172800s
lidl.pl NS  dns12.cotdns.net 172800s
lidl.pl NS  dns13.cotdns.net 172800s
lidl.pl NS  dns14.cotdns.net 172800s
lidl.pl SOA
server: dns11.cotdns.net
email: sysadmin@cotendo.com
serial: 1
refresh: 3600
retry: 600
expire: 604800
minimum ttl: 0
172800s
lidl.pl A 208.93.142.220 300s

Authority records

Additional records
dns11.cotdns.net A 208.93.136.11 604800s
dns12.cotdns.net A 208.93.136.12 604800s
dns13.cotdns.net A 98.142.96.13 604800s
dns14.cotdns.net A 98.142.96.14 604800s

IP 94.127.75.220 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 80 Errors
  • 79 Warnings
Ratio Text/Html
  • 0.4066971529724148
Message Error
  • Error Line 32, Column 75: required attribute "type" not specified
    …/css_js/3946.js" language="javascript"></script><script language="JavaScript" …

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

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

  • Warning Line 34, Column 8: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 34, Column 12: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 34, Column 16: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 34, Column 20: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 34, Column 24: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 34, Column 28: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 34, Column 32: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 34, Column 36: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 34, Column 40: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 34, Column 44: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 34, Column 48: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 34, Column 52: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 34, Column 56: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 34, Column 60: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 34, Column 64: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 34, Column 68: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 34, Column 72: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 34, Column 76: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 49, Column 4: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 49, Column 8: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 49, Column 12: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 49, Column 16: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 49, Column 20: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 49, Column 24: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 49, Column 28: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 49, Column 32: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 49, Column 36: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 49, Column 40: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 49, Column 44: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 49, Column 48: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 49, Column 52: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 49, Column 56: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 49, Column 60: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 49, Column 64: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 49, Column 68: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 49, Column 72: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 49, Column 76: multiple comments in comment declaration
    // -----------------------------------------------------------------------------
  • Warning Line 69, Column 4: multiple comments in comment declaration
    // -->
  • Error Line 103, Column 31: 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 145, Column 37: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                    <li class="inactive"><a href="/cps/rde/xchg/SID-95B56D9A-DCFBB3…

    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 145, Column 114: character "&" is the first character of a delimiter but occurred as data
    …chg/SID-95B56D9A-DCFBB3BD/lidl_pl/hs.xsl/4034.htm">Praca & przedsiębiorstwo</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 147, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    </li><li class="inactive">

    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 151, Column 37: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                    <li class="inactive"><a href="/cps/rde/xchg/SID-95B56D9A-DCFBB3…

    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 156, 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 147, Column 6: start tag was here
    </li><li class="inactive">
  • Error Line 156, 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 141, Column 6: start tag was here
    </li><li class="inactive">
  • Error Line 300, Column 95: required attribute "alt" not specified
    …"/static_content/lidl_pl/images/PL/aplikacja_Iphone_566x342_statyk.jpg"/></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 310, Column 10: ID "med_flash" already defined
    <div id="med_flash" class="imagenoshade" onclick="window.open('http://www.lidl.…

    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 265, Column 10: ID "med_flash" first defined here
    <div id="med_flash" class="" >
  • Error Line 345, Column 102: required attribute "alt" not specified
    …c_content/lidl_pl/images/PL/kw09_wiosenne_porzadki_pion_nowy_as3_1.jpg"/></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 355, Column 10: ID "med_flash" already defined
    <div id="med_flash" class="imagenoshade" onclick="window.open('http://www.lidl.…

    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 265, Column 10: ID "med_flash" first defined here
    <div id="med_flash" class="" >
  • Error Line 390, Column 88: required attribute "alt" not specified
    …mg src="/static_content/lidl_pl/images/PL/kw09_technika_pion_nowy2.jpg"/></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 400, Column 10: ID "med_flash" already defined
    <div id="med_flash" class="imagenoshade" onclick="window.open('http://www.lidl.…

    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 265, Column 10: ID "med_flash" first defined here
    <div id="med_flash" class="" >
  • Error Line 435, Column 88: required attribute "alt" not specified
    …mg src="/static_content/lidl_pl/images/PL/kw09_trekking_pion_nowy2.jpg"/></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 445, Column 10: ID "med_flash" already defined
    <div id="med_flash" class="imagenoshade" onclick="window.open('http://www.lidl.…

    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 265, Column 10: ID "med_flash" first defined here
    <div id="med_flash" class="" >
  • Error Line 480, Column 89: required attribute "alt" not specified
    …g src="/static_content/lidl_pl/images/PL/kw10_wiosenne_trendy_pion.jpg"/></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 490, Column 10: ID "med_flash" already defined
    <div id="med_flash" class="" onclick="window.open('http://www.lidl.pl/cps/rde/x…

    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 265, Column 10: ID "med_flash" first defined here
    <div id="med_flash" class="" >
  • Error Line 525, Column 108: required attribute "alt" not specified
    …ent/lidl_pl/images/PL/baner_serek_kawa_biszkopty_FOOD_chrupiace_v2.jpg"/></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 535, Column 10: ID "med_flash" already defined
    <div id="med_flash" class="" >

    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 265, Column 10: ID "med_flash" first defined here
    <div id="med_flash" class="" >
  • Error Line 570, Column 84: required attribute "alt" not specified
    …v><img src="/static_content/lidl_pl/images/PL/lidl_ryneczek_jab_01.jpg"/></div>

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

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

  • Warning Line 577, Column 109: cannot generate system identifier for general entity "url"
    …/www.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lidl…

    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 577, Column 109: general entity "url" not defined and no default entity
    …/www.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lidl…

    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 577, Column 112: reference not terminated by REFC delimiter
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lidl_pl…

    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 577, Column 112: reference to external entity in attribute value
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lidl_pl…

    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 577, Column 112: reference to entity "url" for which no system identifier could be generated
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lidl_pl…

    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 577, Column 108: entity was defined here
    …//www.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lid…
  • Warning Line 577, Column 170: cannot generate system identifier for general entity "lnkname"
    …cps/rde/xchg/lidl_pl/hs.xsl/34258.htm&lnkname=SG_maly_procent_1x2*/" id="sp_ou…

    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 577, Column 170: general entity "lnkname" not defined and no default entity
    …cps/rde/xchg/lidl_pl/hs.xsl/34258.htm&lnkname=SG_maly_procent_1x2*/" id="sp_ou…

    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 577, Column 177: reference not terminated by REFC delimiter
    …/xchg/lidl_pl/hs.xsl/34258.htm&lnkname=SG_maly_procent_1x2*/" id="sp_outer_id_…

    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 577, Column 177: reference to external entity in attribute value
    …/xchg/lidl_pl/hs.xsl/34258.htm&lnkname=SG_maly_procent_1x2*/" id="sp_outer_id_…

    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 577, Column 177: reference to entity "lnkname" for which no system identifier could be generated
    …/xchg/lidl_pl/hs.xsl/34258.htm&lnkname=SG_maly_procent_1x2*/" id="sp_outer_id_…

    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 577, Column 169: entity was defined here
    …/cps/rde/xchg/lidl_pl/hs.xsl/34258.htm&lnkname=SG_maly_procent_1x2*/" id="sp_o…
  • Warning Line 577, Column 293: reference not terminated by REFC delimiter
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lidl_pl…

    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 577, Column 293: reference to external entity in attribute value
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lidl_pl…

    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 577, Column 293: reference to entity "url" for which no system identifier could be generated
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lidl_pl…

    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 577, Column 108: entity was defined here
    …//www.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lid…
  • Warning Line 577, Column 358: reference not terminated by REFC delimiter
    …/cps/rde/xchg/lidl_pl/hs.xsl/34258.htm&lnkname=SG_maly_procent_1x2','_self');">

    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 577, Column 358: reference to external entity in attribute value
    …/cps/rde/xchg/lidl_pl/hs.xsl/34258.htm&lnkname=SG_maly_procent_1x2','_self');">

    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 577, Column 358: reference to entity "lnkname" for which no system identifier could be generated
    …/cps/rde/xchg/lidl_pl/hs.xsl/34258.htm&lnkname=SG_maly_procent_1x2','_self');">

    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 577, Column 169: entity was defined here
    …/cps/rde/xchg/lidl_pl/hs.xsl/34258.htm&lnkname=SG_maly_procent_1x2*/" id="sp_o…
  • Error Line 581, Column 96: required attribute "alt" not specified
    …ss=""><img src="/static_content/lidl_pl/images/PL/procent_banerek.jpg"/></div> 

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

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

  • Warning Line 587, Column 114: reference not terminated by REFC delimiter
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lidl_pl…

    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 587, Column 114: reference to external entity in attribute value
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lidl_pl…

    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 587, Column 114: reference to entity "url" for which no system identifier could be generated
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lidl_pl…

    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 577, Column 108: entity was defined here
    …//www.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lid…
  • Warning Line 587, Column 179: reference not terminated by REFC delimiter
    …/xchg/lidl_pl/hs.xsl/34313.htm&lnkname=SG_miska_dla_schroniska_1x2*/" id="sp_o…

    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 587, Column 179: reference to external entity in attribute value
    …/xchg/lidl_pl/hs.xsl/34313.htm&lnkname=SG_miska_dla_schroniska_1x2*/" id="sp_o…

    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 587, Column 179: reference to entity "lnkname" for which no system identifier could be generated
    …/xchg/lidl_pl/hs.xsl/34313.htm&lnkname=SG_miska_dla_schroniska_1x2*/" id="sp_o…

    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 577, Column 169: entity was defined here
    …/cps/rde/xchg/lidl_pl/hs.xsl/34258.htm&lnkname=SG_maly_procent_1x2*/" id="sp_o…
  • Warning Line 587, Column 303: reference not terminated by REFC delimiter
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lidl_pl…

    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 587, Column 303: reference to external entity in attribute value
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lidl_pl…

    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 587, Column 303: reference to entity "url" for which no system identifier could be generated
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lidl_pl…

    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 577, Column 108: entity was defined here
    …//www.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lid…
  • Warning Line 587, Column 368: reference not terminated by REFC delimiter
    …/xchg/lidl_pl/hs.xsl/34313.htm&lnkname=SG_miska_dla_schroniska_1x2','_self');"…

    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 587, Column 368: reference to external entity in attribute value
    …/xchg/lidl_pl/hs.xsl/34313.htm&lnkname=SG_miska_dla_schroniska_1x2','_self');"…

    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 587, Column 368: reference to entity "lnkname" for which no system identifier could be generated
    …/xchg/lidl_pl/hs.xsl/34313.htm&lnkname=SG_miska_dla_schroniska_1x2','_self');"…

    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 577, Column 169: entity was defined here
    …/cps/rde/xchg/lidl_pl/hs.xsl/34258.htm&lnkname=SG_maly_procent_1x2*/" id="sp_o…
  • Error Line 591, Column 105: required attribute "alt" not specified
    …g src="/static_content/lidl_pl/images/PL/zwierzaki_banner_374x166.jpg"/></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 600, Column 10: ID "med_flash" already defined
    <div id="med_flash" class="" onclick="window.open('http://www.lidl.pl/cps/rde/x…

    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 265, Column 10: ID "med_flash" first defined here
    <div id="med_flash" class="" >
  • Error Line 635, Column 86: required attribute "alt" not specified
    …<img src="/static_content/lidl_pl/images/PL/lidl_przepisy_374x166_.jpg"/></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 646, Column 102: required attribute "alt" not specified
    …<img src="/static_content/lidl_pl/images/PL/lidl_iphone_374x166_M.jpg"/></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 652, Column 93: there is no attribute "zIndex"
    …ent/lidl_pl/images/spacer.gif" zIndex="1000" style="width:;height:1238px;" wid…

    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 652, Column 141: required attribute "alt" not specified
    …" style="width:;height:1238px;" width="1px"><!-- Berechnung der Höhe im CMS -->

    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 652, Column 142: end tag for "img" omitted, but OMITTAG NO was specified
    …" style="width:;height:1238px;" width="1px"><!-- Berechnung der Höhe im CMS -->

    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 652, Column 1: start tag was here
    <img name="img_drag_and_drop_footer" src="/static_content/lidl_pl/images/spacer…
  • Error Line 667, Column 8: required attribute "type" not specified
    <script> 

    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 691, Column 24: ID "med_flash" already defined
    <div class="flash" id="med_flash"> 

    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 265, Column 10: ID "med_flash" first defined here
    <div id="med_flash" class="" >
  • Error Line 720, Column 251: invalid comment declaration: found name start character outside comment but inside comment declaration
    …e.jpg" BORDER=0 alt="Teaser"/></a><!--https://www.facebook.com/lidlpolska--></…
  • Info Line 694, Column 5: comment declaration started here
        <!-- 
  • Error Line 720, Column 294: end tag for "script" omitted, but OMITTAG NO was specified
    …" BORDER=0 alt="Teaser"/></a><!--https://www.facebook.com/lidlpolska--></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 693, Column 2: start tag was here
     <script language="JavaScript" type="text/javascript"> 
  • Error Line 724, Column 13: end tag for element "script" which is not open
        </script> 

    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 728, Column 103: there is no attribute "SRC"
    …w.facebook.com/lidlpolska')"><IMG SRC="/static_content/lidl_pl/images/PL/menu_…

    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 728, Column 160: there is no attribute "BORDER"
    …C="/static_content/lidl_pl/images/PL/menu_blue.jpg" BORDER=0 alt="Teaser"/></a>

    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 728, Column 160: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …C="/static_content/lidl_pl/images/PL/menu_blue.jpg" BORDER=0 alt="Teaser"/></a>
  • Error Line 728, Column 166: there is no attribute "alt"
    …C="/static_content/lidl_pl/images/PL/menu_blue.jpg" BORDER=0 alt="Teaser"/></a>

    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 728, Column 175: element "IMG" undefined
    …C="/static_content/lidl_pl/images/PL/menu_blue.jpg" BORDER=0 alt="Teaser"/></a>

    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 732, Column 12: required attribute "type" not specified
        <script>

    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 752, Column 8: required attribute "type" not specified
    <script> 

    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 766, Column 224: reference not terminated by REFC delimiter
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lidl_pl…

    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 766, Column 224: reference to external entity in attribute value
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lidl_pl…

    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 766, Column 224: reference to entity "url" for which no system identifier could be generated
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lidl_pl…

    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 577, Column 108: entity was defined here
    …//www.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lid…
  • Warning Line 766, Column 288: reference not terminated by REFC delimiter
    …e/xchg/lidl_pl/hs.xsl/5698.htm&lnkname= SG_Teaser_zamow_newsletter*/" onclick=…

    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 766, Column 288: reference to external entity in attribute value
    …e/xchg/lidl_pl/hs.xsl/5698.htm&lnkname= SG_Teaser_zamow_newsletter*/" onclick=…

    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 766, Column 288: reference to entity "lnkname" for which no system identifier could be generated
    …e/xchg/lidl_pl/hs.xsl/5698.htm&lnkname= SG_Teaser_zamow_newsletter*/" onclick=…

    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 577, Column 169: entity was defined here
    …/cps/rde/xchg/lidl_pl/hs.xsl/34258.htm&lnkname=SG_maly_procent_1x2*/" id="sp_o…
  • Warning Line 766, Column 394: reference not terminated by REFC delimiter
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lidl_pl…

    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 766, Column 394: reference to external entity in attribute value
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lidl_pl…

    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 766, Column 394: reference to entity "url" for which no system identifier could be generated
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lidl_pl…

    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 577, Column 108: entity was defined here
    …//www.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lid…
  • Warning Line 766, Column 458: reference not terminated by REFC delimiter
    …pl/cps/rde/xchg/lidl_pl/hs.xsl/5698.htm&lnkname= SG_Teaser_zamow_newsletter')">

    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 766, Column 458: reference to external entity in attribute value
    …pl/cps/rde/xchg/lidl_pl/hs.xsl/5698.htm&lnkname= SG_Teaser_zamow_newsletter')">

    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 766, Column 458: reference to entity "lnkname" for which no system identifier could be generated
    …pl/cps/rde/xchg/lidl_pl/hs.xsl/5698.htm&lnkname= SG_Teaser_zamow_newsletter')">

    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 577, Column 169: entity was defined here
    …/cps/rde/xchg/lidl_pl/hs.xsl/34258.htm&lnkname=SG_maly_procent_1x2*/" id="sp_o…
  • Error Line 775, Column 8: required attribute "type" not specified
    <script> 

    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 789, Column 226: reference not terminated by REFC delimiter
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lidl_pl…

    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 789, Column 226: reference to external entity in attribute value
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lidl_pl…

    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 789, Column 226: reference to entity "url" for which no system identifier could be generated
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lidl_pl…

    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 577, Column 108: entity was defined here
    …//www.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lid…
  • Warning Line 789, Column 290: reference not terminated by REFC delimiter
    …e/xchg/lidl_pl/hs.xsl/4222.htm&lnkname= SG_Teaser_znajdz_sklep*/" onclick="ope…

    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 789, Column 290: reference to external entity in attribute value
    …e/xchg/lidl_pl/hs.xsl/4222.htm&lnkname= SG_Teaser_znajdz_sklep*/" onclick="ope…

    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 789, Column 290: reference to entity "lnkname" for which no system identifier could be generated
    …e/xchg/lidl_pl/hs.xsl/4222.htm&lnkname= SG_Teaser_znajdz_sklep*/" onclick="ope…

    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 577, Column 169: entity was defined here
    …/cps/rde/xchg/lidl_pl/hs.xsl/34258.htm&lnkname=SG_maly_procent_1x2*/" id="sp_o…
  • Warning Line 789, Column 392: reference not terminated by REFC delimiter
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lidl_pl…

    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 789, Column 392: reference to external entity in attribute value
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lidl_pl…

    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 789, Column 392: reference to entity "url" for which no system identifier could be generated
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lidl_pl…

    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 577, Column 108: entity was defined here
    …//www.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lid…
  • Warning Line 789, Column 456: reference not terminated by REFC delimiter
    …idl.pl/cps/rde/xchg/lidl_pl/hs.xsl/4222.htm&lnkname= SG_Teaser_znajdz_sklep')">

    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 789, Column 456: reference to external entity in attribute value
    …idl.pl/cps/rde/xchg/lidl_pl/hs.xsl/4222.htm&lnkname= SG_Teaser_znajdz_sklep')">

    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 789, Column 456: reference to entity "lnkname" for which no system identifier could be generated
    …idl.pl/cps/rde/xchg/lidl_pl/hs.xsl/4222.htm&lnkname= SG_Teaser_znajdz_sklep')">

    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 577, Column 169: entity was defined here
    …/cps/rde/xchg/lidl_pl/hs.xsl/34258.htm&lnkname=SG_maly_procent_1x2*/" id="sp_o…
  • Error Line 799, Column 24: ID "med_flash" already defined
    <div class="flash" id="med_flash"> 

    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 265, Column 10: ID "med_flash" first defined here
    <div id="med_flash" class="" >
  • Error Line 828, Column 337: invalid comment declaration: found name start character outside comment but inside comment declaration
    …0.jpg" BORDER=0 alt="Teaser"/></a><!--http://www.etracker.de/lnkcnt.php?et=6Tm…
  • Info Line 802, Column 5: comment declaration started here
        <!-- 
  • Warning Line 828, Column 384: reference not terminated by REFC delimiter
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.kuchnialidla.pl&lnkname=SG_m…

    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 828, Column 384: reference to entity "url" for which no system identifier could be generated
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.kuchnialidla.pl&lnkname=SG_m…

    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 577, Column 108: entity was defined here
    …//www.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lid…
  • Warning Line 828, Column 419: reference not terminated by REFC delimiter
    …url=http://www.kuchnialidla.pl&lnkname=SG_menu_rozwijane_kuchnia_lidla--></div…

    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 828, Column 419: reference to entity "lnkname" for which no system identifier could be generated
    …url=http://www.kuchnialidla.pl&lnkname=SG_menu_rozwijane_kuchnia_lidla--></div…

    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 577, Column 169: entity was defined here
    …/cps/rde/xchg/lidl_pl/hs.xsl/34258.htm&lnkname=SG_maly_procent_1x2*/" id="sp_o…
  • Error Line 828, Column 459: end tag for "script" omitted, but OMITTAG NO was specified
    …l=http://www.kuchnialidla.pl&lnkname=SG_menu_rozwijane_kuchnia_lidla--></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 801, Column 2: start tag was here
     <script language="JavaScript" type="text/javascript"> 
  • Error Line 832, Column 13: end tag for element "script" which is not open
        </script> 

    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.

  • Warning Line 836, Column 102: reference not terminated by REFC delimiter
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.kuchnialidla.pl&lnkname=SG_m…

    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 836, Column 102: reference to external entity in attribute value
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.kuchnialidla.pl&lnkname=SG_m…

    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 836, Column 102: reference to entity "url" for which no system identifier could be generated
    …w.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.kuchnialidla.pl&lnkname=SG_m…

    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 577, Column 108: entity was defined here
    …//www.etracker.de/lnkcnt.php?et=6TmD6m&url=http://www.lidl.pl/cps/rde/xchg/lid…
  • Warning Line 836, Column 137: reference not terminated by REFC delimiter
    …url=http://www.kuchnialidla.pl&lnkname=SG_menu_rozwijane_kuchnia_lidla')"><IMG…

    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 836, Column 137: reference to external entity in attribute value
    …url=http://www.kuchnialidla.pl&lnkname=SG_menu_rozwijane_kuchnia_lidla')"><IMG…

    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 836, Column 137: reference to entity "lnkname" for which no system identifier could be generated
    …url=http://www.kuchnialidla.pl&lnkname=SG_menu_rozwijane_kuchnia_lidla')"><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.

  • Info Line 577, Column 169: entity was defined here
    …/cps/rde/xchg/lidl_pl/hs.xsl/34258.htm&lnkname=SG_maly_procent_1x2*/" id="sp_o…
  • Error Line 836, Column 246: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …tic_content/lidl_pl/images/PL/akordeon_200x270.jpg" BORDER=0 alt="Teaser"/></a>
  • Error Line 836, Column 261: element "IMG" undefined
    …tic_content/lidl_pl/images/PL/akordeon_200x270.jpg" BORDER=0 alt="Teaser"/></a>

    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 840, Column 12: required attribute "type" not specified
        <script>

    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 862, Column 10: end tag for element "div" which is not open
        </div><!--End Wrapper-->

    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 875, Column 13: character data is not allowed here
                |

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 883, Column 13: character data is not allowed here
                |

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 891, Column 13: character data is not allowed here
                |

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 899, Column 13: character data is not allowed here
                |

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 907, Column 13: character data is not allowed here
                |

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 915, Column 13: character data is not allowed here
                |

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 923, Column 13: character data is not allowed here
                |

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 931, Column 13: character data is not allowed here
                |

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 942, Column 6: end tag for element "div" which is not open
    </div><!--End Container-->

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

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

Visitor Analysis

Daily Visitor
  • 15.400 visits
Daily Visitor