merlin.pl

Sklep internetowy Merlin.pl poleca: książki, muzyka, filmy, zabawki, kosmetyki, elektronika, multimedia, sport, prezenty ...

Display Widget for this domain on your website. Click Here
This data was last updated from 03-08-2013 05:56:55  (update).

Overview Info

  • Domain Name
    merlin.pl
  • Favicon
  • Alexa Rank
    #9293
  • Google Page Rank
    PR 6
  • Ip Address
    213.218.116.36
  • Page Size
    110.4 KB
  • Images
    40 GIF, 53 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 0 11 12 0 0

Website Meta Analysis



  • Title
    Sklep internetowy Merlin.pl - filmy, książki, zabawki, muzyka, ...
  • Meta Keyword
    sklep internetowy, merlin.pl, książki, muzyka, kosmetyki, filmy, prezenty, bielizna, zabawki, sport, sklep, multimedia, elektronika, księgarnia, odzież, agd
  • Meta Description
    Sklep internetowy Merlin.pl poleca: książki, muzyka, filmy, zabawki, kosmetyki, elektronika, multimedia, sport, prezenty

Technical Analysis



  • Webserver
    Apache-Coyote/1.1
  • Ip Address
    213.218.116.36
  • Domain Age
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sat, 03 Aug 2013 17:56:52 GMT
  • server: Apache-Coyote/1.1
  • cache-control: no-store
  • pragma: no-cache
  • expires: Sat, 03 Aug 2013 18:11:52 GMT
  • content-type: text/html;charset=iso-8859-2
  • content-language: pl-PL
  • vary: Accept-Encoding
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

DOMAIN NAME: merlin.pl
registrant type: organization
nameservers: ns1.merlin.pl. [213.218.116.41]
ns2.merlin.pl. [213.218.116.42]
created: 1998.04.08 13:00:00
last modified: 2012.03.28 12:02:08
renewal date: 2013.04.07 14:00:00

no option

dnssec: Unsigned


REGISTRAR:
Grupa Onet.pl S.A.
ul. G. Zapolskiej 44
30 - 126 Krakow
Polska/Poland
+48. 12 2600200
email

WHOIS displays data with a delay not exceeding 15 minutes in relation to the .pl Registry system
Registrant data available at http://dns.pl/cgi-bin/en_whois.pl

DNS Analysis


DNS servers
ns1.merlin.pl [213.218.116.41]
ns2.merlin.pl [213.218.116.42]

DNS Records

Answer records
merlin.pl SOA
server: ns1.merlin.pl
email: hostmaster@merlin.pl
serial: 2012112600
refresh: 3600
retry: 900
expire: 2592000
minimum ttl: 600
3600s
merlin.pl MX
preference: 10
exchange: ds.merlin.pl
43200s
merlin.pl TXT spf2.0/pra ?all 43200s
merlin.pl TXT v=spf1 a mx ip4:213.218.116.39 ip4:213.218.116.32 ip4:213.218.116.41 ip4:213.218.116.42 ip4:213.218.116.43 ?all 43200s
merlin.pl NS  ns2.merlin.pl 43200s
merlin.pl NS  ns1.merlin.pl 43200s
merlin.pl A 213.218.116.36 43200s

Authority records

Additional records
ds.merlin.pl A 213.218.116.34 43200s
ns1.merlin.pl A 213.218.116.41 43200s
ns2.merlin.pl A 213.218.116.42 43200s

IP 213.218.116.36 Analysis

  • Country Code
    PL
  • Country Code3
    POL
  • Country Name
    Poland
  • City
    Polska
  • Continent Code
    EU
  • Latitude
    52.6.
  • Longitude
    19.1.
  • No whois ip data for 213.218.116.36

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 60 Errors
  • 18 Warnings
Ratio Text/Html
  • 0.8081304840079253
