Oficiální eshop skupiny Nova ...

yoopy.cz
  • Domain Name
    yoopy.cz
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #262507
  • Page Size
    98.7 KB
  • Ip Address
    88.86.114.5
  • Heading
    H1: 1, H2: 7, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 36 JPG, 18 PNG

Website Meta Analysis

  • Title
    Hlavní stránka - Yoopy
  • Meta Keyword
    Yoopy.cz
  • Meta Description
    Oficiální eshop skupiny Nova

Technical Analysis

  • Webserver
    nginx/1.2.4
  • Ip Address
    88.86.114.5
  • Domain Age
  • Javascript Library
    jquery, prototype
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from yoopy.cz.

HTML Analysis

  • server: nginx/1.2.4
  • date: Sat, 31 Aug 2013 08:52:42 GMT
  • content-type: text/html; charset=UTF-8
  • content-length: 14123
  • connection: keep-alive
  • x-powered-by: PHP/5.3.3-7+squeeze15
  • vary: Accept-Encoding
  • content-encoding: gzip
  • accept-ranges: bytes
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • expires: Mon, 31 Mar 2008 10:00:00 GMT
  • age: 0
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for yoopy.cz

DNS Analysis


DNS servers
ns1.cme-devel.net [91.202.65.240]
ns2.cme-devel.net [88.86.114.150]

DNS Records

Answer records
yoopy.cz SOA
server: ns1.cme-devel.net
email: dns@cme-devel.net
serial: 2012121000
refresh: 28800
retry: 10800
expire: 2419200
minimum ttl: 43200
3600s
yoopy.cz NS  ns1.cme-devel.net 3600s
yoopy.cz NS  ns2.cme-devel.net 3600s
yoopy.cz MX
preference: 10
exchange: mail.services.jyxo.com
3600s
yoopy.cz A 88.86.114.233 3600s

Authority records

Additional records
ns1.cme-devel.net A 91.202.65.240 3600s
ns2.cme-devel.net A 88.86.114.150 3600s
mail.services.jyxo.com A 46.234.102.230 3600s

IP 88.86.114.5 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 30 Errors
  • 6 Warnings
Ratio Text/Html
  • 0.6445946480880373
