lidl-hellas.gr

Καλώς ήλθατε στη Lidl Ελληνικά Welcome to Lidl Online English ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    lidl-hellas.gr
  • Favicon
  • Alexa Rank
    #42303
  • Google Page Rank
    PR 5
  • Ip Address
    195.143.104.230
  • Page Size
    4.6 KB
  • Images
    0 GIF, 0 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
    LIDL
  • Meta Keyword
  • Meta Description
    Καλώς ήλθατε στη Lidl Ελληνικά Welcome to Lidl Online English

Technical Analysis



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

Hyper Text Transfer Protocol (HTTP) header show data header response from lidl-hellas.gr.

HTML Analysis

  • content-type: text/html;charset=UTF-8
  • server: Microsoft-IIS/7.5
  • x-powered-by: ASP.NET
  • content-length: 5479
  • expires: Mon, 08 Jul 2013 22:57:49 GMT
  • cache-control: max-age=0, no-cache, no-store
  • pragma: no-cache
  • date: Mon, 08 Jul 2013 22:57:49 GMT
  • connection: keep-alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for lidl-hellas.gr

IP 195.143.104.230 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 4 Errors
  • 6 Warnings
Ratio Text/Html
  • 0.3097814555484829
Message Error
  • Warning Line 95, Column 134: cannot generate system identifier for general entity "address"
    ….xsl/cookie_save.xml?rdeLocaleAttr=el&address=/cps/rde/xchg/SID-0CF53C32-9DCC3…

    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 "&" (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 æ 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 95, Column 134: general entity "address" not defined and no default entity
    ….xsl/cookie_save.xml?rdeLocaleAttr=el&address=/cps/rde/xchg/SID-0CF53C32-9DCC3…

    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 95, Column 141: reference not terminated by REFC delimiter
    …okie_save.xml?rdeLocaleAttr=el&address=/cps/rde/xchg/SID-0CF53C32-9DCC30B6/lid…

    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 95, Column 141: reference to external entity in attribute value
    …okie_save.xml?rdeLocaleAttr=el&address=/cps/rde/xchg/SID-0CF53C32-9DCC30B6/lid…

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

  • Error Line 95, Column 141: reference to entity "address" for which no system identifier could be generated
    …okie_save.xml?rdeLocaleAttr=el&address=/cps/rde/xchg/SID-0CF53C32-9DCC30B6/lid…

    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 95, Column 133: entity was defined here
    …s.xsl/cookie_save.xml?rdeLocaleAttr=el&address=/cps/rde/xchg/SID-0CF53C32-9DCC…
  • Warning Line 103, Column 141: reference not terminated by REFC delimiter
    …okie_save.xml?rdeLocaleAttr=az&address=/cps/rde/xchg/SID-0CF53C32-9DCC30B6/lid…

    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 103, Column 141: reference to external entity in attribute value
    …okie_save.xml?rdeLocaleAttr=az&address=/cps/rde/xchg/SID-0CF53C32-9DCC30B6/lid…

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

  • Error Line 103, Column 141: reference to entity "address" for which no system identifier could be generated
    …okie_save.xml?rdeLocaleAttr=az&address=/cps/rde/xchg/SID-0CF53C32-9DCC30B6/lid…

    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 95, Column 133: entity was defined here
    …s.xsl/cookie_save.xml?rdeLocaleAttr=el&address=/cps/rde/xchg/SID-0CF53C32-9DCC…
  • Error Line 113, Column 14: end tag for element "div" which is not open
            </div>

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

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

Visitor Analysis

Daily Visitor
  • 3.500 visits

In Page Analysis