afriness.com

Pour tous vos besoins spécifiques ou ponctuels, publiez vos annonces, elles seront relayées par les apporteurs d’affaires et les principaux moteurs de recherche.Trouvez des produits, des partenaires et de nouveaux marchés ! Avec les ...
Last updated from 10-03-2014 11:39:54  Update data

Overview Info

  • Domain Name
    afriness.com
  • Favicon
  • Alexa Rank
    #0
  • Google Page Rank
    1
  • Ip Address
    80.80.228.13
  • Page Size
    26.6 KB
  • Images
    11 GIF, 1 JPG, 20 PNG
Heading
H1H2H3H4H5H6
0 0 0 0 0 0

Website Meta Analysis

  • Title
    Afriness - Réseau Africain de Consultation et d'apport d'affaires en ligne
  • Meta Keyword
    apporteur affaire, apporteurs affaires,apporteur d'affaires,agent commercial,apport d'affaires,réseau professionnel,réseau d'affaires,job étudiant,job d'été,job étudiants,emploi sénior,s'occuper en retraite,contrat,contrat commercial, entreprise, entreprises, mise en relation, réseau international, gagner argent, augmenter revenus, professionnel,international, professionnelle, nouveaux clients, agent commercial, business, faire des affaires, prospection, destockage,agent commercial,vitrine illimité,recrutement,cv anonyme,séniors,place de marché,vrp,gagner de l'argent,agent co, minier, miniers, mining, RDC, Congo, consultation, consultations, consultant, consultants, secteur africain, Afrique,
  • Meta Description
    Pour tous vos besoins spécifiques ou ponctuels, publiez vos annonces, elles seront relayées par les apporteurs d’affaires et les principaux moteurs de recherche.Trouvez des produits, des partenaires et de nouveaux marchés ! Avec les bonnes affaires, vendez, achetez, déstockez ! Laissez les acheteurs consulter vos annonces et maintenez vos marges en écoulant votre stock marchand. Faites des affaires en bas de chez vous comme à l’autre bout du monde sans limites.
Advertisement

Technical Analysis

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

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

HTML Analysis

  • date: Mon, 10 Mar 2014 23:39:49 GMT
  • server: Apache
  • accept-ranges: bytes
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 5347
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

No data whois for afriness.com

IP 80.80.228.13 Analysis

  • Country Name
  • City
  • Latitude
  • Longitude
  • No whois ip data for 80.80.228.13

Traffic Analysis

Magestic Backlinks


Daily Ranks

Rank Trend

Visitor Trend

Bounce Trend

HTML Analysis

HTML validation

  • 37 Errors
  • 14 Warnings

Ratio Text/Html

  • 0.7100652444835422

