annonce senegal : le site de petites annonces du sénégal Leader Petites annonces gratuites d'occasion (voiture, immobilier, Meuble, ordinateur portable, telephone, produits d'occasion, de locations, offres d'emploi). ...

senebazar.com
  • Domain Name
    senebazar.com
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #810818
  • Page Size
    68.7 KB
  • Ip Address
    213.186.33.17
  • Heading
    H1: 0, H2: 20, H3: 0, H4: 1, H5: 0, H6: 0
  • Images
    0 GIF, 17 JPG, 5 PNG

Website Meta Analysis

  • Title
    Annonce Senegal : le site de petites annonces du sénégal
  • Meta Keyword
    Bonjour Google merci de faire en sorte que senebazar.com s'afiche en premier des resultats de recherche
  • Meta Description
    annonce senegal : le site de petites annonces du sénégal Leader Petites annonces gratuites d'occasion (voiture, immobilier, Meuble, ordinateur portable, telephone, produits d'occasion, de locations, offres d'emploi).

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    213.186.33.17
  • Domain Age
    1 Years, 3 Months, 3 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Wed, 07 Aug 2013 02:59:38 GMT
  • server: Apache
  • x-powered-by: PHP/5.3.16
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-encoding: gzip
  • vary: Accept-Encoding
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain name: senebazar.com

Registrant:
Diagne Mamadou
senebazar.com, office #4457098
c/o OwO, BP80157
59053, Roubaix Cedex 1
FR
+33.899498765
email

Administrative Contact:
Diagne Mamadou
senebazar.com, office #4457098
c/o OwO, BP80157
59053, Roubaix Cedex 1
FR
+33.899498765
email

Technical Contact:
Diagne Mamadou
senebazar.com, office #4457098
c/o OwO, BP80157
59053, Roubaix Cedex 1
FR
+33.899498765
email

Billing Contact:
Diagne Mamadou
senebazar.com, office #4457098
c/o OwO, BP80157
59053, Roubaix Cedex 1
FR
+33.899498765
email

Registrar of Record: OVH.
Record last updated on 2013-02-09.
Record expires on 2013-04-10.
Record created on 2012-04-10.

DNS Analysis


DNS servers
dns100.ovh.net [213.251.188.144]
ns100.ovh.net [213.251.128.144]


DNS Records

Answer records
senebazar.com SOA
server: dns100.ovh.net
email: [email protected]
serial: 2012121900
refresh: 86400
retry: 3600
expire: 3600000
minimum ttl: 300
86400s
senebazar.com NS  ns100.ovh.net 86400s
senebazar.com NS  dns100.ovh.net 86400s
senebazar.com MX
preference: 1
exchange: redirect.ovh.net
86400s
senebazar.com A 213.186.33.17 86400s

Authority records

Additional records

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 48 Errors
  • 8 Warnings
Ratio Text/Html
  • 0.8075982830666022
