avoncosmetics.ro

Home     |     Ajutor     |     Login in contul tau Avon Adauga la favorite JOIN THE COMMUNITY             Contacteaza-ne | Termeni si conditii | NOU - Cookies, confidentialitate si securitate ...

Display Widget for this domain on your website. Click Here
This data was last updated from 04-03-2013 05:21:14  (update).

Overview Info

  • Domain Name
    avoncosmetics.ro
  • Favicon
  • Alexa Rank
    #26933
  • Google Page Rank
    PR 5
  • Ip Address
    134.65.41.51
  • Page Size
    31.9 KB
  • Images
    2 GIF, 11 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
    Avon Cosmetics Romania - afacerea ta online
  • Meta Keyword
  • Meta Description
    Home     |     Ajutor     |     Login in contul tau Avon Adauga la favorite JOIN THE COMMUNITY             Contacteaza-ne | Termeni si conditii | NOU - Cookies, confidentialitate si securitate | Harta site | Avon in lume | ACVD | Newsletter ...

Technical Analysis



  • Webserver
    IBM_HTTP_Server
  • Ip Address
    134.65.41.51
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from avoncosmetics.ro.

HTML Analysis

  • date: Mon, 04 Mar 2013 05:21:09 GMT
  • server: IBM_HTTP_Server
  • x-powered-by: Servlet/3.0
  • expires: Thu, 01 Dec 1994 16:00:00 GMT
  • cache-control: no-cache="set-cookie, set-cookie2"
  • content-type: text/html; charset=UTF-8
  • content-language: ro-ro
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

% Whois Server Version 3.0 - whois.rotld.ro:43

% Rights restricted by copyright.
% Specifically, this data MAY ONLY be used for Internet operational
% purposes. It may not be used for targeted advertising or any
% other purpose.

% Este INTERZISA folosirea datelor de pe acest server in oricare
% alt scop decat operarea retelei. In special este INTERZISA
% folosirea lor in scopuri publicitare.

% Top Level Domain : ro
% Maintainance : www.rotld.ro

Domain Name: avoncosmetics.ro
Registered On: 2002-04-22
Registrar: ICI - ROTLD
Referral URL:

Nameserver: dns1.avon.com
Nameserver: dns4.avon.com

Domain Status: OK


IP 134.65.41.51 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 134.65.41.51

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 43 Errors
  • 21 Warnings
Ratio Text/Html
  • 0.33839140942882495
