Ünlü markaların online ayakkabı satışı. Ücretsiz kargo, 365 gün iade ve 7/24 müşteri desteğiyle hizmetinizde. ...

zizigo.com
  • Domain Name
    zizigo.com
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #30833
  • Page Size
    56.2 KB
  • Ip Address
    212.68.50.33
  • Heading
    H1: 0, H2: 6, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    2 GIF, 13 JPG, 14 PNG

Website Meta Analysis

  • Title
    Zizigo - Binlerce Ayakkabı, Yüzlerce Marka - Ücretsiz Kargo
  • Meta Keyword
    zizigo, online ayakkabı mağazası, online ayakkabı satın al, ayakkabı modelleri, terlik modelleri, sandalet modelleri
  • Meta Description
    Ünlü markaların online ayakkabı satışı. Ücretsiz kargo, 365 gün iade ve 7/24 müşteri desteğiyle hizmetinizde.

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    212.68.50.33
  • Domain Age
    2 Years, 4 Months, 28 days.
  • Javascript Library
    jquery, prototype
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from zizigo.com.

HTML Analysis

  • age: 291
  • date: Thu, 28 Feb 2013 18:58:24 GMT
  • cache-control: max-age=300
  • content-length: 15961
  • connection: Keep-Alive
  • via: NS-CACHE-9.2: 1
  • etag: "KXOGBGOLJJLVSQRRX"
  • server: nginx
  • content-type: text/html; charset=UTF-8
  • x-powered-by: PHP/5.3.10-1ubuntu3.1
  • x-nscache: yes
  • content-encoding: gzip
  • x-newns: True
  • x-google-cache-control: remote-fetch
No data whois for zizigo.com

IP 212.68.50.33 Analysis

  • Country Code
    TR
  • Country Code3
    TUR
  • Country Name
    Turkey
  • City
    EU
  • Continent Code
    39° North
  • Latitude
    35.
  • Longitude
  • No whois ip data for 212.68.50.33

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 105 Errors
  • 35 Warnings
Ratio Text/Html
  • 0.5233101244942961
