Buty & Odzież dla każdego w sklepie internetowym ► ZALANDO: duży wybór, top marki, dostawa gratis! Buty & Odzież w ► ZALANDO ...

zalando.pl
  • Domain Name
    zalando.pl
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #15937
  • Page Size
    91.5 KB
  • Ip Address
    195.71.68.110
  • Heading
    H1: 1, H2: 0, H3: 2, H4: 1, H5: 0, H6: 0
  • Images
    1 GIF, 36 JPG, 0 PNG

Website Meta Analysis

  • Title
    Buty & Odzież dla każdego | Zamów w sklepie internetowym ZALANDO
  • Meta Keyword
    Buty, odzież, obuwie, ubrania, buty damskie, moda męska, akcesoria, sklep internetowy, zakupy online, Zalando
  • Meta Description
    Buty & Odzież dla każdego w sklepie internetowym ► ZALANDO: duży wybór, top marki, dostawa gratis! Buty & Odzież w ► ZALANDO

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    195.71.68.110
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Fri, 01 Mar 2013 05:18:50 GMT
  • server: Apache
  • vary: Host,Accept-Encoding
  • expires: Thu, 01 Jan 1970 00:00:00 GMT
  • cache-control: no-store, no-cache, must-revalidate
  • pragma: no-cache
  • content-language: pl-PL
  • content-encoding: gzip
  • content-length: 22160
  • connection: close
  • content-type: text/html;charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

DOMAIN NAME: zalando.pl
registrant type: organization
nameservers: ns-2.mediaways.net.
ns.mediaways.net.
ns-3.mediaways.net.
created: 2008.08.19 10:27:28
last modified: 2012.08.05 03:22:39
renewal date: 2013.08.19 10:27:28

no option

dnssec: Unsigned

TECHNICAL CONTACT:
company: Robert Gentz
Zalando GmbH
street: Sonnenburger Str. 73
city: 10437 Berlin
location: DE
handle: ks_rzg99_197611
phone: +49.30814590400
last modified: 2011.12.01


REGISTRAR:
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Niemcy/Germany
+49 68949396850
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

IP 195.71.68.110 Analysis

  • Country Code
    DE
  • Country Code3
    DEU
  • Country Name
    Germany
  • City
    Berlin
  • Continent Code
    EU
  • Latitude
    52.5167
  • Longitude
    13.4.
  • No whois ip data for 195.71.68.110

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 42 Errors
  • 12 Warnings
Ratio Text/Html
  • 0.4963559728965481