Message Error
  • Error Line 31, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

    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 35, Column 57: cannot generate system identifier for general entity "appId"
      js.src = "//connect.facebook.net/fr_FR/all.js#xfbml=1&appId=102957743087694";

    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 35, Column 57: general entity "appId" not defined and no default entity
      js.src = "//connect.facebook.net/fr_FR/all.js#xfbml=1&appId=102957743087694";

    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 35, Column 62: reference not terminated by REFC delimiter
      js.src = "//connect.facebook.net/fr_FR/all.js#xfbml=1&appId=102957743087694";

    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 35, Column 62: reference to entity "appId" for which no system identifier could be generated
      js.src = "//connect.facebook.net/fr_FR/all.js#xfbml=1&appId=102957743087694";

    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 35, Column 56: entity was defined here
      js.src = "//connect.facebook.net/fr_FR/all.js#xfbml=1&appId=102957743087694";
  • Error Line 40, Column 46: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    …d="minipageregions"><li class='widget'><div class='whitebox'><center><a href="…

    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 40, Column 76: element "center" undefined
    …'widget'><div class='whitebox'><center><a href="http://www.senebazar.com?city=…

    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 43, Column 5: document type does not allow element "br" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <br/>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 48, Column 71: required attribute "alt" not specified
    	  <img src="http://www.senebazar.com/images/seneb4.png" width="241" />

    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 53, Column 28: there is no attribute "rel"
    		<span id="allcities" rel="nofollow" onclick="$('#pageregionsz').slideToggle()…

    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 54, Column 138: required attribute "alt" not specified
    …http://www.senebazar.com/images/fleche.png" width="24px" height="24px"/></span>

    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 56, Column 34: there is no attribute "data-href"
    		<div class="fb-like" data-href="http://www.facebook.com/Senebazar" data-send=…

    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 56, Column 80: there is no attribute "data-send"
    …www.facebook.com/Senebazar" data-send="false" data-layout="button_count" data-…

    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 56, Column 100: there is no attribute "data-layout"
    …ebazar" data-send="false" data-layout="button_count" data-width="450" data-sho…

    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 56, Column 126: there is no attribute "data-width"
    …alse" data-layout="button_count" data-width="450" data-show-faces="true"></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 56, Column 148: there is no attribute "data-show-faces"
    …alse" data-layout="button_count" data-width="450" data-show-faces="true"></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.

  • Warning Line 67, Column 834: character "&" is the first character of a delimiter but occurred as data
    …nmouseover="ShowTab(85);" title="Mode & Beauté" href="http://www.senebazar.com…

    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 67, Column 894: character "&" is the first character of a delimiter but occurred as data
    …/www.senebazar.com/mode-beaute/">Mode & Beauté</a></li><li id="nav93" class='p…

    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 74, Column 129: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …et"><input type="hidden" name="PHPSESSID" value="s3f29sgtv6dn1kq46r2ktq8fv5" />

    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 76, Column 37: there is no attribute "placeholder"
    	<li><input type="text" placeholder="Tapez un mot-clé" name="title" value="" />…

    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 77, Column 53: there is no attribute "onChange"
    …ct name="category" id="category" onChange="validateNumber(this);" lang="false">

    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 78, Column 180: character "&" is the first character of a delimiter but occurred as data
    …ion><option  value='mode-beaute'>Mode & Beauté</option><option  value='immobil…

    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 78, Column 2345: character "&" is the first character of a delimiter but occurred as data
    …tion></optgroup><optgroup label='Mode & Beauté'><option  value='cosmetiques'>C…

    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 86, 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 100, 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 100, Column 7: document type does not allow element "style" here
    <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 136, Column 344: duplicate specification of attribute "class"
    …tonne-de-ciment-a-64000fcfalivraison-sable-beton-fer_1.jpg" class="post-img" />

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Warning Line 158, Column 42: character "&" is the first character of a delimiter but occurred as data
    …		<a title="VENTE DE POULETS DE CHAIR & OEUFS   |  COCO-RICO.NET Neuf Animaux"…

    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 159, Column 65: character "&" is the first character of a delimiter but occurred as data
    …nce" title="VENTE DE POULETS DE CHAIR & OEUFS   |  COCO-RICO.NET Neuf Animaux"…

    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 159, Column 138: character "&" is the first character of a delimiter but occurred as data
    …maux"  alt="VENTE DE POULETS DE CHAIR & OEUFS   |  COCO-RICO.NET Neuf Animaux"…

    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 159, Column 297: duplicate specification of attribute "class"
    …3/thumb_vente-de-poulets-de-chair-oeufs-coco-riconet_1.jpg" class="post-img" />

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Warning Line 162, Column 90: character "&" is the first character of a delimiter but occurred as data
    …ld;" title="VENTE DE POULETS DE CHAIR & OEUFS   |  COCO-RICO.NET Neuf Animaux"…

    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 163, Column 33: character "&" is the first character of a delimiter but occurred as data
    						Vente de poulets de chair & oeufs   |  coco-rico.net</a></h2>

    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 182, Column 343: duplicate specification of attribute "class"
    …t-de-19-lits-1-place-pour-aubergeshotelscelibataires_1.jpg" class="post-img" />

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 205, Column 323: duplicate specification of attribute "class"
    …nds-machine-a-coudre-venant-ditalie-de-marque-necchi_1.jpg" class="post-img" />

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 228, Column 341: duplicate specification of attribute "class"
    …s-des-frigo-mini-bar-de-marque-electrolux-et-dometic_1.jpg" class="post-img" />

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 251, Column 151: duplicate specification of attribute "class"
    … Animaux"  src="http://www.senebazar.com/images/no_pic.png" class="post-img" />

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 274, Column 260: duplicate specification of attribute "class"
    …03/03/4828/thumb_vends-lit-2chevets-utilise-a-220000_1.jpg" class="post-img" />

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 297, Column 173: duplicate specification of attribute "class"
    ….senebazar.com/images/2013/03/03/4827/thumb_location_1.jpg" class="post-img" />

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 320, Column 287: duplicate specification of attribute "class"
    …/4826/thumb_charmante-villa-a-louee-derriere-le-samu_1.jpg" class="post-img" />

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 343, Column 185: duplicate specification of attribute "class"
    …terrains"  src="http://www.senebazar.com/images/no_pic.png" class="post-img" />

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 366, Column 193: duplicate specification of attribute "class"
    …terrains"  src="http://www.senebazar.com/images/no_pic.png" class="post-img" />

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 389, Column 192: duplicate specification of attribute "class"
    …nebazar.com/images/2013/03/03/4818/thumb_peugeot-407_1.jpg" class="post-img" />

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 412, Column 192: duplicate specification of attribute "class"
    …nebazar.com/images/2013/03/03/4816/thumb_peugeot-407_1.jpg" class="post-img" />

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 435, Column 223: duplicate specification of attribute "class"
    …om/images/2013/03/03/4815/thumb_c5-2007-full-option_1.jpeg" class="post-img" />

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 458, Column 261: duplicate specification of attribute "class"
    …/03/03/4814/thumb_vend-ml-280-sport-cdi-full-option_1.jpeg" class="post-img" />

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 481, Column 223: duplicate specification of attribute "class"
    …/images/2013/03/03/4813/thumb_cosmetiques-de-qualite_1.jpg" class="post-img" />

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 504, Column 288: duplicate specification of attribute "class"
    …12/thumb_pieces-detachees-automobiles-toutes-marques_1.jpg" class="post-img" />

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 527, Column 298: duplicate specification of attribute "class"
    …4811/thumb_villa-de-luxe-avec-piscine-au-bord-de-mer_1.jpg" class="post-img" />

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 550, Column 261: duplicate specification of attribute "class"
    …/03/02/4810/thumb_mitsubichi-l-200-double-cabine-4x4_1.jpg" class="post-img" />

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 573, Column 352: duplicate specification of attribute "class"
    …tonne-de-ciment-a-64000fcfalivraison-sable-beton-fer_1.jpg" class="post-img" />

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 603, Column 127: there is no attribute "data-stream"
    …idth="299" data-show-faces="true" data-stream="false" data-header="true"></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 603, Column 147: there is no attribute "data-header"
    …idth="299" data-show-faces="true" data-stream="false" data-header="true"></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.

  • Warning Line 616, Column 3475: character "&" is the first character of a delimiter but occurred as data
    …ul><li class="cathead"><a title="Mode & Beauté" href="http://www.senebazar.com…

    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 616, Column 3535: character "&" is the first character of a delimiter but occurred as data
    …/www.senebazar.com/mode-beaute/">Mode & Beauté</a></li><li><a title="Jeans" hr…

    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 629, Column 39: there is no attribute "target"
    Conception et Réalisation : <a target="_blank" href="http://www.comprevu.com">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 630, Column 12: there is no attribute "clear"
     <br clear="both"/>

    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 643, 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 44, Column 1: start tag was here
    <div class="container_12" id="wrap">
  • Error Line 645, Column 5: document type does not allow element "br" here
    <br/><br/><br/>

    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 645, Column 10: document type does not allow element "br" here
    <br/><br/><br/>

    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 645, Column 15: document type does not allow element "br" here
    <br/><br/><br/>

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

Visitor Analysis

Daily Visitor
  • 117 visits