Message Error
  • Error Line 8, Column 20: there is no attribute "property"
        <meta property="og:type" content="website"/>

    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 73, Column 26: document type does not allow element "div" here; assuming missing "object" start-tag
    <div style="display:none">
  • Warning Line 88, Column 144: cannot generate system identifier for general entity "label"
    …wthroughconversion/981879069/?value=0&label=ZMnlCNulpQMQnZKZ1AM&guid=ON&script…

    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 88, Column 144: general entity "label" not defined and no default entity
    …wthroughconversion/981879069/?value=0&label=ZMnlCNulpQMQnZKZ1AM&guid=ON&script…

    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 88, Column 149: reference not terminated by REFC delimiter
    …oughconversion/981879069/?value=0&label=ZMnlCNulpQMQnZKZ1AM&guid=ON&script=0"/>

    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 88, Column 149: reference to external entity in attribute value
    …oughconversion/981879069/?value=0&label=ZMnlCNulpQMQnZKZ1AM&guid=ON&script=0"/>

    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 88, Column 149: reference to entity "label" for which no system identifier could be generated
    …oughconversion/981879069/?value=0&label=ZMnlCNulpQMQnZKZ1AM&guid=ON&script=0"/>

    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 88, Column 143: entity was defined here
    …ewthroughconversion/981879069/?value=0&label=ZMnlCNulpQMQnZKZ1AM&guid=ON&scrip…
  • Warning Line 88, Column 170: cannot generate system identifier for general entity "guid"
    …oughconversion/981879069/?value=0&label=ZMnlCNulpQMQnZKZ1AM&guid=ON&script=0"/>

    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 88, Column 170: general entity "guid" not defined and no default entity
    …oughconversion/981879069/?value=0&label=ZMnlCNulpQMQnZKZ1AM&guid=ON&script=0"/>

    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 88, Column 174: reference not terminated by REFC delimiter
    …oughconversion/981879069/?value=0&label=ZMnlCNulpQMQnZKZ1AM&guid=ON&script=0"/>

    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 88, Column 174: reference to external entity in attribute value
    …oughconversion/981879069/?value=0&label=ZMnlCNulpQMQnZKZ1AM&guid=ON&script=0"/>

    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 88, Column 174: reference to entity "guid" for which no system identifier could be generated
    …oughconversion/981879069/?value=0&label=ZMnlCNulpQMQnZKZ1AM&guid=ON&script=0"/>

    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 88, Column 169: entity was defined here
    …oughconversion/981879069/?value=0&label=ZMnlCNulpQMQnZKZ1AM&guid=ON&script=0"/>
  • Warning Line 88, Column 178: cannot generate system identifier for general entity "script"
    …oughconversion/981879069/?value=0&label=ZMnlCNulpQMQnZKZ1AM&guid=ON&script=0"/>

    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 88, Column 178: general entity "script" not defined and no default entity
    …oughconversion/981879069/?value=0&label=ZMnlCNulpQMQnZKZ1AM&guid=ON&script=0"/>

    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 88, Column 184: reference not terminated by REFC delimiter
    …oughconversion/981879069/?value=0&label=ZMnlCNulpQMQnZKZ1AM&guid=ON&script=0"/>

    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 88, Column 184: reference to external entity in attribute value
    …oughconversion/981879069/?value=0&label=ZMnlCNulpQMQnZKZ1AM&guid=ON&script=0"/>

    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 88, Column 184: reference to entity "script" for which no system identifier could be generated
    …oughconversion/981879069/?value=0&label=ZMnlCNulpQMQnZKZ1AM&guid=ON&script=0"/>

    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 88, Column 177: entity was defined here
    …oughconversion/981879069/?value=0&label=ZMnlCNulpQMQnZKZ1AM&guid=ON&script=0"/>
  • Error Line 95, Column 41: document type does not allow element "meta" here
    <meta property="ct:page" content="home"/>

    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 114, 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 133, Column 7: end tag for "object" omitted, but OMITTAG NO was specified
    </head>

    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 73, Column 1: start tag was here
    <div style="display:none">
  • Error Line 297, Column 17: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<table border=0 cellpadding=0 cellspacing=0>
  • Error Line 297, Column 31: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<table border=0 cellpadding=0 cellspacing=0>
  • Error Line 297, Column 45: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<table border=0 cellpadding=0 cellspacing=0>
  • Error Line 300, Column 20: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    					<table border=0 cellpadding=0 cellspacing=0>
  • Error Line 300, Column 34: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    					<table border=0 cellpadding=0 cellspacing=0>
  • Error Line 300, Column 48: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    					<table border=0 cellpadding=0 cellspacing=0>
  • Error Line 302, Column 77: syntax of attribute value does not conform to declared value
    							<td><input type="radio" name="gender" id="female" value="2" checked="">

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 302, Column 77: value of attribute "checked" cannot be ""; must be one of "checked"
    							<td><input type="radio" name="gender" id="female" value="2" checked="">

    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 302, Column 79: end tag for "input" omitted, but OMITTAG NO was specified
    							<td><input type="radio" name="gender" id="female" value="2" checked="">

    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 302, Column 12: start tag was here
    							<td><input type="radio" name="gender" id="female" value="2" checked="">
  • Error Line 303, Column 152: required attribute "alt" not specified
    …ontend/coolshoes/zizigo/images/zizigo_signup_fm.gif" class="pt3"/></label></td>

    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 304, Column 18: there is no attribute "width"
    							<td width="10"></td>

    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 306, Column 63: end tag for "input" omitted, but OMITTAG NO was specified
    								<input type="radio" name="gender" id="male" value="1">

    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 306, Column 9: start tag was here
    								<input type="radio" name="gender" id="male" value="1">
  • Error Line 307, Column 149: required attribute "alt" not specified
    …rontend/coolshoes/zizigo/images/zizigo_signup_m.gif" class="pt3"/></label></td>

    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 313, Column 15: there is no attribute "height"
    			<tr height="10"></tr>

    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 313, Column 24: end tag for "tr" which is not finished
    			<tr height="10"></tr>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 316, Column 95: end tag for "input" omitted, but OMITTAG NO was specified
    …                     <input type="hidden" id="ref" name="ref" value="Lightbox">

    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 316, Column 37: start tag was here
                                        <input type="hidden" id="ref" name="ref" va…
  • Error Line 378, Column 68: document type does not allow element "a" here; assuming missing "li" start-tag
    …href="https://www.facebook.com/zizigo"><li class="top-link-social-f top-link-s…
  • Error Line 378, Column 118: document type does not allow element "li" here
    …acebook.com/zizigo"><li class="top-link-social-f top-link-social-pad"></li></a>

    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 379, Column 112: document type does not allow element "li" here
    …twitter.com/zizigo"><li class="top-link-social-t top-link-social-pad"></li></a>

    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 380, Column 138: document type does not allow element "li" here
    …018266578296/posts"><li class="top-link-social-g top-link-social-pad"></li></a>

    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 381, Column 41: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    …  <li id="register-link" class="first"><a rel="nofollow" href="https://www.ziz…

    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 382, Column 26: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
        <li id="account-link"><a rel="nofollow" href="https://www.zizigo.com/custom…

    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 383, Column 49: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    …="checkout-link" style="display:none;"><a rel="nofollow" href="https://www.ziz…

    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 384, Column 37: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
        <li id="login-link" class="last"><a rel="nofollow" href="https://www.zizigo…

    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 385, Column 47: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    …id="logout-link" style="display:none;"><a rel="nofollow" href="https://www.ziz…

    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 386, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 378, Column 2: start tag was here
    	<a class="top-social-links" href="https://www.facebook.com/zizigo"><li class="…
  • Error Line 387, 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 608, Column 47: document type does not allow element "style" here
                            <style type="text/css">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 622, Column 155: document type does not allow element "link" here
    …rontend/coolshoes/zizigo/css/nivo-slider.css" type="text/css" media="screen" />

    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).

  • Warning Line 636, Column 55: cannot generate system identifier for general entity "order"
        <a href="http://www.zizigo.com/firsatlar?dir=desc&order=position">

    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 636, Column 55: general entity "order" not defined and no default entity
        <a href="http://www.zizigo.com/firsatlar?dir=desc&order=position">

    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 636, Column 60: reference not terminated by REFC delimiter
        <a href="http://www.zizigo.com/firsatlar?dir=desc&order=position">

    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 636, Column 60: reference to external entity in attribute value
        <a href="http://www.zizigo.com/firsatlar?dir=desc&order=position">

    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 636, Column 60: reference to entity "order" for which no system identifier could be generated
        <a href="http://www.zizigo.com/firsatlar?dir=desc&order=position">

    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 636, Column 54: entity was defined here
        <a href="http://www.zizigo.com/firsatlar?dir=desc&order=position">
  • Error Line 732, Column 23: document type does not allow element "style" here
    <style type="text/css">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 745, Column 22: required attribute "id" not specified
    <map name="bannermap">

    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 746, Column 100: required attribute "alt" not specified
    …ords="7,55,88,80" href="http://www.zizigo.com/pazar-temizligi?shoe_size=130" />

    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 747, Column 102: required attribute "alt" not specified
    …ds="98,56,176,81" href="http://www.zizigo.com/pazar-temizligi?shoe_size=132" />

    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 748, Column 101: required attribute "alt" not specified
    …rds="9,86,87,106" href="http://www.zizigo.com/pazar-temizligi?shoe_size=133" />

    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 749, Column 103: required attribute "alt" not specified
    …s="98,86,178,108" href="http://www.zizigo.com/pazar-temizligi?shoe_size=131" />

    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 750, Column 103: required attribute "alt" not specified
    …s="10,112,90,135" href="http://www.zizigo.com/pazar-temizligi?shoe_size=136" />

    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 751, Column 104: required attribute "alt" not specified
    …="99,113,177,135" href="http://www.zizigo.com/pazar-temizligi?shoe_size=144" />

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

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

  • Error Line 752, Column 102: required attribute "alt" not specified
    …ds="8,139,88,163" href="http://www.zizigo.com/pazar-temizligi?shoe_size=145" />

    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 753, Column 104: required attribute "alt" not specified
    …="99,140,177,165" href="http://www.zizigo.com/pazar-temizligi?shoe_size=146" />

    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 754, Column 103: required attribute "alt" not specified
    …s="11,168,90,191" href="http://www.zizigo.com/pazar-temizligi?shoe_size=147" />

    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 755, Column 105: required attribute "alt" not specified
    …100,169,176,192" href="http://www.zizigo.com/pazar-temizligi?shoe_size=148" /> 

    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 768, Column 66: reference not terminated by REFC delimiter
    	<a href="http://www.zizigo.com/markalar/fredperry?dir=desc&order=position">

    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 768, Column 66: reference to external entity in attribute value
    	<a href="http://www.zizigo.com/markalar/fredperry?dir=desc&order=position">

    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 768, Column 66: reference to entity "order" for which no system identifier could be generated
    	<a href="http://www.zizigo.com/markalar/fredperry?dir=desc&order=position">

    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 636, Column 54: entity was defined here
        <a href="http://www.zizigo.com/firsatlar?dir=desc&order=position">
  • Warning Line 772, Column 69: reference not terminated by REFC delimiter
    	<a href="http://www.zizigo.com/markalar/pierrecardin?dir=desc&order=position">

    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 772, Column 69: reference to external entity in attribute value
    	<a href="http://www.zizigo.com/markalar/pierrecardin?dir=desc&order=position">

    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 772, Column 69: reference to entity "order" for which no system identifier could be generated
    	<a href="http://www.zizigo.com/markalar/pierrecardin?dir=desc&order=position">

    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 636, Column 54: entity was defined here
        <a href="http://www.zizigo.com/firsatlar?dir=desc&order=position">
  • Warning Line 776, Column 64: reference not terminated by REFC delimiter
    	<a href="http://www.zizigo.com/markalar/lacoste?dir=desc&order=position ">

    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 776, Column 64: reference to external entity in attribute value
    	<a href="http://www.zizigo.com/markalar/lacoste?dir=desc&order=position ">

    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 776, Column 64: reference to entity "order" for which no system identifier could be generated
    	<a href="http://www.zizigo.com/markalar/lacoste?dir=desc&order=position ">

    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 636, Column 54: entity was defined here
        <a href="http://www.zizigo.com/firsatlar?dir=desc&order=position">
  • Warning Line 780, Column 57: reference not terminated by REFC delimiter
    	<a href="http://www.zizigo.com/kadin/bot?dir=desc&order=position">

    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 780, Column 57: reference to external entity in attribute value
    	<a href="http://www.zizigo.com/kadin/bot?dir=desc&order=position">

    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 780, Column 57: reference to entity "order" for which no system identifier could be generated
    	<a href="http://www.zizigo.com/kadin/bot?dir=desc&order=position">

    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 636, Column 54: entity was defined here
        <a href="http://www.zizigo.com/firsatlar?dir=desc&order=position">
  • Warning Line 784, Column 53: reference not terminated by REFC delimiter
    	<a href="http://www.zizigo.com/canta?dir=desc&order=position">

    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 784, Column 53: reference to external entity in attribute value
    	<a href="http://www.zizigo.com/canta?dir=desc&order=position">

    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 784, Column 53: reference to entity "order" for which no system identifier could be generated
    	<a href="http://www.zizigo.com/canta?dir=desc&order=position">

    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 636, Column 54: entity was defined here
        <a href="http://www.zizigo.com/firsatlar?dir=desc&order=position">
  • Warning Line 788, Column 60: reference not terminated by REFC delimiter
    	<a href="http://www.zizigo.com/kadin/gunluk?dir=desc&order=position">

    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 788, Column 60: reference to external entity in attribute value
    	<a href="http://www.zizigo.com/kadin/gunluk?dir=desc&order=position">

    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 788, Column 60: reference to entity "order" for which no system identifier could be generated
    	<a href="http://www.zizigo.com/kadin/gunluk?dir=desc&order=position">

    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 636, Column 54: entity was defined here
        <a href="http://www.zizigo.com/firsatlar?dir=desc&order=position">
  • Error Line 791, Column 92: there is no attribute "wid"
    …                                  <div class="convertale_widget" wid="8"></div>

    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 251: required attribute "alt" not specified
    …ge/101x100/9df78eab33525d08d6e5fb8d27136e95/1/3/135588_01.JPG_2.jpg"/></a></li>

    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 810, Column 111: there is no attribute "href"
    …                        <fb:like href="http://www.zizigo.com/calvina-661033" s…

    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 810, Column 155: there is no attribute "send"
    …//www.zizigo.com/calvina-661033" send="false" show_faces="false" layout="butto…

    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 810, Column 174: there is no attribute "show_faces"
    …lvina-661033" send="false" show_faces="false" layout="button_count" height="30…

    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 810, Column 189: there is no attribute "layout"
    …end="false" show_faces="false" layout="button_count" height="30" font=""></fb:…

    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 810, Column 211: there is no attribute "height"
    …"false" show_faces="false" layout="button_count" height="30" font=""></fb:like>

    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 810, Column 221: there is no attribute "font"
    …"false" show_faces="false" layout="button_count" height="30" font=""></fb:like>

    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 810, Column 223: element "fb:like" undefined
    …"false" show_faces="false" layout="button_count" height="30" font=""></fb:like>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 817, Column 269: required attribute "alt" not specified
    …age/101x100/9df78eab33525d08d6e5fb8d27136e95/3/6/36881_01.JPG_2.jpg"/></a></li>

    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 827, Column 242: element "fb:like" undefined
    …"false" show_faces="false" layout="button_count" height="30" font=""></fb:like>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 834, Column 268: required attribute "alt" not specified
    …ge/101x100/9df78eab33525d08d6e5fb8d27136e95/4/2/42063_01.JPG_11.jpg"/></a></li>

    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 842, Column 240: element "fb:like" undefined
    …"false" show_faces="false" layout="button_count" height="30" font=""></fb:like>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 849, Column 263: required attribute "alt" not specified
    …age/101x100/9df78eab33525d08d6e5fb8d27136e95/1/3/13055_01.jpg_2.jpg"/></a></li>

    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 859, Column 236: element "fb:like" undefined
    …"false" show_faces="false" layout="button_count" height="30" font=""></fb:like>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 866, Column 274: required attribute "alt" not specified
    …age/101x100/9df78eab33525d08d6e5fb8d27136e95/4/2/42409_01.jpg_1.jpg"/></a></li>

    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 876, Column 247: element "fb:like" undefined
    …"false" show_faces="false" layout="button_count" height="30" font=""></fb:like>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 883, Column 274: required attribute "alt" not specified
    …image/101x100/9df78eab33525d08d6e5fb8d27136e95/1/5/15516_01.jpg.jpg"/></a></li>

    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 893, Column 249: element "fb:like" undefined
    …"false" show_faces="false" layout="button_count" height="30" font=""></fb:like>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 900, Column 274: required attribute "alt" not specified
    …age/101x100/9df78eab33525d08d6e5fb8d27136e95/1/7/17624_01.jpg_1.jpg"/></a></li>

    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 910, Column 247: element "fb:like" undefined
    …"false" show_faces="false" layout="button_count" height="30" font=""></fb:like>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 917, Column 256: required attribute "alt" not specified
    …image/101x100/9df78eab33525d08d6e5fb8d27136e95/2/2/22045_01.jpg.jpg"/></a></li>

    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 925, Column 231: element "fb:like" undefined
    …"false" show_faces="false" layout="button_count" height="30" font=""></fb:like>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 937, Column 110: there is no attribute "align"
    …edia.zizigo.com/cmedia/cache-102/media/ilovezizigo.png" alt="" align="right" />

    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 950, Column 73: document type does not allow element "div" here
            document.write('<div id="cto_se_7715380_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).

  • Warning Line 951, Column 96: character "<" is the first character of a delimiter but occurred as data
    …iv class="ctoWidgetServer">http:\/\/zizigotr.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.
  • Warning Line 952, Column 59: 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.
  • Warning Line 953, Column 59: cannot generate system identifier for general entity "pt1"
            document.write('<div class="ctoParams">wi=7715380&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 953, Column 59: general entity "pt1" not defined and no default entity
            document.write('<div class="ctoParams">wi=7715380&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 953, Column 62: reference not terminated by REFC delimiter
            document.write('<div class="ctoParams">wi=7715380&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 953, Column 62: reference to entity "pt1" for which no system identifier could be generated
            document.write('<div class="ctoParams">wi=7715380&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 953, Column 58: entity was defined here
            document.write('<div class="ctoParams">wi=7715380&pt1=0&pt2=1<\/div>');
  • Warning Line 953, Column 65: cannot generate system identifier for general entity "pt2"
            document.write('<div class="ctoParams">wi=7715380&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 953, Column 65: general entity "pt2" not defined and no default entity
            document.write('<div class="ctoParams">wi=7715380&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 953, Column 68: reference not terminated by REFC delimiter
            document.write('<div class="ctoParams">wi=7715380&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 953, Column 68: reference to entity "pt2" for which no system identifier could be generated
            document.write('<div class="ctoParams">wi=7715380&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 953, Column 64: entity was defined here
            document.write('<div class="ctoParams">wi=7715380&pt1=0&pt2=1<\/div>');
  • Warning Line 953, Column 70: character "<" is the first character of a delimiter but occurred as data
            document.write('<div class="ctoParams">wi=7715380&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 954, Column 25: 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 955, Column 13: 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 953, Column 25: start tag was here
            document.write('<div class="ctoParams">wi=7715380&pt1=0&pt2=1<\/div>');
  • Error Line 955, Column 13: 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 952, Column 25: start tag was here
            document.write('<div class="ctoDataType">sendEvent<\/div>');
  • Error Line 955, Column 13: 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 951, Column 25: start tag was here
            document.write('<div class="ctoWidgetServer">http:\/\/zizigotr.widget.c…
  • Error Line 955, Column 13: 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 950, Column 25: start tag was here
            document.write('<div id="cto_se_7715380_ac" style="display:none">');
  • Error Line 994, Column 78: there is no attribute "target"
    …"http://www.facebook.com/zizigo" target="_blank" >Facebook Fan Sayfası</a></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 1006, Column 236: required attribute "alt" not specified
    …mg src="http://media.zizigo.com/cmedia/cache-102/media/zizigo-anket.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 1010, Column 29: there is no attribute "src"
                    <iframe src="http://www.facebook.com/plugins/likebox.php?locale…

    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 1010, Column 87: cannot generate system identifier for general entity "href"
    ….com/plugins/likebox.php?locale=tr_TR&href=http%3A%2F%2Fwww.facebook.com%2Fziz…

    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 1010, Column 87: general entity "href" not defined and no default entity
    ….com/plugins/likebox.php?locale=tr_TR&href=http%3A%2F%2Fwww.facebook.com%2Fziz…

    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 1010, Column 91: reference not terminated by REFC delimiter
    …/plugins/likebox.php?locale=tr_TR&href=http%3A%2F%2Fwww.facebook.com%2Fzizigo&…

    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 1010, Column 91: reference to external entity in attribute value
    …/plugins/likebox.php?locale=tr_TR&href=http%3A%2F%2Fwww.facebook.com%2Fzizigo&…

    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 1010, Column 91: reference to entity "href" for which no system identifier could be generated
    …/plugins/likebox.php?locale=tr_TR&href=http%3A%2F%2Fwww.facebook.com%2Fzizigo&…

    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 1010, Column 86: entity was defined here
    …k.com/plugins/likebox.php?locale=tr_TR&href=http%3A%2F%2Fwww.facebook.com%2Fzi…
  • Error Line 1010, Column 264: there is no attribute "scrolling"
    …eader=false&amp;height=258" scrolling="no" frameborder="0" style="border:none;…

    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 1010, Column 281: there is no attribute "frameborder"
    …eight=258" scrolling="no" frameborder="0" style="border:none; overflow:hidden;…

    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 1010, Column 291: there is no attribute "style"
    … scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:240…

    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 1010, Column 368: there is no attribute "allowTransparency"
    …overflow:hidden; width:240px; height:258px;" allowTransparency="true"></iframe>

    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 1010, Column 374: element "iframe" undefined
    …overflow:hidden; width:240px; height:258px;" allowTransparency="true"></iframe>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1014, Column 116: required attribute "alt" not specified
    ….com/cmedia/cache-102/skin/frontend/coolshoes/zizigo/images/footer_card.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 1072, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

    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 353, Column 1: start tag was here
    <div class="wrapper">

Visitor Analysis

Daily Visitor
  • 4.550 visits
Daily Visitor