Message Error
  • Error Line 8, Column 16: there is no attribute "property"
    <meta property="fb:app_id" content="267636633320522" />

    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 70, Column 71: there is no attribute "data-options"
    …ount" class="msgAccount" data-options="account" href="/konto-uzytkownika/">Moj…

    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 190, Column 189: required attribute "alt" not specified
    …_2l_580x530_41_pl.jpg" width="580" height="530" border="0" usemap="#imap_45" />

    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 209, Column 175: required attribute "alt" not specified
    …_2L_200x260_15_pl.jpg" width="200" height="260" border="0" usemap="#imap_58" />

    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 219, Column 180: required attribute "alt" not specified
    …_1L_200x260_26_pl.jpg" width="200" height="260" border="0" usemap="#imap_80" />

    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 229, Column 189: required attribute "alt" not specified
    …_2l_580x530_41_pl.jpg" width="580" height="530" border="0" usemap="#imap_45" />

    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 230, Column 10: ID "imap_45" already defined
    <map id="imap_45" name="imap_45" >

    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 191, Column 10: ID "imap_45" first defined here
    <map id="imap_45" name="imap_45" >
  • Error Line 237, Column 140: required attribute "alt" not specified
    …S Fallbacks Winter/HP/OSM_un_hp_r1.sp_wo_ex_ski_out_fe_1l_200x260_41_pl.jpg" />

    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 239, Column 187: required attribute "alt" not specified
    …_1L_200x260_26_pl.jpg" width="200" height="260" border="0" usemap="#imap_80" />

    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 240, Column 10: ID "imap_80" already defined
    <map id="imap_80" name="imap_80" >

    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 220, Column 10: ID "imap_80" first defined here
    <map id="imap_80" name="imap_80" >
  • Error Line 253, Column 267: required attribute "alt" not specified
    …er/CMSfallbacks_PL/HP/OSM_un_hp_b1.wo_cl_jackets_1l_500x310_CW35_pl.jpg" /></a>

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

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

  • Error Line 258, Column 276: required attribute "alt" not specified
    …_PL/HP/OSM_sh_un_hp_b2.br_me_hp_youturn_ind_1me_1l_240x310_13_gl_pl.jpg" /></a>

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

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

  • Error Line 265, Column 282: required attribute "alt" not specified
    …r/CMSfallbacks_PL/HP/OSM_sh_un_hp_r3.ac_wo_wallets_1L_240x150_26_pl.jpg" /></a>

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

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

  • Error Line 271, Column 264: required attribute "alt" not specified
    …ser/CMSfallbacks_PL/HP/OSM_sh_un_hp_r4.ac_me_belts_1L_240x150_26_pl.jpg" /></a>

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

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

  • Error Line 281, Column 267: required attribute "alt" not specified
    …er/CMSfallbacks_PL/HP/OSM_un_hp_b1.wo_cl_jackets_1l_500x310_CW35_pl.jpg" /></a>

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

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

  • Error Line 282, Column 265: required attribute "alt" not specified
    …_PL/HP/OSM_sh_un_hp_b2.br_me_hp_youturn_ind_1me_1l_240x310_13_gl_pl.jpg" /></a>

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

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

  • Error Line 285, Column 282: required attribute "alt" not specified
    …r/CMSfallbacks_PL/HP/OSM_sh_un_hp_r3.ac_wo_wallets_1L_240x150_26_pl.jpg" /></a>

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

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

  • Error Line 286, Column 264: required attribute "alt" not specified
    …ser/CMSfallbacks_PL/HP/OSM_sh_un_hp_r4.ac_me_belts_1L_240x150_26_pl.jpg" /></a>

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

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

  • Error Line 650, Column 373: there is no attribute "allowTransparency"
    …low:hidden; width:300px; height:258px;" allowTransparency="true"></iframe></li>

    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 800, Column 75: value of attribute "type" cannot be "email"; must be one of "text", "password", "checkbox", "radio", "submit", "reset", "file", "hidden", "image", "button"
    …t id="loginEmail" name="email" value="" class="inputText" type="email" /></div>

    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 853, 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 922, Column 25: an attribute value must be a literal unless it contains only name characters
    document.write('<div id=\"cto_se_7717934_ac\" style=\"display:none\">');

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 922, Column 25: character "\" is not allowed in the value of attribute "id"
    document.write('<div id=\"cto_se_7717934_ac\" style=\"display:none\">');

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

  • Error Line 922, Column 53: an attribute value must be a literal unless it contains only name characters
    document.write('<div id=\"cto_se_7717934_ac\" style=\"display:none\">');

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 922, Column 69: document type does not allow element "div" here
    document.write('<div id=\"cto_se_7717934_ac\" style=\"display:none\">');

    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 923, Column 28: an attribute value must be a literal unless it contains only name characters
    document.write('<div class=\"ctoWidgetServer\">http:\/\/zalandopl.widget.criteo…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Warning Line 923, Column 91: character "<" is the first character of a delimiter but occurred as data
    …class=\"ctoWidgetServer\">http:\/\/zalandopl.widget.criteo.com\/pyz\/<\/div>');

    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 924, Column 28: an attribute value must be a literal unless it contains only name characters
    document.write('<div class=\"ctoDataType\">sendEvent<\/div>');

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Warning Line 924, Column 53: character "<" is the first character of a delimiter but occurred as data
    document.write('<div class=\"ctoDataType\">sendEvent<\/div>');

    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 925, Column 28: an attribute value must be a literal unless it contains only name characters
    document.write('<div class=\"ctoParams\">wi=7717934&pt1=0&pt2=1<\/div>');

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Warning Line 925, Column 53: cannot generate system identifier for general entity "pt1"
    document.write('<div class=\"ctoParams\">wi=7717934&pt1=0&pt2=1<\/div>');

    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 925, Column 53: general entity "pt1" not defined and no default entity
    document.write('<div class=\"ctoParams\">wi=7717934&pt1=0&pt2=1<\/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.

  • Warning Line 925, Column 56: reference not terminated by REFC delimiter
    document.write('<div class=\"ctoParams\">wi=7717934&pt1=0&pt2=1<\/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 925, Column 56: reference to entity "pt1" for which no system identifier could be generated
    document.write('<div class=\"ctoParams\">wi=7717934&pt1=0&pt2=1<\/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 925, Column 52: entity was defined here
    document.write('<div class=\"ctoParams\">wi=7717934&pt1=0&pt2=1<\/div>');
  • Warning Line 925, Column 59: cannot generate system identifier for general entity "pt2"
    document.write('<div class=\"ctoParams\">wi=7717934&pt1=0&pt2=1<\/div>');

    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 925, Column 59: general entity "pt2" not defined and no default entity
    document.write('<div class=\"ctoParams\">wi=7717934&pt1=0&pt2=1<\/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.

  • Warning Line 925, Column 62: reference not terminated by REFC delimiter
    document.write('<div class=\"ctoParams\">wi=7717934&pt1=0&pt2=1<\/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 925, Column 62: reference to entity "pt2" for which no system identifier could be generated
    document.write('<div class=\"ctoParams\">wi=7717934&pt1=0&pt2=1<\/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 925, Column 58: entity was defined here
    document.write('<div class=\"ctoParams\">wi=7717934&pt1=0&pt2=1<\/div>');
  • Warning Line 925, Column 64: character "<" is the first character of a delimiter but occurred as data
    document.write('<div class=\"ctoParams\">wi=7717934&pt1=0&pt2=1<\/div>');

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 926, Column 17: character "<" is the first character of a delimiter but occurred as data
    document.write('<\/div>');

    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 927, Column 9: end tag for "div" omitted, but OMITTAG NO was specified
    </script>

    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 925, Column 17: start tag was here
    document.write('<div class=\"ctoParams\">wi=7717934&pt1=0&pt2=1<\/div>');
  • Error Line 927, Column 9: end tag for "div" omitted, but OMITTAG NO was specified
    </script>

    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 924, Column 17: start tag was here
    document.write('<div class=\"ctoDataType\">sendEvent<\/div>');
  • Error Line 927, Column 9: end tag for "div" omitted, but OMITTAG NO was specified
    </script>

    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 923, Column 17: start tag was here
    document.write('<div class=\"ctoWidgetServer\">http:\/\/zalandopl.widget.criteo…
  • Error Line 927, Column 9: end tag for "div" omitted, but OMITTAG NO was specified
    </script>

    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 922, Column 17: start tag was here
    document.write('<div id=\"cto_se_7717934_ac\" style=\"display:none\">');
  • Error Line 971, Column 77: required attribute "type" not specified
    … language="javascript" src="http://www.everestjs.net/static/st.v2.js"></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 972, Column 30: required attribute "type" not specified
    <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 974, Column 52: cannot generate system identifier for general entity "ev_transid"
    var ef_transaction_properties = "ev_startpage_pl=1&ev_transid=";

    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 974, Column 52: general entity "ev_transid" not defined and no default entity
    var ef_transaction_properties = "ev_startpage_pl=1&ev_transid=";

    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 974, Column 62: reference not terminated by REFC delimiter
    var ef_transaction_properties = "ev_startpage_pl=1&ev_transid=";

    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 974, Column 62: reference to entity "ev_transid" for which no system identifier could be generated
    var ef_transaction_properties = "ev_startpage_pl=1&ev_transid=";

    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 974, Column 51: entity was defined here
    var ef_transaction_properties = "ev_startpage_pl=1&ev_transid=";
  • Warning Line 985, Column 85: reference not terminated by REFC delimiter
    …ch.net/3189/t?ev_startpage_pl=1&ev_transid=' width='1' height='1' /></noscript>

    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 985, Column 85: reference to external entity in attribute value
    …ch.net/3189/t?ev_startpage_pl=1&ev_transid=' width='1' height='1' /></noscript>

    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 985, Column 85: reference to entity "ev_transid" for which no system identifier could be generated
    …ch.net/3189/t?ev_startpage_pl=1&ev_transid=' width='1' height='1' /></noscript>

    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 974, Column 51: entity was defined here
    var ef_transaction_properties = "ev_startpage_pl=1&ev_transid=";
  • Error Line 985, Column 110: required attribute "alt" not specified
    …ch.net/3189/t?ev_startpage_pl=1&ev_transid=' width='1' height='1' /></noscript>

    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
  • 8.283 visits
Daily Visitor