Message Error
  • Error Line 5, Column 1: no document type declaration; will parse without validation
    <script type="text/javascript">	

    The document type could not be determined, because the document had no correct DOCTYPE declaration. The document does not look like HTML, therefore automatic fallback could not be performed, and the document was only checked against basic markup syntax.

    Learn how to add a doctype to your document from our FAQ, or use the validator's Document Type option to validate your document against a specific Document Type.

  • Error Line 17, Column 6: document type does not allow element "HTML" here
    <html>

    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 21, Column 43: NET-enabling start-tag requires SHORTTAG YES
    <LINK href="static/css/usec.css" type=text/css rel=stylesheet>

    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.

  • Warning Line 22, Column 59: NET-enabling start-tag requires SHORTTAG YES
    <LINK title=Style href="static/css/mt_style.css" type=text/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.

  • Warning Line 24, Column 54: NET-enabling start-tag requires SHORTTAG YES
    <LINK title=Style href="static/css/win.css" type=text/css rel=STYLESHEET>

    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.

  • Warning Line 116, Column 99: cannot generate system identifier for general entity "location.search.indexOf"
    …tion.search.indexOf("endcount")!=-1 &&location.search.indexOf("pagename")!=-1)…

    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 116, Column 99: general entity "location.search.indexOf" not defined and no default entity
    …tion.search.indexOf("endcount")!=-1 &&location.search.indexOf("pagename")!=-1)…

    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 116, Column 122: reference to entity "location.search.indexOf" for which no system identifier could be generated
    …tion.search.indexOf("endcount")!=-1 &&location.search.indexOf("pagename")!=-1){

    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 116, Column 98: entity was defined here
    …ation.search.indexOf("endcount")!=-1 &&location.search.indexOf("pagename")!=-1…
  • Error Line 301, Column 6: end tag for element "DIV" which is not open
    </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 359, Column 5: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!--Function to open navigations in a new window - 19th August -->
  • Info Line 356, Column 31: comment declaration started here
    <script language="JavaScript"><!--
  • Warning Line 378, Column 20: cannot generate system identifier for general entity "LangCodeVal"
    		if(url.indexOf('&LangCodeVal') > 0){

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 378, Column 20: general entity "LangCodeVal" not defined and no default entity
    		if(url.indexOf('&LangCodeVal') > 0){

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

  • Error Line 378, Column 31: reference to entity "LangCodeVal" for which no system identifier could be generated
    		if(url.indexOf('&LangCodeVal') > 0){

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

  • Info Line 378, Column 19: entity was defined here
    		if(url.indexOf('&LangCodeVal') > 0){
  • Error Line 382, Column 41: reference to entity "LangCodeVal" for which no system identifier could be generated
    		formObj.action=urlString+"&LangCodeVal="+langVal;

    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 378, Column 19: entity was defined here
    		if(url.indexOf('&LangCodeVal') > 0){
  • Error Line 386, Column 69: reference to entity "LangCodeVal" for which no system identifier could be generated
    			        	formObj.action=formObj.CURR_PAGE_URL.value+"&LangCodeVal="+langVal;

    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 378, Column 19: entity was defined here
    		if(url.indexOf('&LangCodeVal') > 0){
  • Warning Line 411, Column 68: cannot generate system identifier for general entity "currPage"
    …ngChange.page?LangCodeVal="+langVal+"&currPage="+currpage+"&"+requestParameter…

    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 411, Column 68: general entity "currPage" not defined and no default entity
    …ngChange.page?LangCodeVal="+langVal+"&currPage="+currpage+"&"+requestParameter…

    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 411, Column 76: reference to entity "currPage" for which no system identifier could be generated
    …ngChange.page?LangCodeVal="+langVal+"&currPage="+currpage+"&"+requestParameter;

    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 411, Column 67: entity was defined here
    …angChange.page?LangCodeVal="+langVal+"&currPage="+currpage+"&"+requestParamete…
  • Error Line 446, Column 27: character ";" not allowed in attribute specification list
    	    for(count=0;count<len;count++)
  • Error Line 508, Column 77: reference to entity "currPage" for which no system identifier could be generated
    …ngChange.page?LangCodeVal="+langVal+"&currPage="+currpage+"&"+requestParameter;

    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 411, Column 67: entity was defined here
    …angChange.page?LangCodeVal="+langVal+"&currPage="+currpage+"&"+requestParamete…
  • Warning Line 539, Column 12: cannot generate system identifier for general entity "langCd"
    		return "&langCd="+lng;

    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 539, Column 12: general entity "langCd" not defined and no default entity
    		return "&langCd="+lng;

    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 539, Column 18: reference to entity "langCd" for which no system identifier could be generated
    		return "&langCd="+lng;

    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 539, Column 11: entity was defined here
    		return "&langCd="+lng;
  • Warning Line 601, Column 27: NET-enabling start-tag requires SHORTTAG YES
    	NAME="NAV_PAGE" VALUE="" />

    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.

  • Warning Line 615, Column 51: NET-enabling start-tag requires SHORTTAG YES
    				<INPUT TYPE="HIDDEN" NAME="NAV_PAGE" VALUE="" />

    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 621, Column 33: an attribute value must be a literal unless it contains only name characters
    						<td height="99%" width=100%><a

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

  • Error Line 632, Column 20: an attribute value must be a literal unless it contains only name characters
    						<td width=100%><IMG

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

  • Error Line 646, Column 55: "NOWRAP" is not a member of a group specified for any attribute
    								<td class="topLinksBold" align="center" nowrap>Home</td>
  • Warning Line 648, Column 42: cannot generate system identifier for general entity "nbsp"
    …					<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbs…

    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 648, Column 42: general entity "nbsp" not defined and no default entity
    …					<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbs…

    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 648, Column 46: reference to entity "nbsp" for which no system identifier could be generated
    …	<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&n…

    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 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 648, Column 52: reference to entity "nbsp" for which no system identifier could be generated
    …lass=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</…

    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 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 648, Column 58: reference to entity "nbsp" for which no system identifier could be generated
    …ss=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</td>

    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 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 648, Column 64: reference to entity "nbsp" for which no system identifier could be generated
    …ss=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</td>

    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 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 648, Column 71: reference to entity "nbsp" for which no system identifier could be generated
    …ss=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</td>

    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 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 648, Column 77: reference to entity "nbsp" for which no system identifier could be generated
    …ss=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</td>

    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 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 648, Column 83: reference to entity "nbsp" for which no system identifier could be generated
    …ss=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</td>

    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 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 648, Column 89: reference to entity "nbsp" for which no system identifier could be generated
    …ss=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</td>

    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 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 650, Column 51: "NOWRAP" is not a member of a group specified for any attribute
    								<td align="center" class="topLinks" nowrap><a href="#"
  • Error Line 654, Column 46: reference to entity "nbsp" for which no system identifier could be generated
    …	<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&n…

    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 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 654, Column 52: reference to entity "nbsp" for which no system identifier could be generated
    …lass=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</…

    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 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 654, Column 58: reference to entity "nbsp" for which no system identifier could be generated
    …ss=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</td>

    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 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 654, Column 64: reference to entity "nbsp" for which no system identifier could be generated
    …ss=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</td>

    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 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 654, Column 71: reference to entity "nbsp" for which no system identifier could be generated
    …ss=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</td>

    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 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 654, Column 77: reference to entity "nbsp" for which no system identifier could be generated
    …ss=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</td>

    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 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 654, Column 83: reference to entity "nbsp" for which no system identifier could be generated
    …ss=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</td>

    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 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 654, Column 89: reference to entity "nbsp" for which no system identifier could be generated
    …ss=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</td>

    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 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 656, Column 51: "NOWRAP" is not a member of a group specified for any attribute
    								<td align="center" class="topLinks" nowrap><a href="#"
  • Warning Line 682, Column 56: NET-enabling start-tag requires SHORTTAG YES
    									onkeypress="return checkSearchSubmit(event);" /></td>

    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.

  • Warning Line 725, Column 71: cannot generate system identifier for general entity "requestId"
    …ref="/REPSuite/customerRegistration.page?actionType=REJECTEDBAR&requestId=null"

    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 725, Column 71: general entity "requestId" not defined and no default entity
    …ref="/REPSuite/customerRegistration.page?actionType=REJECTEDBAR&requestId=null"

    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 725, Column 80: reference to entity "requestId" for which no system identifier could be generated
    …ref="/REPSuite/customerRegistration.page?actionType=REJECTEDBAR&requestId=null"

    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 725, Column 70: entity was defined here
    …ref="/REPSuite/customerRegistration.page?actionType=REJECTEDBAR&requestId=null"
  • Warning Line 728, Column 50: NET-enabling start-tag requires SHORTTAG YES
    			<INPUT TYPE="HIDDEN" NAME="CURR_URL" VALUE="" />

    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.

  • Warning Line 792, Column 19: NET-enabling start-tag requires SHORTTAG YES
    					width="100%" /></TD>

    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.

  • Warning Line 989, Column 39: cannot generate system identifier for general entity "CURR_URL"
    			document.location.href=currVal + "&CURR_URL=" + tempUrl;	

    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 989, Column 39: general entity "CURR_URL" not defined and no default entity
    			document.location.href=currVal + "&CURR_URL=" + tempUrl;	

    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 989, Column 47: reference to entity "CURR_URL" for which no system identifier could be generated
    			document.location.href=currVal + "&CURR_URL=" + tempUrl;	

    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 989, Column 38: entity was defined here
    			document.location.href=currVal + "&CURR_URL=" + tempUrl;	
  • Warning Line 1006, Column 54: NET-enabling start-tag requires SHORTTAG YES
    <input type="hidden" name="index" id="index" value=""/>

    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.

  • Warning Line 1007, Column 62: NET-enabling start-tag requires SHORTTAG YES
    <input type="hidden" name="cmpgnYrNr" id="cmpgnYrNr" value=""/>			

    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.

  • Warning Line 1014, Column 66: NET-enabling start-tag requires SHORTTAG YES
    			src="static/images/home_page/HT_bottom_line.jpg" width="100%" /></TD>

    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 1046, Column 28: "NOWRAP" is not a member of a group specified for any attribute
    		<td align="right" nowrap style="cursor:no-cursor"><font color="white">© 2012 …
  • Warning Line 1049, Column 47: NET-enabling start-tag requires SHORTTAG YES
    	<INPUT TYPE="HIDDEN" NAME="CURR_URL" VALUE=""/>

    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.

Visitor Analysis

Daily Visitor
  • 5.950 visits
Daily Visitor

In Page Analysis