Excédence 3 Suisses, destockage 3 Suisses jusqu'à -85%, propose la vente de produits dégriffés, pas chers et discount: vêtements enfant, vêtements femme, vêtements homme, chaussures et grandes marques à prix discount. ...

excedence.com
  • Domain Name
    excedence.com
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #46066
  • Page Size
    50.6 KB
  • Ip Address
    193.238.149.97
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    35 GIF, 9 JPG, 0 PNG

Website Meta Analysis

  • Title
    Excédence 3 Suisses, destockage 3 Suisses. Vente vêtements, chaussures et accessoires pas cher et discount.
  • Meta Keyword
    destockage vêtements, vêtements femme dégriffés, destockage chaussures, vêtements sport degriffes, destockage textile, destockage vêtement enfant, destockage vêtements sports, destockage et liquidation, fin de série destockage, bonnes affaires chouchou, 3 suisses bonnes affaires chouchou, catalogue de vêtement pas cher, bon prix catalogue vêtement, vêtement hard discount
  • Meta Description
    Excédence 3 Suisses, destockage 3 Suisses jusqu'à -85%, propose la vente de produits dégriffés, pas chers et discount: vêtements enfant, vêtements femme, vêtements homme, chaussures et grandes marques à prix discount.

Technical Analysis

  • Webserver
    Microsoft-IIS/7.5
  • Ip Address
    193.238.149.97
  • Domain Age
    12 Years, 10 Months, 15 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: private,private
  • pragma: no-cache
  • content-length: 47850
  • content-type: text/html
  • expires: Sat, 02 Mar 2013 21:56:48 GMT
  • server: Microsoft-IIS/7.5
  • x-powered-by: ASP.NET
  • date: Sun, 03 Mar 2013 21:56:48 GMT
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for excedence.com

IP 193.238.149.97 Analysis

  • Country Code
    FR
  • Country Code3
    FRA
  • Country Name
    France
  • City
    Lille
  • Continent Code
    EU
  • Latitude
    50.6333
  • Longitude
    3.0667
  • No whois ip data for 193.238.149.97

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 35 Errors
  • 6 Warnings
Ratio Text/Html
  • 0.7158522694364539