Message Error

  • Error Line 5, Column 147: non SGML character number 146
    …s seront relayées par les apporteurs d’affaires et les principaux moteurs de r…

    You have used an illegal character in your text. HTML uses the standard UNICODE Consortium character repertoire, and it leaves undefined (among others) 65 character codes (0 to 31 inclusive and 127 to 159 inclusive) that are sometimes used for typographical quote marks and similar in proprietary character sets. The validator has found one of these undefined characters in your document. The character may appear on your browser as a curly quote, or a trademark symbol, or some other fancy glyph; on a different computer, however, it will likely appear as a completely different character, or nothing at all.

    Your best bet is to replace the character with the nearest equivalent ASCII character, or to use an appropriate character entity. For more information on Character Encoding on the web, see Alan Flavell's excellent HTML Character Set Issues reference.

    This error can also be triggered by formatting characters embedded in documents by some word processors. If you use a word processor to edit your HTML documents, be sure to use the "Save as ASCII" or similar command to save the document without formatting information.

  • Error Line 9, Column 50: non SGML character number 146
    … des affaires en bas de chez vous comme à l’autre bout du monde sans limites.">

    You have used an illegal character in your text. HTML uses the standard UNICODE Consortium character repertoire, and it leaves undefined (among others) 65 character codes (0 to 31 inclusive and 127 to 159 inclusive) that are sometimes used for typographical quote marks and similar in proprietary character sets. The validator has found one of these undefined characters in your document. The character may appear on your browser as a curly quote, or a trademark symbol, or some other fancy glyph; on a different computer, however, it will likely appear as a completely different character, or nothing at all.

    Your best bet is to replace the character with the nearest equivalent ASCII character, or to use an appropriate character entity. For more information on Character Encoding on the web, see Alan Flavell's excellent HTML Character Set Issues reference.

    This error can also be triggered by formatting characters embedded in documents by some word processors. If you use a word processor to edit your HTML documents, be sure to use the "Save as ASCII" or similar command to save the document without formatting information.

  • Warning Line 15, Column 59: NET-enabling start-tag requires SHORTTAG YES
    <link rel="stylesheet" type="text/css" href="default.css" />

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

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

  • Error Line 16, 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 39, 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 52, Column 7: end tag for element "HEAD" which is not open
    </head>

    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 53, Column 141: document type does not allow element "BODY" here
    …="#808080" VLink="#808080" ALink="#808080" style="background-repeat:repeat-x;">

    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 141, Column 31: value of attribute "NOSHADE" cannot be "TRUE"; must be one of "NOSHADE"
    <hr size=2 width=1201 NOSHADE=true color="#ECECEC">

    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 141, Column 42: there is no attribute "COLOR"
    <hr size=2 width=1201 NOSHADE=true color="#ECECEC">

    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 284, Column 69: cannot generate system identifier for general entity "style"
    …o.net/cgi-bin/counter.cgi?link=visites2011&style=E&nbdigits=4&reloads=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 284, Column 69: general entity "style" not defined and no default entity
    …o.net/cgi-bin/counter.cgi?link=visites2011&style=E&nbdigits=4&reloads=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.

  • Error Line 284, Column 74: reference to entity "style" for which no system identifier could be generated
    …o.net/cgi-bin/counter.cgi?link=visites2011&style=E&nbdigits=4&reloads=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 284, Column 68: entity was defined here
    …o.net/cgi-bin/counter.cgi?link=visites2011&style=E&nbdigits=4&reloads=1"></div>
  • Warning Line 284, Column 77: cannot generate system identifier for general entity "nbdigits"
    …o.net/cgi-bin/counter.cgi?link=visites2011&style=E&nbdigits=4&reloads=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 284, Column 77: general entity "nbdigits" not defined and no default entity
    …o.net/cgi-bin/counter.cgi?link=visites2011&style=E&nbdigits=4&reloads=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.

  • Error Line 284, Column 85: reference to entity "nbdigits" for which no system identifier could be generated
    …o.net/cgi-bin/counter.cgi?link=visites2011&style=E&nbdigits=4&reloads=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 284, Column 76: entity was defined here
    …o.net/cgi-bin/counter.cgi?link=visites2011&style=E&nbdigits=4&reloads=1"></div>
  • Warning Line 284, Column 88: cannot generate system identifier for general entity "reloads"
    …o.net/cgi-bin/counter.cgi?link=visites2011&style=E&nbdigits=4&reloads=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 284, Column 88: general entity "reloads" not defined and no default entity
    …o.net/cgi-bin/counter.cgi?link=visites2011&style=E&nbdigits=4&reloads=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.

  • Error Line 284, Column 95: reference to entity "reloads" for which no system identifier could be generated
    …o.net/cgi-bin/counter.cgi?link=visites2011&style=E&nbdigits=4&reloads=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 284, Column 87: entity was defined here
    …o.net/cgi-bin/counter.cgi?link=visites2011&style=E&nbdigits=4&reloads=1"></div>
  • Error Line 284, Column 98: required attribute "ALT" not specified
    …o.net/cgi-bin/counter.cgi?link=visites2011&style=E&nbdigits=4&reloads=1"></div>

    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 287, Column 166: cannot generate system identifier for general entity "send"
    …%2Fpages%2FAfriness%2F128736333837326&send=false&layout=box_count&width=522&sh…

    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 287, Column 166: general entity "send" not defined and no default entity
    …%2Fpages%2FAfriness%2F128736333837326&send=false&layout=box_count&width=522&sh…

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

  • Error Line 287, Column 170: reference to entity "send" for which no system identifier could be generated
    …ages%2FAfriness%2F128736333837326&send=false&layout=box_count&width=522&show_f…

    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 287, Column 165: entity was defined here
    …m%2Fpages%2FAfriness%2F128736333837326&send=false&layout=box_count&width=522&s…
  • Warning Line 287, Column 177: cannot generate system identifier for general entity "layout"
    …Afriness%2F128736333837326&send=false&layout=box_count&width=522&show_faces=fa…

    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 287, Column 177: general entity "layout" not defined and no default entity
    …Afriness%2F128736333837326&send=false&layout=box_count&width=522&show_faces=fa…

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

  • Error Line 287, Column 183: reference to entity "layout" for which no system identifier could be generated
    …ss%2F128736333837326&send=false&layout=box_count&width=522&show_faces=false&fo…

    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 287, Column 176: entity was defined here
    …FAfriness%2F128736333837326&send=false&layout=box_count&width=522&show_faces=f…
  • Warning Line 287, Column 194: cannot generate system identifier for general entity "width"
    …333837326&send=false&layout=box_count&width=522&show_faces=false&font&colorsch…

    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 287, Column 194: general entity "width" not defined and no default entity
    …333837326&send=false&layout=box_count&width=522&show_faces=false&font&colorsch…

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

  • Error Line 287, Column 199: reference to entity "width" for which no system identifier could be generated
    …7326&send=false&layout=box_count&width=522&show_faces=false&font&colorscheme=l…

    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 287, Column 193: entity was defined here
    …6333837326&send=false&layout=box_count&width=522&show_faces=false&font&colorsc…
  • Warning Line 287, Column 204: cannot generate system identifier for general entity "show_faces"
    …send=false&layout=box_count&width=522&show_faces=false&font&colorscheme=light&…

    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 287, Column 204: general entity "show_faces" not defined and no default entity
    …send=false&layout=box_count&width=522&show_faces=false&font&colorscheme=light&…

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

  • Error Line 287, Column 214: reference to entity "show_faces" for which no system identifier could be generated
    …&layout=box_count&width=522&show_faces=false&font&colorscheme=light&action=rec…

    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 287, Column 203: entity was defined here
    …&send=false&layout=box_count&width=522&show_faces=false&font&colorscheme=light…
  • Warning Line 287, Column 221: cannot generate system identifier for general entity "font"
    …=box_count&width=522&show_faces=false&font&colorscheme=light&action=recommend&…

    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 287, Column 221: general entity "font" not defined and no default entity
    …=box_count&width=522&show_faces=false&font&colorscheme=light&action=recommend&…

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

  • Error Line 287, Column 225: reference to entity "font" for which no system identifier could be generated
    …_count&width=522&show_faces=false&font&colorscheme=light&action=recommend&heig…

    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 287, Column 220: entity was defined here
    …t=box_count&width=522&show_faces=false&font&colorscheme=light&action=recommend…
  • Warning Line 287, Column 226: cannot generate system identifier for general entity "colorscheme"
    …count&width=522&show_faces=false&font&colorscheme=light&action=recommend&heigh…

    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 287, Column 226: general entity "colorscheme" not defined and no default entity
    …count&width=522&show_faces=false&font&colorscheme=light&action=recommend&heigh…

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

  • Error Line 287, Column 237: reference to entity "colorscheme" for which no system identifier could be generated
    …=522&show_faces=false&font&colorscheme=light&action=recommend&height=90&appId=…

    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 287, Column 225: entity was defined here
    …_count&width=522&show_faces=false&font&colorscheme=light&action=recommend&heig…
  • Warning Line 287, Column 244: cannot generate system identifier for general entity "action"
    …ow_faces=false&font&colorscheme=light&action=recommend&height=90&appId=1183109…

    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 287, Column 244: general entity "action" not defined and no default entity
    …ow_faces=false&font&colorscheme=light&action=recommend&height=90&appId=1183109…

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

  • Error Line 287, Column 250: reference to entity "action" for which no system identifier could be generated
    …es=false&font&colorscheme=light&action=recommend&height=90&appId=1183109682045…

    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 287, Column 243: entity was defined here
    …how_faces=false&font&colorscheme=light&action=recommend&height=90&appId=118310…
  • Warning Line 287, Column 261: cannot generate system identifier for general entity "height"
    …nt&colorscheme=light&action=recommend&height=90&appId=118310968204588" scrolli…

    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 287, Column 261: general entity "height" not defined and no default entity
    …nt&colorscheme=light&action=recommend&height=90&appId=118310968204588" scrolli…

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

  • Error Line 287, Column 267: reference to entity "height" for which no system identifier could be generated
    …orscheme=light&action=recommend&height=90&appId=118310968204588" scrolling="no…

    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 287, Column 260: entity was defined here
    …ont&colorscheme=light&action=recommend&height=90&appId=118310968204588" scroll…
  • Warning Line 287, Column 271: cannot generate system identifier for general entity "appId"
    …heme=light&action=recommend&height=90&appId=118310968204588" scrolling="no" fr…

    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 287, Column 271: general entity "appId" not defined and no default entity
    …heme=light&action=recommend&height=90&appId=118310968204588" scrolling="no" fr…

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

  • Error Line 287, Column 276: reference to entity "appId" for which no system identifier could be generated
    …light&action=recommend&height=90&appId=118310968204588" scrolling="no" framebo…

    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 287, Column 270: entity was defined here
    …cheme=light&action=recommend&height=90&appId=118310968204588" scrolling="no" f…
  • Error Line 291, 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 300, Column 13: element "GCSE:SEARCH" undefined
    <gcse:search></gcse:search></div>

    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 311, Column 6: document type does not allow element "BODY" here
    <body>

    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 316, Column 319: NET-enabling start-tag requires SHORTTAG YES
    …"0" style="visibility:hidden;" alt="" /></noscript><!-- http://www.LiveZilla.n…

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

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

  • Error Line 322, Column 8: unterminated comment: found end of entity inside comment
    </html>

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, therefore including the rest of the content in your comment.

  • Info Line 316, Column 332: comment started here
    …sibility:hidden;" alt="" /></noscript><!-- http://www.LiveZilla.net Tracking C…

Visitor Analysis

Daily Visitors Country Map

In Page Analysis