Message Error
  • Warning Line 6, Column 74: NET-enabling start-tag requires SHORTTAG YES
    <link rel="apple-touch-icon-precomposed" href="/apple-touch-icon-57.png" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 6, Column 75: character data is not allowed here
    <link rel="apple-touch-icon-precomposed" href="/apple-touch-icon-57.png" />

    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.
  • Warning Line 7, Column 62: NET-enabling start-tag requires SHORTTAG YES
    <link rel="apple-touch-icon" href="/apple-touch-icon-57.png" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 8, Column 36: there is no attribute "SIZES"
    <link rel="apple-touch-icon" sizes="72x72" href="/apple-touch-icon-72.png" />

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Warning Line 8, Column 76: NET-enabling start-tag requires SHORTTAG YES
    <link rel="apple-touch-icon" sizes="72x72" href="/apple-touch-icon-72.png" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 9, Column 79: NET-enabling start-tag requires SHORTTAG YES
    <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114.png" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 46, Column 16: there is no attribute "PROPERTY"
    <meta property="fb:admins" content="698079459"><meta property="fb:page_id" cont…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Warning Line 46, Column 99: NET-enabling start-tag requires SHORTTAG YES
    …y="fb:page_id" content="135346702483" /><link rel="canonical" href="http://mer…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 46, Column 100: character data is not allowed here
    …="fb:page_id" content="135346702483" /><link rel="canonical" href="http://merl…

    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 116, Column 78: there is no attribute "AUTOCOMPLETE"
    … alt="wyszukiwana fraza" autocomplete="off" onclick="suggestHoverReset();" onk…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 129, Column 4: end tag for element "P" which is not open
    </p>

    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 391, Column 88: cannot generate system identifier for general entity "sort"
    …1E91871645224DD2C34FA571E.LB7?offer=O&sort=nowosc&set=19272" title="Kryminały"…

    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 391, Column 88: general entity "sort" not defined and no default entity
    …1E91871645224DD2C34FA571E.LB7?offer=O&sort=nowosc&set=19272" title="Kryminały"…

    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.

  • Error Line 391, Column 92: reference to entity "sort" for which no system identifier could be generated
    …871645224DD2C34FA571E.LB7?offer=O&sort=nowosc&set=19272" title="Kryminały"><im…

    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 391, Column 87: entity was defined here
    …B1E91871645224DD2C34FA571E.LB7?offer=O&sort=nowosc&set=19272" title="Kryminały…
  • Warning Line 391, Column 100: cannot generate system identifier for general entity "set"
    …4DD2C34FA571E.LB7?offer=O&sort=nowosc&set=19272" title="Kryminały"><img src="/…

    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 391, Column 100: general entity "set" not defined and no default entity
    …4DD2C34FA571E.LB7?offer=O&sort=nowosc&set=19272" title="Kryminały"><img src="/…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Error Line 391, Column 103: reference to entity "set" for which no system identifier could be generated
    …2C34FA571E.LB7?offer=O&sort=nowosc&set=19272" title="Kryminały"><img src="/ima…

    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 391, Column 99: entity was defined here
    …24DD2C34FA571E.LB7?offer=O&sort=nowosc&set=19272" title="Kryminały"><img src="…
  • Error Line 391, Column 314: reference to entity "sort" for which no system identifier could be generated
    …871645224DD2C34FA571E.LB7?offer=O&sort=nowosc&set=19272" title="Kryminały z 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 391, Column 87: entity was defined here
    …B1E91871645224DD2C34FA571E.LB7?offer=O&sort=nowosc&set=19272" title="Kryminały…
  • Error Line 391, Column 325: reference to entity "set" for which no system identifier could be generated
    …2C34FA571E.LB7?offer=O&sort=nowosc&set=19272" title="Kryminały z rabatem do 40…

    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 391, Column 99: entity was defined here
    …24DD2C34FA571E.LB7?offer=O&sort=nowosc&set=19272" title="Kryminały"><img src="…
  • Error Line 399, Column 92: reference to entity "sort" for which no system identifier could be generated
    …871645224DD2C34FA571E.LB7?offer=O&sort=rank&set=19187" title="Oferta specjalna…

    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 391, Column 87: entity was defined here
    …B1E91871645224DD2C34FA571E.LB7?offer=O&sort=nowosc&set=19272" title="Kryminały…
  • Error Line 399, Column 101: reference to entity "set" for which no system identifier could be generated
    …DD2C34FA571E.LB7?offer=O&sort=rank&set=19187" title="Oferta specjalna"><img sr…

    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 391, Column 99: entity was defined here
    …24DD2C34FA571E.LB7?offer=O&sort=nowosc&set=19272" title="Kryminały"><img src="…
  • Error Line 399, Column 313: reference to entity "sort" for which no system identifier could be generated
    …871645224DD2C34FA571E.LB7?offer=O&sort=rank&set=19187" title="Oferta specjalna…

    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 391, Column 87: entity was defined here
    …B1E91871645224DD2C34FA571E.LB7?offer=O&sort=nowosc&set=19272" title="Kryminały…
  • Error Line 399, Column 322: reference to entity "set" for which no system identifier could be generated
    …DD2C34FA571E.LB7?offer=O&sort=rank&set=19187" title="Oferta specjalna z rabate…

    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 391, Column 99: entity was defined here
    …24DD2C34FA571E.LB7?offer=O&sort=nowosc&set=19272" title="Kryminały"><img src="…
  • Error Line 448, Column 7: character data is not allowed here
    						(wysyłamy w ciągu 24 godz.)

    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 480, Column 7: character data is not allowed here
    						(wysyłamy w ciągu 24 godz.)

    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 512, Column 7: character data is not allowed here
    						(wysyłamy w ciągu 24 godz.)

    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 1794, Column 92: reference to entity "sort" for which no system identifier could be generated
    …871645224DD2C34FA571E.LB7?offer=O&sort=nowosc&set=19265" title="Najlepsze krym…

    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 391, Column 87: entity was defined here
    …B1E91871645224DD2C34FA571E.LB7?offer=O&sort=nowosc&set=19272" title="Kryminały…
  • Error Line 1794, Column 103: reference to entity "set" for which no system identifier could be generated
    …2C34FA571E.LB7?offer=O&sort=nowosc&set=19265" title="Najlepsze kryminały"><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 391, Column 99: entity was defined here
    …24DD2C34FA571E.LB7?offer=O&sort=nowosc&set=19272" title="Kryminały"><img src="…
  • Error Line 1826, Column 92: reference to entity "sort" for which no system identifier could be generated
    …871645224DD2C34FA571E.LB7?offer=O&sort=nowosc&set=19285"><img src="/gfx/banery…

    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 391, Column 87: entity was defined here
    …B1E91871645224DD2C34FA571E.LB7?offer=O&sort=nowosc&set=19272" title="Kryminały…
  • Error Line 1826, Column 103: reference to entity "set" for which no system identifier could be generated
    …2C34FA571E.LB7?offer=O&sort=nowosc&set=19285"><img src="/gfx/banery/07022013wy…

    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 391, Column 99: entity was defined here
    …24DD2C34FA571E.LB7?offer=O&sort=nowosc&set=19272" title="Kryminały"><img src="…
  • Warning Line 1847, Column 27: NET-enabling start-tag requires SHORTTAG YES
    		<div class="roundBottom"/></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1852, Column 90: there is no attribute "TARGET"
    …1E91871645224DD2C34FA571E.LB7" target="_blank"><img src="/img/bok/mail.jpg" al…

    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 1874, Column 29: start tag for "LEGEND" omitted, but its declaration does not permit this
    	Informacje o nowościach,<br>zapowiedziach, promocjach<br>oraz specjalnych raba…
  • Error Line 1875, Column 9: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    	   <div><label for="g_email"><strong>Twój e-mail:</strong></label><br>

    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 1878, Column 19: end tag for "LEGEND" omitted, but its declaration does not permit this
            </fieldset>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 1874, Column 26: start tag was here
    	Informacje o nowościach,<br>zapowiedziach, promocjach<br>oraz specjalnych raba…
  • Error Line 2163, Column 96: end tag for element "A" which is not open
    …th('<a href="'+urlGA+'" class="'+style.replace('linkJS','')+'">'+anchor+'</a>')

    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
  • 10.383 visits

In Page Analysis