Message Error
  • Warning Line 35, Column 38: character "&" is the first character of a delimiter but occurred as data
    		if ((aParameter["SelectedURL"]!="")&&(aParameter["IsAutoComplete"]))

    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 35, Column 39: character "&" is the first character of a delimiter but occurred as data
    		if ((aParameter["SelectedURL"]!="")&&(aParameter["IsAutoComplete"]))

    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 56, Column 7: required attribute "type" not specified
    <style>

    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 73, Column 232: end tag for element "b" which is not open
    … livraison gratuite dès 50 euros d'achats avec le code avantage B1VNU</b></div>

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

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

  • Error Line 108, Column 16: there is no attribute "height"
    				<tr height="25" valign="middle">

    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 154, Column 97: there is no attribute "onClick"
    …age-hiver/269/template_269/1' onClick="_gaq.push(['_trackEvent', 'Bloc Boutiqu…

    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 174, Column 79: there is no attribute "onFocus"
    … value="Votre adresse e-mail" onFocus="if(this.value=='Votre adresse e-mail'){…

    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 177, Column 111: there is no attribute "type"
    …IMAGES/HOMEPAGE/navG_bt_grisOK.gif" type="image" alt="" style="border:0" /></a>

    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 228, 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 254, Column 172: document type does not allow element "div" here; assuming missing "li" start-tag
    …oNav('Rayon_1');"  onmouseout="OngletPrecedent='Rayon_1';HideNav('Rayon_1');" >
  • Error Line 293, Column 192: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …);" style='border-width:0 0 2px 0; border-color:#E65439; border-style:solid; '>

    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 359, Column 192: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …);" style='border-width:0 0 2px 0; border-color:#1379A1; border-style:solid; '>

    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 395, Column 192: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …);" style='border-width:0 0 2px 0; border-color:#FF7800; border-style:solid; '>

    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 431, Column 192: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …);" style='border-width:0 0 2px 0; border-color:#363B3E; border-style:solid; '>

    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 452, Column 192: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …);" style='border-width:0 0 2px 0; border-color:#D5A37B; border-style:solid; '>

    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 489, Column 192: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …);" style='border-width:0 0 2px 0; border-color:#D159C3; border-style:solid; '>

    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 517, Column 192: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …);" style='border-width:0 0 2px 0; border-color:#708F01; border-style:solid; '>

    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 572, Column 192: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …);" style='border-width:0 0 2px 0; border-color:#D3267D; border-style:solid; '>

    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 590, Column 195: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …);" style='border-width:0 0 2px 0; border-color:#FF0088; border-style:solid; '>

    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 614, 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 254, Column 1: start tag was here
    <div style='left:0px; border-color:#FF0088;' class='DivRayon' id='Rayon_1'  onm…
  • Error Line 616, Column 36: required attribute "type" not specified
    			<div id="AccueilHomepage"><style>

    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 616, Column 36: document type does not allow element "style" here
    			<div id="AccueilHomepage"><style>

    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 663, Column 9: ID "UlBonneAffaire" already defined
    <ul id='UlBonneAffaire'>

    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 658, Column 13: ID "UlBonneAffaire" first defined here
    				<ul id='UlBonneAffaire'>
  • Error Line 668, Column 9: ID "UlBonneAffaire" already defined
    <ul id='UlBonneAffaire'>

    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 658, Column 13: ID "UlBonneAffaire" first defined here
    				<ul id='UlBonneAffaire'>
  • Error Line 711, Column 27: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    				<div class="InterneHG"><img src="http://www.excedence.com/IMAGES/HOMEPAGE/v…

    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 713, Column 27: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    				<div class="InterneHD"><img src="http://www.excedence.com/IMAGES/HOMEPAGE/v…

    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 720, Column 86: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …sommaire.asp#2"><div class="InterneHG"><img src="http://www.excedence.com/IMAG…

    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 721, Column 106: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …&amp;STheme=30"><div class="InterneHD"><img src="http://www.excedence.com/IMAG…

    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 728, Column 87: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ES/carte4E.asp"><div class="InterneHG"><img src="http://www.excedence.com/IMAG…

    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 729, Column 86: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …sommaire.asp#4"><div class="InterneHD"><img src="http://www.excedence.com/IMAG…

    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 736, Column 105: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …class="InterneHG" style="width:116px;"><img src="http://www.excedence.com/IMAG…

    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 857, Column 75: required attribute "type" not specified
    …pt language="JavaScript" src="http://www.excedence.com/JS/s_code.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 858, 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 933, Column 347: cannot generate system identifier for general entity "md"
    …://www.")+"mediapeo2.com/ap/?cc="+d+"&md="+c+"&u="+g;f.parentNode.insertBefore…

    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 933, Column 347: general entity "md" not defined and no default entity
    …://www.")+"mediapeo2.com/ap/?cc="+d+"&md="+c+"&u="+g;f.parentNode.insertBefore…

    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 933, Column 349: reference not terminated by REFC delimiter
    …/www.")+"mediapeo2.com/ap/?cc="+d+"&md="+c+"&u="+g;f.parentNode.insertBefore(e…

    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 933, Column 349: reference to entity "md" for which no system identifier could be generated
    …/www.")+"mediapeo2.com/ap/?cc="+d+"&md="+c+"&u="+g;f.parentNode.insertBefore(e…

    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 933, Column 346: entity was defined here
    …p://www.")+"mediapeo2.com/ap/?cc="+d+"&md="+c+"&u="+g;f.parentNode.insertBefor…
  • Warning Line 933, Column 356: cannot generate system identifier for general entity "u"
    …+"mediapeo2.com/ap/?cc="+d+"&md="+c+"&u="+g;f.parentNode.insertBefore(e,f)}win…

    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 933, Column 356: general entity "u" not defined and no default entity
    …+"mediapeo2.com/ap/?cc="+d+"&md="+c+"&u="+g;f.parentNode.insertBefore(e,f)}win…

    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 933, Column 357: reference not terminated by REFC delimiter
    …"mediapeo2.com/ap/?cc="+d+"&md="+c+"&u="+g;f.parentNode.insertBefore(e,f)}wind…

    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 933, Column 357: reference to entity "u" for which no system identifier could be generated
    …"mediapeo2.com/ap/?cc="+d+"&md="+c+"&u="+g;f.parentNode.insertBefore(e,f)}wind…

    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 933, Column 355: entity was defined here
    …)+"mediapeo2.com/ap/?cc="+d+"&md="+c+"&u="+g;f.parentNode.insertBefore(e,f)}wi…

Visitor Analysis

Daily Visitor
  • 3.617 visits
Daily Visitor