Message Error
  • Error Line 68, Column 94: value of attribute "method" cannot be "GET"; must be one of "get", "post"
    …opy_header_search_form" action="http://obchod.yoopy.cz/index.php" method="GET">

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 288, Column 174: required attribute "alt" not specified
    …43.html"><img src="http://obchod.yoopy.cz/foto/velke2/CET-243.jpg" /></a></div>

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

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

  • Error Line 324, Column 175: required attribute "alt" not specified
    …-239.html"><img src="http://obchod.yoopy.cz/foto/male/CET-239.jpg" /></a></div>

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

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

  • Error Line 344, Column 166: required attribute "alt" not specified
    …-003.html"><img src="http://obchod.yoopy.cz/foto/male/CET-003.jpg" /></a></div>

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

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

  • Error Line 364, Column 162: required attribute "alt" not specified
    …-014.html"><img src="http://obchod.yoopy.cz/foto/male/CET-014.jpg" /></a></div>

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

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

  • Error Line 384, Column 160: required attribute "alt" not specified
    …-004.html"><img src="http://obchod.yoopy.cz/foto/male/CET-004.jpg" /></a></div>

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

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

  • Error Line 422, Column 156: required attribute "alt" not specified
    …6.html"><img src="http://obchod.yoopy.cz/foto/stredni/CET-026.jpg" /></a></div>

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

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

  • Error Line 444, Column 163: required attribute "alt" not specified
    …5.html"><img src="http://obchod.yoopy.cz/foto/stredni/CET-005.jpg" /></a></div>

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

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

  • Error Line 468, Column 155: required attribute "alt" not specified
    …7.html"><img src="http://obchod.yoopy.cz/foto/stredni/CET-017.jpg" /></a></div>

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

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

  • Error Line 490, Column 181: required attribute "alt" not specified
    …8.html"><img src="http://obchod.yoopy.cz/foto/stredni/CET-008.jpg" /></a></div>

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

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

  • Error Line 512, Column 187: required attribute "alt" not specified
    …3.html"><img src="http://obchod.yoopy.cz/foto/stredni/CET-083.jpg" /></a></div>

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

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

  • Error Line 534, Column 163: required attribute "alt" not specified
    …3.html"><img src="http://obchod.yoopy.cz/foto/stredni/CET-013.jpg" /></a></div>

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

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

  • Error Line 600, Column 38: end tag for element "span" which is not open
            <h3><span>Služby</span></span></h3>

    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 644, Column 86: cannot generate system identifier for general entity "pf"
    …hotely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span class='imageSpa…

    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 644, Column 86: general entity "pf" not defined and no default entity
    …hotely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span class='imageSpa…

    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 644, Column 88: reference not terminated by REFC delimiter
    …tely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span class='imageSpan'…

    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 644, Column 88: reference to external entity in attribute value
    …tely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span class='imageSpan'…

    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 644, Column 88: reference to entity "pf" for which no system identifier could be generated
    …tely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span class='imageSpan'…

    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 644, Column 85: entity was defined here
    …/hotely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span class='imageSp…
  • Warning Line 644, Column 91: cannot generate system identifier for general entity "pt"
    …tely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span class='imageSpan'>

    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 644, Column 91: general entity "pt" not defined and no default entity
    …tely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span class='imageSpan'>

    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 644, Column 93: reference not terminated by REFC delimiter
    …tely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span class='imageSpan'>

    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 644, Column 93: reference to external entity in attribute value
    …tely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span class='imageSpan'>

    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 644, Column 93: reference to entity "pt" for which no system identifier could be generated
    …tely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span class='imageSpan'>

    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 644, Column 90: entity was defined here
    …tely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span class='imageSpan'>
  • Warning Line 644, Column 99: cannot generate system identifier for general entity "ur"
    …tely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span class='imageSpan'>

    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 644, Column 99: general entity "ur" not defined and no default entity
    …tely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span class='imageSpan'>

    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 644, Column 101: reference not terminated by REFC delimiter
    …tely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span class='imageSpan'>

    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 644, Column 101: reference to external entity in attribute value
    …tely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span class='imageSpan'>

    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 644, Column 101: reference to entity "ur" for which no system identifier could be generated
    …tely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span class='imageSpan'>

    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 644, Column 98: entity was defined here
    …tely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span class='imageSpan'>
  • Warning Line 649, Column 77: reference not terminated by REFC delimiter
    …otely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0">Ubytování v ČR</a></h4>

    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 649, Column 77: reference to external entity in attribute value
    …otely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0">Ubytování v ČR</a></h4>

    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 649, Column 77: reference to entity "pf" for which no system identifier could be generated
    …otely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0">Ubytování v ČR</a></h4>

    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 644, Column 85: entity was defined here
    …/hotely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span class='imageSp…
  • Warning Line 649, Column 82: reference not terminated by REFC delimiter
    …otely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0">Ubytování v ČR</a></h4>

    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 649, Column 82: reference to external entity in attribute value
    …otely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0">Ubytování v ČR</a></h4>

    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 649, Column 82: reference to entity "pt" for which no system identifier could be generated
    …otely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0">Ubytování v ČR</a></h4>

    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 644, Column 90: entity was defined here
    …tely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span class='imageSpan'>
  • Warning Line 649, Column 90: reference not terminated by REFC delimiter
    …otely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0">Ubytování v ČR</a></h4>

    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 649, Column 90: reference to external entity in attribute value
    …otely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0">Ubytování v ČR</a></h4>

    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 649, Column 90: reference to entity "ur" for which no system identifier could be generated
    …otely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0">Ubytování v ČR</a></h4>

    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 644, Column 98: entity was defined here
    …tely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span class='imageSpan'>
  • Warning Line 651, Column 98: reference not terminated by REFC delimiter
    …tely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span>Zobrazit</span><s…

    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 651, Column 98: reference to external entity in attribute value
    …tely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span>Zobrazit</span><s…

    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 651, Column 98: reference to entity "pf" for which no system identifier could be generated
    …tely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span>Zobrazit</span><s…

    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 644, Column 85: entity was defined here
    …/hotely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span class='imageSp…
  • Warning Line 651, Column 103: reference not terminated by REFC delimiter
    …vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span>Zobrazit</span><span c…

    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 651, Column 103: reference to external entity in attribute value
    …vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span>Zobrazit</span><span c…

    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 651, Column 103: reference to entity "pt" for which no system identifier could be generated
    …vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span>Zobrazit</span><span c…

    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 644, Column 90: entity was defined here
    …tely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span class='imageSpan'>
  • Warning Line 651, Column 111: reference not terminated by REFC delimiter
    ….cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span>Zobrazit</span><span class="ra…

    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 651, Column 111: reference to external entity in attribute value
    ….cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span>Zobrazit</span><span class="ra…

    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 651, Column 111: reference to entity "ur" for which no system identifier could be generated
    ….cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span>Zobrazit</span><span class="ra…

    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 644, Column 98: entity was defined here
    …tely.vybereme.cz/hotely/search/#a=0&pf=0&pt=5000&ur=0"><span class='imageSpan'>
  • Error Line 700, Column 148: required attribute "alt" not specified
    …91476"><img src="http://www.slevuska.cz/pictures/img/hlavni01.jpg" /></a></div>

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

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

  • Error Line 732, Column 159: required attribute "alt" not specified
    …rc="http://www.slever.cz/files/actions/-332-1361878854sperky7.jpg" /></a></div>

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

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

  • Error Line 764, Column 155: required attribute "alt" not specified
    …mg src="http://www.slever.cz/files/actions/-332-1361890557caj.jpg" /></a></div>

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

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

  • Error Line 796, Column 158: required attribute "alt" not specified
    …rc="http://www.jooka.cz/public/offers_photos/big/side-1000433.png" /></a></div>

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

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

  • Error Line 828, Column 180: required attribute "alt" not specified
    …zbozomat.cz/obrazek/24959-neoprenovy-pas-na-hubnuti-2_640x640.jpg" /></a></div>

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

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

  • Error Line 860, Column 152: required attribute "alt" not specified
    …68"><img src="http://www.zapakatel.cz/static/deal/81048-9446b.jpg" /></a></div>

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

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

Visitor Analysis

Daily Visitor
  • 665 visits