Matrimonial in India: India's No. 1 matrimonials site provides online matrimony service! Find suitable Indian & NRI brides and grooms for marriage. Register for free and take advantage of our singles matchmaking ...

simplymarry.com
  • Domain Name
    simplymarry.com
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #21869
  • Page Size
    124.6 KB
  • Ip Address
    115.112.206.14
  • Heading
    H1: 0, H2: 12, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    6 GIF, 3 JPG, 28 PNG

Website Meta Analysis

  • Title
    Matrimonials in India-Matrimony,Indian Matrimonial Site-SimplyMarry.Com
  • Meta Keyword
    matrimonial, matrimonials, matrimonial service, matrimony, matrimonial site, matchmaking, matchmaking services, indian matchmaker, NRI matrimonial, singles matchmaking, online matchmaking, indian matchmaking services, indian brides, indian grooms, hindu m
  • Meta Description
    Matrimonial in India: India's No. 1 matrimonials site provides online matrimony service! Find suitable Indian & NRI brides and grooms for marriage. Register for free and take advantage of our singles matchmaking services.

Technical Analysis

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

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

HTML Analysis

  • date: Mon, 04 Mar 2013 00:38:06 GMT
  • server: Apache
  • content-language: en-US
  • vary: Accept-Encoding,User-Agent
  • content-encoding: gzip
  • content-length: 25353
  • content-type: text/html;charset=ISO-8859-1
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Contact Privacy Inc. Customer 028150
96 Mowat Ave
Toronto, ON M6K 3M1
CA

Domain name: SIMPLYMARRY.COM


Administrative Contact:
Contact Privacy Inc. Customer 028150, email
96 Mowat Ave
Toronto, ON M6K 3M1
CA
+1.4165385457
Technical Contact:
Contact Privacy Inc. Customer 028150, email
96 Mowat Ave
Toronto, ON M6K 3M1
CA
+1.4165385457
Billing Contact:
Contact Privacy Inc. Customer 028150, email
96 Mowat Ave
Toronto, ON M6K 3M1
CA
+1.4165385457

Registration Service Provider:
Times Internet Ltd., email
+911244187000
This company may be contacted for domain login/passwords,
DNS/Nameserver changes, and general domain support questions.


Registrar of Record: Times Internet Ltd.
Record last updated on 20-Feb-2011.
Record expires on 02-Nov-2019.
Record created on 02-Nov-2006.

Domain servers in listed order:
PDNS3.ULTRADNS.ORG
PDNS2.ULTRADNS.NET
PDNS1.ULTRADNS.NET
PDNS5.ULTRADNS.INFO
PDNS4.ULTRADNS.ORG


Domain status: clientTransferProhibited
clientUpdateProhibited


This domain's privacy is protected by business.indiatimes.com. To reach the domain contacts, please go to http://www.business.indiatimes.com and follow the instructions.


IP 115.112.206.14 Analysis

  • Country Code
    IN
  • Country Code3
    IND
  • Country Name
    India
  • City
    Mumbai
  • Continent Code
    AS
  • Latitude
    18.975
  • Longitude
    72.8258
  • % [whois.apnic.net node-5]
    % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

    inetnum: 115.112.0.0 - 115.119.255.255
    netname: TATACOMM-IN
    descr: Internet Service Provider
    descr: TATA Communications formerly VSNL is Leading ISP,
    descr: Data and Voice Carrier in India
    admin-c: TC651-AP
    tech-c: TC651-AP
    country: IN
    status: ALLOCATED PORTABLE
    mnt-by: APNIC-HM
    mnt-lower: MAINT-TATACOMM-IN
    mnt-irt: IRT-TATACOMM-IN
    remarks: -+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    remarks: This object can only be updated by APNIC hostmasters.
    remarks: To update this object, please contact APNIC
    remarks: hostmasters and include your organisation's account
    remarks: name in the subject line.
    remarks: -+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    changed: hm-changed@apnic.net 20080730
    changed: hm-changed@apnic.net 20080826
    changed: hm-changed@apnic.net 20080827
    changed: hm-changed@apnic.net 20120221
    source: APNIC

    role: TATA Communications
    nic-hdl: TC651-AP
    address: 6th Floor, LVSB, VSNL
    address: Kashinath Dhuru marg, Prabhadevi
    address: Dadar(W), Mumbai 400028
    phone: +91-22-56633503
    fax-no: +91-22-24320132
    country: IN
    e-mail: ip.admin@vsnl.co.in
    admin-c: IA15-AP
    tech-c: VT43-AP
    mnt-by: MAINT-TATACOMM-IN
    changed: hm-changed@apnic.net 20080826
    changed: hm-changed@apnic.net 20080827
    source: APNIC


Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 183 Errors
  • 46 Warnings
Ratio Text/Html
  • 0.7553846877351392
Message Error
  • Warning Line 30, Column 147: character "&" is the first character of a delimiter but occurred as data
    …trimony service! Find suitable Indian & NRI brides and grooms for marriage. Re…

    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 145, Column 41: end tag for "br" omitted, but OMITTAG NO was specified
    of match search on SimplyMarry.com. <br>

    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 145, Column 37: start tag was here
    of match search on SimplyMarry.com. <br>
  • Error Line 150, Column 53: end tag for "img" omitted, but OMITTAG NO was specified
    		id="cRs_0" src="/images/ie_safari_browser.png"></a></li>

    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 149, Column 39: start tag was here
    		href="http://www.apple.com/safari/"><img alt="safari browser"
  • Error Line 154, Column 43: end tag for "img" omitted, but OMITTAG NO was specified
    		src="/images/ie_mozilla_browser.png"></a></li>

    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 152, Column 62: start tag was here
    		href="http://www.mozilla.org/en-US/products/download.html"><img
  • Error Line 158, Column 42: end tag for "img" omitted, but OMITTAG NO was specified
    		src="/images/ie_chrome_browser.png"></a></li>

    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 156, Column 48: start tag was here
    		href="http://www.google.com/chrome?hl=en-GB"><img
  • Error Line 161, Column 52: end tag for "img" omitted, but OMITTAG NO was specified
    		id="cRs_3" src="/images/ie_opera_browser.png"></a></li>

    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 160, Column 41: start tag was here
    		href="http://www.opera.com/download/"><img alt="Opera browser"
  • Error Line 165, Column 44: end tag for "img" omitted, but OMITTAG NO was specified
    		src="/images/ie_internet_browser.png"></a></li>

    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 163, Column 89: start tag was here
    …//www.microsoft.com/india/windows/ie/IE8.aspx?os=Win7&amp;browser=Firefox"><img
  • Error Line 170, Column 59: end tag for "img" omitted, but OMITTAG NO was specified
    	alt="close" id="cRs_5" src="/images/ie_close_div.png"></a></div>

    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 169, Column 55: start tag was here
    	onclick="$('#compBrowsersDiv').hide();return false;"><img
  • Error Line 176, Column 81: invalid comment declaration: found name character outside comment but inside comment declaration
    …vascript" src="/js/feedback.js"></script> <!----- page header html start ----->
  • Info Line 176, Column 75: comment declaration started here
    …vascript" src="/js/feedback.js"></script> <!----- page header html start ----->
  • Error Line 180, Column 20: there is no attribute "allowtransparency"
    	allowtransparency="true"

    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 187, Column 17: there is no attribute "size"
    <g:plusone size="medium"></g:plusone>

    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 187, Column 25: element "g:plusone" undefined
    <g:plusone size="medium"></g:plusone>

    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 216, Column 10: ID "cRs_173" already defined
    	<li id="cRs_173"><a id="cRs_58"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 213, Column 10: ID "cRs_173" first defined here
    	<li id="cRs_173"><a id="cRs_58"
  • Error Line 216, Column 26: ID "cRs_58" already defined
    	<li id="cRs_173"><a id="cRs_58"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 213, Column 26: ID "cRs_58" first defined here
    	<li id="cRs_173"><a id="cRs_58"
  • Error Line 222, Column 135: required attribute "alt" not specified
    …id=155" target="_blank"><img src="/images/brahmin_3March.gif" border="0" /></a>

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

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

  • Error Line 224, Column 71: required attribute "alt" not specified
    …         <br/><img src="/images/spacer.gif" width="1" height="10" /><br/></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>.

  • Error Line 227, Column 137: ID "cRs_0" already defined
    …ges/sm_index_logo.png" alt="SimplyMarry.com" name="cRs_0" id="cRs_0"></a></div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 150, Column 7: ID "cRs_0" first defined here
    		id="cRs_0" src="/images/ie_safari_browser.png"></a></li>
  • Error Line 227, Column 147: end tag for "img" omitted, but OMITTAG NO was specified
    …ges/sm_index_logo.png" alt="SimplyMarry.com" name="cRs_0" id="cRs_0"></a></div>

    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 227, Column 61: start tag was here
    …="sm_logo fl"><a id="cRs_64" href="#"><img src="/images/sm_index_logo.png" alt…
  • Error Line 233, Column 50: end tag for "br" omitted, but OMITTAG NO was specified
    		<p id="cRs_130"><b id="cRs_146">Take a step<br>

    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 233, Column 46: start tag was here
    		<p id="cRs_130"><b id="cRs_146">Take a step<br>
  • Error Line 234, Column 22: end tag for "br" omitted, but OMITTAG NO was specified
    		forward to find<br>

    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 234, Column 18: start tag was here
    		forward to find<br>
  • Error Line 237, Column 28: ID "cRs_1" already defined
    			alt="register free" id="cRs_1"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 153, Column 37: ID "cRs_1" first defined here
    		alt="Mozilla firefox browser" id="cRs_1"
  • Error Line 238, Column 49: end tag for "img" omitted, but OMITTAG NO was specified
    			src="/images/sm_visual_registration_btn.png"> </a> <span

    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 236, Column 52: start tag was here
    		<a id="cRs_66" href="/matrimonial/registration"> <img
  • Error Line 274, Column 102: value of attribute "method" cannot be "POST"; must be one of "get", "post"
    …t>  <form id="searchCriteriaForm" action="/search/performSearch" method="POST">

    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 284, Column 70: there is no attribute "onChange"
    …elect id="genderSelect" name="gender" class="qsselect" onChange="updateAge();">

    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 4041, Column 22: character "&" is the first character of a delimiter but occurred as data
    									Saint Kitts & Nevis

    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 4296, Column 10: ID "cRs_22" already defined
    <div id="cRs_22" class="smhelpline fr clr">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 142, Column 10: ID "cRs_22" first defined here
    <div id="cRs_22" class="ienotifyico fl">&nbsp;</div>
  • Warning Line 4297, Column 143: cannot generate system identifier for general entity "file"
    ….liveperson.net/hc/26231671/?cmd=file&file=visitorWantsToChat&site=26231671&SE…

    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 4297, Column 143: general entity "file" not defined and no default entity
    ….liveperson.net/hc/26231671/?cmd=file&file=visitorWantsToChat&site=26231671&SE…

    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 4297, Column 147: reference not terminated by REFC delimiter
    …eperson.net/hc/26231671/?cmd=file&file=visitorWantsToChat&site=26231671&SESSIO…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 4297, Column 147: reference to external entity in attribute value
    …eperson.net/hc/26231671/?cmd=file&file=visitorWantsToChat&site=26231671&SESSIO…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 4297, Column 147: reference to entity "file" for which no system identifier could be generated
    …eperson.net/hc/26231671/?cmd=file&file=visitorWantsToChat&site=26231671&SESSIO…

    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 4297, Column 142: entity was defined here
    …d.liveperson.net/hc/26231671/?cmd=file&file=visitorWantsToChat&site=26231671&S…
  • Warning Line 4297, Column 167: cannot generate system identifier for general entity "site"
    …671/?cmd=file&file=visitorWantsToChat&site=26231671&SESSIONVAR!operator=ananya…

    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 4297, Column 167: general entity "site" not defined and no default entity
    …671/?cmd=file&file=visitorWantsToChat&site=26231671&SESSIONVAR!operator=ananya…

    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 4297, Column 171: reference not terminated by REFC delimiter
    …?cmd=file&file=visitorWantsToChat&site=26231671&SESSIONVAR!operator=ananya&SES…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 4297, Column 171: reference to external entity in attribute value
    …?cmd=file&file=visitorWantsToChat&site=26231671&SESSIONVAR!operator=ananya&SES…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 4297, Column 171: reference to entity "site" for which no system identifier could be generated
    …?cmd=file&file=visitorWantsToChat&site=26231671&SESSIONVAR!operator=ananya&SES…

    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 4297, Column 166: entity was defined here
    …1671/?cmd=file&file=visitorWantsToChat&site=26231671&SESSIONVAR!operator=anany…
  • Warning Line 4297, Column 181: cannot generate system identifier for general entity "SESSIONVAR"
    …file=visitorWantsToChat&site=26231671&SESSIONVAR!operator=ananya&SESSIONVAR!sk…

    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 4297, Column 181: general entity "SESSIONVAR" not defined and no default entity
    …file=visitorWantsToChat&site=26231671&SESSIONVAR!operator=ananya&SESSIONVAR!sk…

    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 4297, Column 191: reference not terminated by REFC delimiter
    …orWantsToChat&site=26231671&SESSIONVAR!operator=ananya&SESSIONVAR!skill=timesm…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 4297, Column 191: reference to external entity in attribute value
    …orWantsToChat&site=26231671&SESSIONVAR!operator=ananya&SESSIONVAR!skill=timesm…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 4297, Column 191: reference to entity "SESSIONVAR" for which no system identifier could be generated
    …orWantsToChat&site=26231671&SESSIONVAR!operator=ananya&SESSIONVAR!skill=timesm…

    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 4297, Column 180: entity was defined here
    …&file=visitorWantsToChat&site=26231671&SESSIONVAR!operator=ananya&SESSIONVAR!s…
  • Warning Line 4297, Column 218: reference not terminated by REFC delimiter
    …&SESSIONVAR!operator=ananya&SESSIONVAR!skill=timesmatri&imageUrl=http://&refer…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 4297, Column 218: reference to external entity in attribute value
    …&SESSIONVAR!operator=ananya&SESSIONVAR!skill=timesmatri&imageUrl=http://&refer…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 4297, Column 218: reference to entity "SESSIONVAR" for which no system identifier could be generated
    …&SESSIONVAR!operator=ananya&SESSIONVAR!skill=timesmatri&imageUrl=http://&refer…

    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 4297, Column 180: entity was defined here
    …&file=visitorWantsToChat&site=26231671&SESSIONVAR!operator=ananya&SESSIONVAR!s…
  • Warning Line 4297, Column 236: cannot generate system identifier for general entity "imageUrl"
    …or=ananya&SESSIONVAR!skill=timesmatri&imageUrl=http://&referrer='+escape(docum…

    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 4297, Column 236: general entity "imageUrl" not defined and no default entity
    …or=ananya&SESSIONVAR!skill=timesmatri&imageUrl=http://&referrer='+escape(docum…

    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 4297, Column 244: reference not terminated by REFC delimiter
    …a&SESSIONVAR!skill=timesmatri&imageUrl=http://&referrer='+escape(document.loca…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 4297, Column 244: reference to external entity in attribute value
    …a&SESSIONVAR!skill=timesmatri&imageUrl=http://&referrer='+escape(document.loca…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 4297, Column 244: reference to entity "imageUrl" for which no system identifier could be generated
    …a&SESSIONVAR!skill=timesmatri&imageUrl=http://&referrer='+escape(document.loca…

    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 4297, Column 235: entity was defined here
    …tor=ananya&SESSIONVAR!skill=timesmatri&imageUrl=http://&referrer='+escape(docu…
  • Warning Line 4297, Column 253: cannot generate system identifier for general entity "referrer"
    …VAR!skill=timesmatri&imageUrl=http://&referrer='+escape(document.location),'ch…

    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 4297, Column 253: general entity "referrer" not defined and no default entity
    …VAR!skill=timesmatri&imageUrl=http://&referrer='+escape(document.location),'ch…

    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 4297, Column 261: reference not terminated by REFC delimiter
    …l=timesmatri&imageUrl=http://&referrer='+escape(document.location),'chat262316…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 4297, Column 261: reference to external entity in attribute value
    …l=timesmatri&imageUrl=http://&referrer='+escape(document.location),'chat262316…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 4297, Column 261: reference to entity "referrer" for which no system identifier could be generated
    …l=timesmatri&imageUrl=http://&referrer='+escape(document.location),'chat262316…

    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 4297, Column 252: entity was defined here
    …NVAR!skill=timesmatri&imageUrl=http://&referrer='+escape(document.location),'c…
  • Error Line 4302, Column 7: invalid comment declaration: found name character outside comment but inside comment declaration
    <!----- page header html end -----> <!----- page content html start ----->
  • Info Line 4302, Column 1: comment declaration started here
    <!----- page header html end -----> <!----- page content html start ----->
  • Error Line 4302, Column 43: invalid comment declaration: found name character outside comment but inside comment declaration
    <!----- page header html end -----> <!----- page content html start ----->
  • Info Line 4302, Column 37: comment declaration started here
    <!----- page header html end -----> <!----- page content html start ----->
  • Error Line 4304, Column 9: invalid comment declaration: found name character outside comment but inside comment declaration
    		<!----- what's new title start ----->
  • Info Line 4304, Column 3: comment declaration started here
    		<!----- what's new title start ----->
  • Error Line 4308, Column 13: invalid comment declaration: found name character outside comment but inside comment declaration
        	 <!----- what's new title end ----->
  • Info Line 4308, Column 7: comment declaration started here
        	 <!----- what's new title end ----->
  • Error Line 4346, Column 53: ID "cRs_2" already defined
    	onclick="return false;"> <img alt="left_arrow" id="cRs_2"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 157, Column 35: ID "cRs_2" first defined here
    		alt="Google Chrome browser" id="cRs_2"
  • Error Line 4353, Column 7: ID "cRs_3" already defined
    		id="cRs_3" src="/images/sm_smile_new.png"></div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 161, Column 7: ID "cRs_3" first defined here
    		id="cRs_3" src="/images/ie_opera_browser.png"></a></li>
  • Error Line 4353, Column 50: end tag for "img" omitted, but OMITTAG NO was specified
    		id="cRs_3" src="/images/sm_smile_new.png"></div>

    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 4352, Column 42: start tag was here
    	<div id="cRs_28" class="whatnew_ico fl"><img alt="gaana"
  • Error Line 4364, Column 7: ID "cRs_4" already defined
    		id="cRs_4" src="/images/sm_video_new.png"></div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 164, Column 39: ID "cRs_4" first defined here
    		alt="Internet explorer browser" id="cRs_4"
  • Error Line 4364, Column 50: end tag for "img" omitted, but OMITTAG NO was specified
    		id="cRs_4" src="/images/sm_video_new.png"></div>

    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 4363, Column 42: start tag was here
    	<div id="cRs_30" class="whatnew_ico fl"><img alt="video"
  • Error Line 4373, Column 7: ID "cRs_5" already defined
    		id="cRs_5" src="/images/sm_ganna_new.png"></div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 170, Column 18: ID "cRs_5" first defined here
    	alt="close" id="cRs_5" src="/images/ie_close_div.png"></a></div>
  • Error Line 4373, Column 50: end tag for "img" omitted, but OMITTAG NO was specified
    		id="cRs_5" src="/images/sm_ganna_new.png"></div>

    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 4372, Column 42: start tag was here
    	<div id="cRs_32" class="whatnew_ico fl"><img alt="gaana"
  • Error Line 4382, Column 50: end tag for "img" omitted, but OMITTAG NO was specified
    		id="cRs_6" src="/images/sm_photo_new.png"></div>

    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 4381, Column 42: start tag was here
    	<div id="cRs_34" class="whatnew_ico fl"><img alt="gaana"
  • Error Line 4390, Column 29: ID "cRs_189" already defined
    	<li style="margin: 0;" id="cRs_189">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4380, Column 29: ID "cRs_189" first defined here
    	<li style="margin: 0;" id="cRs_189">
  • Error Line 4391, Column 11: ID "cRs_34" already defined
    	<div id="cRs_34" class="whatnew_ico fl"><img alt="gaana"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4381, Column 11: ID "cRs_34" first defined here
    	<div id="cRs_34" class="whatnew_ico fl"><img alt="gaana"
  • Error Line 4392, Column 7: ID "cRs_6" already defined
    		id="cRs_6" src="/images/sm_Videomessage_new.gif"></div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4382, Column 7: ID "cRs_6" first defined here
    		id="cRs_6" src="/images/sm_photo_new.png"></div>
  • Error Line 4392, Column 57: end tag for "img" omitted, but OMITTAG NO was specified
    		id="cRs_6" src="/images/sm_Videomessage_new.gif"></div>

    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 4391, Column 42: start tag was here
    	<div id="cRs_34" class="whatnew_ico fl"><img alt="gaana"
  • Error Line 4393, Column 11: ID "cRs_35" already defined
    	<div id="cRs_35" class="smwntext fl">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4383, Column 11: ID "cRs_35" first defined here
    	<div id="cRs_35" class="smwntext fl">
  • Error Line 4394, Column 10: ID "cRs_251" already defined
    	<h2 id="cRs_251">Video Message</h2>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4384, Column 10: ID "cRs_251" first defined here
    	<h2 id="cRs_251">Photos</h2>
  • Error Line 4395, Column 9: ID "cRs_142" already defined
    	<p id="cRs_142">A picture says a thousand words; a video says a

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4385, Column 9: ID "cRs_142" first defined here
    	<p id="cRs_142">Share photo that&rsquo;s making your day memorable
  • Error Line 4400, Column 29: ID "cRs_189" already defined
    	<li style="margin: 0;" id="cRs_189">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4380, Column 29: ID "cRs_189" first defined here
    	<li style="margin: 0;" id="cRs_189">
  • Error Line 4401, Column 11: ID "cRs_34" already defined
    	<div id="cRs_34" class="whatnew_ico fl"><img alt="gaana"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4381, Column 11: ID "cRs_34" first defined here
    	<div id="cRs_34" class="whatnew_ico fl"><img alt="gaana"
  • Error Line 4402, Column 7: ID "cRs_6" already defined
    		id="cRs_6" src="/images/sm_si_new.png"></div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4382, Column 7: ID "cRs_6" first defined here
    		id="cRs_6" src="/images/sm_photo_new.png"></div>
  • Error Line 4402, Column 47: end tag for "img" omitted, but OMITTAG NO was specified
    		id="cRs_6" src="/images/sm_si_new.png"></div>

    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 4401, Column 42: start tag was here
    	<div id="cRs_34" class="whatnew_ico fl"><img alt="gaana"
  • Error Line 4403, Column 11: ID "cRs_35" already defined
    	<div id="cRs_35" class="smwntext fl">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4383, Column 11: ID "cRs_35" first defined here
    	<div id="cRs_35" class="smwntext fl">
  • Error Line 4404, Column 10: ID "cRs_251" already defined
    	<h2 id="cRs_251">Social Connect</h2>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4384, Column 10: ID "cRs_251" first defined here
    	<h2 id="cRs_251">Photos</h2>
  • Error Line 4405, Column 9: ID "cRs_142" already defined
    	<p id="cRs_142">The world is a small place. Find common contacts,

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4385, Column 9: ID "cRs_142" first defined here
    	<p id="cRs_142">Share photo that&rsquo;s making your day memorable
  • Error Line 4410, Column 29: ID "cRs_189" already defined
    	<li style="margin: 0;" id="cRs_189">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4380, Column 29: ID "cRs_189" first defined here
    	<li style="margin: 0;" id="cRs_189">
  • Error Line 4411, Column 11: ID "cRs_34" already defined
    	<div id="cRs_34" class="whatnew_ico fl"><img alt="gaana"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4381, Column 11: ID "cRs_34" first defined here
    	<div id="cRs_34" class="whatnew_ico fl"><img alt="gaana"
  • Error Line 4412, Column 7: ID "cRs_6" already defined
    		id="cRs_6" src="/images/sm_chat_new.png"></div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4382, Column 7: ID "cRs_6" first defined here
    		id="cRs_6" src="/images/sm_photo_new.png"></div>
  • Error Line 4412, Column 49: end tag for "img" omitted, but OMITTAG NO was specified
    		id="cRs_6" src="/images/sm_chat_new.png"></div>

    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 4411, Column 42: start tag was here
    	<div id="cRs_34" class="whatnew_ico fl"><img alt="gaana"
  • Error Line 4413, Column 11: ID "cRs_35" already defined
    	<div id="cRs_35" class="smwntext fl">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4383, Column 11: ID "cRs_35" first defined here
    	<div id="cRs_35" class="smwntext fl">
  • Error Line 4414, Column 10: ID "cRs_251" already defined
    	<h2 id="cRs_251">Simply Talk</h2>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4384, Column 10: ID "cRs_251" first defined here
    	<h2 id="cRs_251">Photos</h2>
  • Error Line 4415, Column 9: ID "cRs_142" already defined
    	<p id="cRs_142">&quot;Freedom of speech&quot;. Others charge you

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4385, Column 9: ID "cRs_142" first defined here
    	<p id="cRs_142">Share photo that&rsquo;s making your day memorable
  • Error Line 4420, Column 29: ID "cRs_189" already defined
    	<li style="margin: 0;" id="cRs_189">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4380, Column 29: ID "cRs_189" first defined here
    	<li style="margin: 0;" id="cRs_189">
  • Error Line 4421, Column 11: ID "cRs_34" already defined
    	<div id="cRs_34" class="whatnew_ico fl"><img alt="gaana"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4381, Column 11: ID "cRs_34" first defined here
    	<div id="cRs_34" class="whatnew_ico fl"><img alt="gaana"
  • Error Line 4422, Column 7: ID "cRs_6" already defined
    		id="cRs_6" src="/images/sm_photo_new.png"></div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4382, Column 7: ID "cRs_6" first defined here
    		id="cRs_6" src="/images/sm_photo_new.png"></div>
  • Error Line 4422, Column 50: end tag for "img" omitted, but OMITTAG NO was specified
    		id="cRs_6" src="/images/sm_photo_new.png"></div>

    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 4421, Column 42: start tag was here
    	<div id="cRs_34" class="whatnew_ico fl"><img alt="gaana"
  • Error Line 4423, Column 11: ID "cRs_35" already defined
    	<div id="cRs_35" class="smwntext fl">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4383, Column 11: ID "cRs_35" first defined here
    	<div id="cRs_35" class="smwntext fl">
  • Error Line 4424, Column 10: ID "cRs_251" already defined
    	<h2 id="cRs_251">Public Photos</h2>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4384, Column 10: ID "cRs_251" first defined here
    	<h2 id="cRs_251">Photos</h2>
  • Error Line 4425, Column 9: ID "cRs_142" already defined
    	<p id="cRs_142">There&rsquo; a lot more to you than your profile.

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4385, Column 9: ID "cRs_142" first defined here
    	<p id="cRs_142">Share photo that&rsquo;s making your day memorable
  • Error Line 4430, Column 29: ID "cRs_189" already defined
    	<li style="margin: 0;" id="cRs_189">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4380, Column 29: ID "cRs_189" first defined here
    	<li style="margin: 0;" id="cRs_189">
  • Error Line 4431, Column 11: ID "cRs_34" already defined
    	<div id="cRs_34" class="whatnew_ico fl"><img alt="gaana"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4381, Column 11: ID "cRs_34" first defined here
    	<div id="cRs_34" class="whatnew_ico fl"><img alt="gaana"
  • Error Line 4432, Column 7: ID "cRs_6" already defined
    		id="cRs_6" src="/images/sm_irecomend_new.gif"></div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4382, Column 7: ID "cRs_6" first defined here
    		id="cRs_6" src="/images/sm_photo_new.png"></div>
  • Error Line 4432, Column 54: end tag for "img" omitted, but OMITTAG NO was specified
    		id="cRs_6" src="/images/sm_irecomend_new.gif"></div>

    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 4431, Column 42: start tag was here
    	<div id="cRs_34" class="whatnew_ico fl"><img alt="gaana"
  • Error Line 4433, Column 11: ID "cRs_35" already defined
    	<div id="cRs_35" class="smwntext fl">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4383, Column 11: ID "cRs_35" first defined here
    	<div id="cRs_35" class="smwntext fl">
  • Error Line 4434, Column 10: ID "cRs_251" already defined
    	<h2 id="cRs_251">iRecommend</h2>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4384, Column 10: ID "cRs_251" first defined here
    	<h2 id="cRs_251">Photos</h2>
  • Error Line 4435, Column 9: ID "cRs_142" already defined
    	<p id="cRs_142">&quot;Facta non verba&quot;- deeds not words.

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4385, Column 9: ID "cRs_142" first defined here
    	<p id="cRs_142">Share photo that&rsquo;s making your day memorable
  • Error Line 4441, Column 29: ID "cRs_189" already defined
    	<li style="margin: 0;" id="cRs_189">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4380, Column 29: ID "cRs_189" first defined here
    	<li style="margin: 0;" id="cRs_189">
  • Error Line 4442, Column 11: ID "cRs_34" already defined
    	<div id="cRs_34" class="whatnew_ico fl"><img alt="gaana"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4381, Column 11: ID "cRs_34" first defined here
    	<div id="cRs_34" class="whatnew_ico fl"><img alt="gaana"
  • Error Line 4443, Column 7: ID "cRs_6" already defined
    		id="cRs_6" src="/images/sm_Smartinbox_new.gif"></div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4382, Column 7: ID "cRs_6" first defined here
    		id="cRs_6" src="/images/sm_photo_new.png"></div>
  • Error Line 4443, Column 55: end tag for "img" omitted, but OMITTAG NO was specified
    		id="cRs_6" src="/images/sm_Smartinbox_new.gif"></div>

    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 4442, Column 42: start tag was here
    	<div id="cRs_34" class="whatnew_ico fl"><img alt="gaana"
  • Error Line 4444, Column 11: ID "cRs_35" already defined
    	<div id="cRs_35" class="smwntext fl">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4383, Column 11: ID "cRs_35" first defined here
    	<div id="cRs_35" class="smwntext fl">
  • Error Line 4445, Column 10: ID "cRs_251" already defined
    	<h2 id="cRs_251">Smart Inbox</h2>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4384, Column 10: ID "cRs_251" first defined here
    	<h2 id="cRs_251">Photos</h2>
  • Error Line 4446, Column 9: ID "cRs_142" already defined
    	<p id="cRs_142">Smart messaging centre helps you communicate

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4385, Column 9: ID "cRs_142" first defined here
    	<p id="cRs_142">Share photo that&rsquo;s making your day memorable
  • Error Line 4451, Column 29: ID "cRs_189" already defined
    	<li style="margin: 0;" id="cRs_189">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4380, Column 29: ID "cRs_189" first defined here
    	<li style="margin: 0;" id="cRs_189">
  • Error Line 4452, Column 11: ID "cRs_34" already defined
    	<div id="cRs_34" class="whatnew_ico fl"><img alt="gaana"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4381, Column 11: ID "cRs_34" first defined here
    	<div id="cRs_34" class="whatnew_ico fl"><img alt="gaana"
  • Error Line 4453, Column 7: ID "cRs_6" already defined
    		id="cRs_6" src="/images/sm_ganna_new.png"></div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4382, Column 7: ID "cRs_6" first defined here
    		id="cRs_6" src="/images/sm_photo_new.png"></div>
  • Error Line 4453, Column 50: end tag for "img" omitted, but OMITTAG NO was specified
    		id="cRs_6" src="/images/sm_ganna_new.png"></div>

    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 4452, Column 42: start tag was here
    	<div id="cRs_34" class="whatnew_ico fl"><img alt="gaana"
  • Error Line 4454, Column 11: ID "cRs_35" already defined
    	<div id="cRs_35" class="smwntext fl">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4383, Column 11: ID "cRs_35" first defined here
    	<div id="cRs_35" class="smwntext fl">
  • Error Line 4455, Column 10: ID "cRs_251" already defined
    	<h2 id="cRs_251">Musically yours</h2>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4384, Column 10: ID "cRs_251" first defined here
    	<h2 id="cRs_251">Photos</h2>
  • Error Line 4456, Column 9: ID "cRs_142" already defined
    	<p id="cRs_142">Your musical choices say a lot about you. Find

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4385, Column 9: ID "cRs_142" first defined here
    	<p id="cRs_142">Share photo that&rsquo;s making your day memorable
  • Error Line 4461, Column 29: ID "cRs_189" already defined
    	<li style="margin: 0;" id="cRs_189">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4380, Column 29: ID "cRs_189" first defined here
    	<li style="margin: 0;" id="cRs_189">
  • Error Line 4462, Column 11: ID "cRs_34" already defined
    	<div id="cRs_34" class="whatnew_ico fl"><img alt="gaana"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4381, Column 11: ID "cRs_34" first defined here
    	<div id="cRs_34" class="whatnew_ico fl"><img alt="gaana"
  • Error Line 4463, Column 7: ID "cRs_6" already defined
    		id="cRs_6" src="/images/sm_PushMessagin_new.gif"></div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4382, Column 7: ID "cRs_6" first defined here
    		id="cRs_6" src="/images/sm_photo_new.png"></div>
  • Error Line 4463, Column 57: end tag for "img" omitted, but OMITTAG NO was specified
    		id="cRs_6" src="/images/sm_PushMessagin_new.gif"></div>

    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 4462, Column 42: start tag was here
    	<div id="cRs_34" class="whatnew_ico fl"><img alt="gaana"
  • Error Line 4464, Column 11: ID "cRs_35" already defined
    	<div id="cRs_35" class="smwntext fl">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4383, Column 11: ID "cRs_35" first defined here
    	<div id="cRs_35" class="smwntext fl">
  • Error Line 4465, Column 10: ID "cRs_251" already defined
    	<h2 id="cRs_251">Push Messaging</h2>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4384, Column 10: ID "cRs_251" first defined here
    	<h2 id="cRs_251">Photos</h2>
  • Error Line 4466, Column 9: ID "cRs_142" already defined
    	<p id="cRs_142">Site header automatically updates you on new

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4385, Column 9: ID "cRs_142" first defined here
    	<p id="cRs_142">Share photo that&rsquo;s making your day memorable
  • Error Line 4500, Column 26: character """ is not allowed in the value of attribute "id"
    		    		    				"<li id='" + i + "'><a href='' onclick='navigateToSuccessStory(…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 4500, Column 27: value of attribute "id" must be a single token
    		    		    				"<li id='" + i + "'><a href='' onclick='navigateToSuccessStory(…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 4500, Column 28: character "+" is not allowed in the value of attribute "id"
    		    		    				"<li id='" + i + "'><a href='' onclick='navigateToSuccessStory(…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 4500, Column 32: character "+" is not allowed in the value of attribute "id"
    		    		    				"<li id='" + i + "'><a href='' onclick='navigateToSuccessStory(…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 4500, Column 34: character """ is not allowed in the value of attribute "id"
    		    		    				"<li id='" + i + "'><a href='' onclick='navigateToSuccessStory(…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 4500, Column 36: document type does not allow element "li" here
    		    		    				"<li id='" + i + "'><a href='' onclick='navigateToSuccessStory(…

    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 4515, Column 10: ID "cRs_35" already defined
    <div id="cRs_35" class="smssimg fl"><img id="cRs_6"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4383, Column 11: ID "cRs_35" first defined here
    	<div id="cRs_35" class="smwntext fl">
  • Error Line 4515, Column 46: ID "cRs_6" already defined
    <div id="cRs_35" class="smssimg fl"><img id="cRs_6"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4382, Column 7: ID "cRs_6" first defined here
    		id="cRs_6" src="/images/sm_photo_new.png"></div>
  • Error Line 4516, Column 75: end tag for "img" omitted, but OMITTAG NO was specified
    	src="/images/sm_story3.jpg" class="fl" alt="Akshay Saxena and Neha"></div>

    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 4515, Column 37: start tag was here
    <div id="cRs_35" class="smssimg fl"><img id="cRs_6"
  • Error Line 4517, Column 10: ID "cRs_36" already defined
    <div id="cRs_36" class="smsscontent fl"><img alt="Success Stories"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4473, Column 10: ID "cRs_36" first defined here
    <div id="cRs_36" class="whatnew_rico fl"><a id="whatsNewNext"
  • Error Line 4518, Column 6: ID "cRs_7" already defined
    	id="cRs_7" src="/images/sm_sucesstories_img.png"> <font>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4474, Column 61: ID "cRs_7" first defined here
    	href="" onclick="return false;"> <img alt="left_arrow" id="cRs_7"
  • Error Line 4518, Column 51: end tag for "img" omitted, but OMITTAG NO was specified
    	id="cRs_7" src="/images/sm_sucesstories_img.png"> <font>

    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 4517, Column 41: start tag was here
    <div id="cRs_36" class="smsscontent fl"><img alt="Success Stories"
  • Error Line 4523, Column 8: ID "cRs_74" already defined
    <a id="cRs_74" href="/matrimonial/success-stories">Read more &raquo;</a></p>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 148, Column 42: ID "cRs_74" first defined here
    	<li id="cRs_202"><a target="_blank" id="cRs_74"
  • Error Line 4529, Column 10: ID "cRs_35" already defined
    <div id="cRs_35" class="smssimg fl"><img id="cRs_6"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4383, Column 11: ID "cRs_35" first defined here
    	<div id="cRs_35" class="smwntext fl">
  • Error Line 4529, Column 46: ID "cRs_6" already defined
    <div id="cRs_35" class="smssimg fl"><img id="cRs_6"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4382, Column 7: ID "cRs_6" first defined here
    		id="cRs_6" src="/images/sm_photo_new.png"></div>
  • Error Line 4530, Column 81: end tag for "img" omitted, but OMITTAG NO was specified
    …rc="/images/sm_story4.jpg" class="fl" alt="Deepika and Rahul Chaoudhary"></div>

    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 4529, Column 37: start tag was here
    <div id="cRs_35" class="smssimg fl"><img id="cRs_6"
  • Error Line 4531, Column 10: ID "cRs_36" already defined
    <div id="cRs_36" class="smsscontent fl"><img alt="Success Stories"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4473, Column 10: ID "cRs_36" first defined here
    <div id="cRs_36" class="whatnew_rico fl"><a id="whatsNewNext"
  • Error Line 4532, Column 6: ID "cRs_7" already defined
    	id="cRs_7" src="/images/sm_sucesstories_img.png"> <font>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4474, Column 61: ID "cRs_7" first defined here
    	href="" onclick="return false;"> <img alt="left_arrow" id="cRs_7"
  • Error Line 4532, Column 51: end tag for "img" omitted, but OMITTAG NO was specified
    	id="cRs_7" src="/images/sm_sucesstories_img.png"> <font>

    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 4531, Column 41: start tag was here
    <div id="cRs_36" class="smsscontent fl"><img alt="Success Stories"
  • Error Line 4533, Column 12: ID "cRs_153" already defined
        <b id="cRs_153">Deepika and Rahul Chaoudhary</b></font>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4519, Column 12: ID "cRs_153" first defined here
        <b id="cRs_153">Akshay Saxena and Neha</b></font>
  • Error Line 4534, Column 8: ID "cRs_136" already defined
    <p id="cRs_136">"We met through SimplyMarry.com and then after talking for some…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4520, Column 8: ID "cRs_136" first defined here
    <p id="cRs_136">
  • Error Line 4535, Column 8: ID "cRs_74" already defined
    <a id="cRs_74" href="/matrimonial/success-stories">Read more &raquo;</a></p>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 148, Column 42: ID "cRs_74" first defined here
    	<li id="cRs_202"><a target="_blank" id="cRs_74"
  • Error Line 4541, Column 10: ID "cRs_35" already defined
    <div id="cRs_35" class="smssimg fl"><img id="cRs_6"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4383, Column 11: ID "cRs_35" first defined here
    	<div id="cRs_35" class="smwntext fl">
  • Error Line 4541, Column 46: ID "cRs_6" already defined
    <div id="cRs_35" class="smssimg fl"><img id="cRs_6"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4382, Column 7: ID "cRs_6" first defined here
    		id="cRs_6" src="/images/sm_photo_new.png"></div>
  • Error Line 4542, Column 68: end tag for "img" omitted, but OMITTAG NO was specified
    	src="/images/sm_story5.jpg" class="fl" alt="Harsh and Veenu"></div>

    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 4541, Column 37: start tag was here
    <div id="cRs_35" class="smssimg fl"><img id="cRs_6"
  • Error Line 4543, Column 10: ID "cRs_36" already defined
    <div id="cRs_36" class="smsscontent fl"><img alt="Success Stories"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4473, Column 10: ID "cRs_36" first defined here
    <div id="cRs_36" class="whatnew_rico fl"><a id="whatsNewNext"
  • Error Line 4544, Column 6: ID "cRs_7" already defined
    	id="cRs_7" src="/images/sm_sucesstories_img.png"> <font><b

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4474, Column 61: ID "cRs_7" first defined here
    	href="" onclick="return false;"> <img alt="left_arrow" id="cRs_7"
  • Error Line 4544, Column 51: end tag for "img" omitted, but OMITTAG NO was specified
    	id="cRs_7" src="/images/sm_sucesstories_img.png"> <font><b

    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 4543, Column 41: start tag was here
    <div id="cRs_36" class="smsscontent fl"><img alt="Success Stories"
  • Error Line 4545, Column 6: ID "cRs_153" already defined
    	id="cRs_153">Harsh and Veenu</b></font>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4519, Column 12: ID "cRs_153" first defined here
        <b id="cRs_153">Akshay Saxena and Neha</b></font>
  • Error Line 4546, Column 8: ID "cRs_136" already defined
    <p id="cRs_136">"Our marriage got fixed through SimplyMarry.com, my parents fou…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4520, Column 8: ID "cRs_136" first defined here
    <p id="cRs_136">
  • Warning Line 4546, Column 123: character "&" is the first character of a delimiter but occurred as data
    … life partner here. Ours was arranged & we tied the knot on 29th November 2012…

    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 4547, Column 8: ID "cRs_74" already defined
    <a id="cRs_74" href="/matrimonial/success-stories">Read more &raquo;</a></p>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 148, Column 42: ID "cRs_74" first defined here
    	<li id="cRs_202"><a target="_blank" id="cRs_74"
  • Error Line 4570, Column 148: end tag for "img" omitted, but OMITTAG NO was specified
    …es advertisement" id="cRs_8" src="/images/sm_sales_banner.png" class="fl"></a> 

    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 4570, Column 58: start tag was here
    …al/take-a-tour" style="border: none;"><img alt="sales advertisement" id="cRs_8…
  • Error Line 4577, Column 10: ID "cRs_188" already defined
    	<li id="cRs_188"><b id="cRs_155">Mother Tongue</b></li>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4371, Column 10: ID "cRs_188" first defined here
    	<li id="cRs_188">
  • Error Line 4577, Column 26: ID "cRs_155" already defined
    	<li id="cRs_188"><b id="cRs_155">Mother Tongue</b></li>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 144, Column 8: ID "cRs_155" first defined here
    <p id="cRs_155"><b id="cRs_172"> We want you to experience best
  • Error Line 4578, Column 10: ID "cRs_189" already defined
    	<li id="cRs_189"><a id="cRs_80"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4380, Column 29: ID "cRs_189" first defined here
    	<li style="margin: 0;" id="cRs_189">
  • Error Line 4584, Column 10: ID "cRs_192" already defined
    	<li id="cRs_192"><a id="cRs_83"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 147, Column 9: ID "cRs_192" first defined here
    <ul id="cRs_192">
  • Error Line 4605, Column 10: ID "cRs_202" already defined
    	<li id="cRs_202"><a id="cRs_92"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 148, Column 10: ID "cRs_202" first defined here
    	<li id="cRs_202"><a target="_blank" id="cRs_74"
  • Error Line 4607, Column 10: ID "cRs_203" already defined
    	<li id="cRs_203"><a id="cRs_93"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 151, Column 10: ID "cRs_203" first defined here
    	<li id="cRs_203"><a target="_blank" id="cRs_75"
  • Error Line 4609, Column 10: ID "cRs_204" already defined
    	<li id="cRs_204"><a id="cRs_94"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 155, Column 10: ID "cRs_204" first defined here
    	<li id="cRs_204"><a target="_blank" id="cRs_76"
  • Error Line 4611, Column 10: ID "cRs_205" already defined
    	<li id="cRs_205"><a id="cRs_95"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 159, Column 10: ID "cRs_205" first defined here
    	<li id="cRs_205"><a target="_blank" id="cRs_77"
  • Error Line 4613, Column 10: ID "cRs_206" already defined
    	<li id="cRs_206"><b id="cRs_157">More</b></li>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 162, Column 29: ID "cRs_206" first defined here
    	<li style="margin: 0;" id="cRs_206"><a target="_blank" id="cRs_78"
  • Error Line 4620, Column 7: invalid comment declaration: found name character outside comment but inside comment declaration
    <!----- page content html end -----> <!----- page footer html start ----->
  • Info Line 4620, Column 1: comment declaration started here
    <!----- page content html end -----> <!----- page footer html start ----->
  • Error Line 4620, Column 44: invalid comment declaration: found name character outside comment but inside comment declaration
    <!----- page content html end -----> <!----- page footer html start ----->
  • Info Line 4620, Column 38: comment declaration started here
    <!----- page content html end -----> <!----- page footer html start ----->
  • Error Line 4621, Column 46: invalid comment declaration: found name character outside comment but inside comment declaration
    <div id="cRs_40" class="pagefooter fl"><!----- SM Page links 1 html ----->
  • Info Line 4621, Column 40: comment declaration started here
    <div id="cRs_40" class="pagefooter fl"><!----- SM Page links 1 html ----->
  • Error Line 4655, Column 32: required attribute "alt" not specified
    	src="/images/fb_foter_ico.png"></a> <a id="cRs_111"

    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 4655, Column 36: end tag for "img" omitted, but OMITTAG NO was specified
    	src="/images/fb_foter_ico.png"></a> <a id="cRs_111"

    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 4654, Column 58: start tag was here
    	id="cRs_110" href="http://www.facebook.com/SimplyMarry"><img id="cRs_9"
  • Error Line 4657, Column 36: required attribute "alt" not specified
    	src="/images/twiter_foter_ico.png"></a></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>.

  • Error Line 4657, Column 40: end tag for "img" omitted, but OMITTAG NO was specified
    	src="/images/twiter_foter_ico.png"></a></div>

    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 4656, Column 43: start tag was here
    	href="http://twitter.com/simplymarry_sm"><img id="cRs_10"
  • Error Line 4659, Column 7: invalid comment declaration: found name character outside comment but inside comment declaration
    <!----- SM Page links 2 html ----->
  • Info Line 4659, Column 1: comment declaration started here
    <!----- SM Page links 2 html ----->
  • Error Line 4672, Column 7: invalid comment declaration: found name character outside comment but inside comment declaration
    <!----- SM Page links 3 html ----->
  • Info Line 4672, Column 1: comment declaration started here
    <!----- SM Page links 3 html ----->
  • Error Line 4689, Column 7: invalid comment declaration: found name character outside comment but inside comment declaration
    <!----- rbsl networks links html ----->
  • Info Line 4689, Column 1: comment declaration started here
    <!----- rbsl networks links html ----->
  • Error Line 4700, Column 9: ID "cRs_139" already defined
    	<p id="cRs_139"><a id="cRs_120" href="http://simplymarry.com/" rel="nofollow">…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4356, Column 9: ID "cRs_139" first defined here
    	<p id="cRs_139">SMile is Simply Marry&rsquo;s Interactive
  • Error Line 4703, Column 9: ID "cRs_140" already defined
    	<p id="cRs_140"><a target="_blank" id="cRs_121"	href="http://swyamvars.com/" r…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4367, Column 9: ID "cRs_140" first defined here
    	<p id="cRs_140">Send your favourite youtube videos and forward that
  • Error Line 4706, Column 9: ID "cRs_141" already defined
    	<p id="cRs_141"><a target="_blank" id="cRs_122"	href="http://techgig.com/" rel…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4376, Column 9: ID "cRs_141" first defined here
    	<p id="cRs_141">Share the song that you&rsquo;re humming today and
  • Error Line 4709, Column 9: ID "cRs_142" already defined
    	<p id="cRs_142"><a target="_blank" id="cRs_123" href="http://ads2book.com/" re…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 4385, Column 9: ID "cRs_142" first defined here
    	<p id="cRs_142">Share photo that&rsquo;s making your day memorable
  • Error Line 4716, Column 7: invalid comment declaration: found name character outside comment but inside comment declaration
    <!----- SM Page links 4 html ----->
  • Info Line 4716, Column 1: comment declaration started here
    <!----- SM Page links 4 html ----->
  • Error Line 4718, Column 9: ID "cRs_172" already defined
    <ul id="cRs_172">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 144, Column 24: ID "cRs_172" first defined here
    <p id="cRs_155"><b id="cRs_172"> We want you to experience best
  • Warning Line 4723, Column 124: cannot generate system identifier for general entity "seType"
    …k/onlineFeedbackForm.html?siteId=1023&seType=simplymarry.com');">Feedback</a><…

    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 4723, Column 124: general entity "seType" not defined and no default entity
    …k/onlineFeedbackForm.html?siteId=1023&seType=simplymarry.com');">Feedback</a><…

    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 4723, Column 130: reference not terminated by REFC delimiter
    …nlineFeedbackForm.html?siteId=1023&seType=simplymarry.com');">Feedback</a></li>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 4723, Column 130: reference to external entity in attribute value
    …nlineFeedbackForm.html?siteId=1023&seType=simplymarry.com');">Feedback</a></li>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 4723, Column 130: reference to entity "seType" for which no system identifier could be generated
    …nlineFeedbackForm.html?siteId=1023&seType=simplymarry.com');">Feedback</a></li>

    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 4723, Column 123: entity was defined here
    …ck/onlineFeedbackForm.html?siteId=1023&seType=simplymarry.com');">Feedback</a>…
  • Warning Line 4736, Column 188: reference not terminated by REFC delimiter
    …eperson.net/hc/26231671/?cmd=file&file=visitorWantsToChat&site=26231671&SESSIO…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 4736, Column 188: reference to external entity in attribute value
    …eperson.net/hc/26231671/?cmd=file&file=visitorWantsToChat&site=26231671&SESSIO…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 4736, Column 188: reference to entity "file" for which no system identifier could be generated
    …eperson.net/hc/26231671/?cmd=file&file=visitorWantsToChat&site=26231671&SESSIO…

    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 4297, Column 142: entity was defined here
    …d.liveperson.net/hc/26231671/?cmd=file&file=visitorWantsToChat&site=26231671&S…
  • Warning Line 4736, Column 212: reference not terminated by REFC delimiter
    …?cmd=file&file=visitorWantsToChat&site=26231671&SESSIONVAR!operator=ananya&SES…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 4736, Column 212: reference to external entity in attribute value
    …?cmd=file&file=visitorWantsToChat&site=26231671&SESSIONVAR!operator=ananya&SES…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 4736, Column 212: reference to entity "site" for which no system identifier could be generated
    …?cmd=file&file=visitorWantsToChat&site=26231671&SESSIONVAR!operator=ananya&SES…

    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 4297, Column 166: entity was defined here
    …1671/?cmd=file&file=visitorWantsToChat&site=26231671&SESSIONVAR!operator=anany…
  • Warning Line 4736, Column 232: reference not terminated by REFC delimiter
    …orWantsToChat&site=26231671&SESSIONVAR!operator=ananya&SESSIONVAR!skill=timesm…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 4736, Column 232: reference to external entity in attribute value
    …orWantsToChat&site=26231671&SESSIONVAR!operator=ananya&SESSIONVAR!skill=timesm…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 4736, Column 232: reference to entity "SESSIONVAR" for which no system identifier could be generated
    …orWantsToChat&site=26231671&SESSIONVAR!operator=ananya&SESSIONVAR!skill=timesm…

    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 4297, Column 180: entity was defined here
    …&file=visitorWantsToChat&site=26231671&SESSIONVAR!operator=ananya&SESSIONVAR!s…
  • Warning Line 4736, Column 259: reference not terminated by REFC delimiter
    …&SESSIONVAR!operator=ananya&SESSIONVAR!skill=timesmatri&imageUrl=http://&refer…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 4736, Column 259: reference to external entity in attribute value
    …&SESSIONVAR!operator=ananya&SESSIONVAR!skill=timesmatri&imageUrl=http://&refer…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 4736, Column 259: reference to entity "SESSIONVAR" for which no system identifier could be generated
    …&SESSIONVAR!operator=ananya&SESSIONVAR!skill=timesmatri&imageUrl=http://&refer…

    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 4297, Column 180: entity was defined here
    …&file=visitorWantsToChat&site=26231671&SESSIONVAR!operator=ananya&SESSIONVAR!s…
  • Warning Line 4736, Column 285: reference not terminated by REFC delimiter
    …a&SESSIONVAR!skill=timesmatri&imageUrl=http://&referrer='+escape(document.loca…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 4736, Column 285: reference to external entity in attribute value
    …a&SESSIONVAR!skill=timesmatri&imageUrl=http://&referrer='+escape(document.loca…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 4736, Column 285: reference to entity "imageUrl" for which no system identifier could be generated
    …a&SESSIONVAR!skill=timesmatri&imageUrl=http://&referrer='+escape(document.loca…

    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 4297, Column 235: entity was defined here
    …tor=ananya&SESSIONVAR!skill=timesmatri&imageUrl=http://&referrer='+escape(docu…
  • Warning Line 4736, Column 302: reference not terminated by REFC delimiter
    …l=timesmatri&imageUrl=http://&referrer='+escape(document.location),'chat262316…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 4736, Column 302: reference to external entity in attribute value
    …l=timesmatri&imageUrl=http://&referrer='+escape(document.location),'chat262316…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 4736, Column 302: reference to entity "referrer" for which no system identifier could be generated
    …l=timesmatri&imageUrl=http://&referrer='+escape(document.location),'chat262316…

    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 4297, Column 252: entity was defined here
    …NVAR!skill=timesmatri&imageUrl=http://&referrer='+escape(document.location),'c…
  • Error Line 4740, 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 4756, Column 123: required attribute "alt" not specified
    …en()"><img src="http://swyamvars.com/images/phone_slider.png" border="0" /></a>

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

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

  • Error Line 4760, Column 129: required attribute "alt" not specified
    …><img src="http://swyamvars.com/images/phone_slider_open.png" border="0" /></a>

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

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

  • Error Line 4765, Column 7: invalid comment declaration: found name character outside comment but inside comment declaration
    <!----- SM footer content html ----->
  • Info Line 4765, Column 1: comment declaration started here
    <!----- SM footer content html ----->
  • Error Line 4781, Column 7: invalid comment declaration: found name character outside comment but inside comment declaration
    <!----- page footer html end -----></div>
  • Info Line 4781, Column 1: comment declaration started here
    <!----- page footer html end -----></div>
  • Error Line 4789, Column 51: an attribute specification must start with a name or name token
    		var chatFrame = "<iframe name='chatWindowFrame' " +

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 4789, Column 51: document type does not allow element "iframe" here
    		var chatFrame = "<iframe name='chatWindowFrame' " +

    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 4817, Column 11: document type does not allow element "noscript" here
    	<noscript><img src="http://b.scorecardresearch.com/p?c1=2&c2=6036484&cv=2.0&cj…

    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 4817, Column 60: cannot generate system identifier for general entity "c2"
    …rc="http://b.scorecardresearch.com/p?c1=2&c2=6036484&cv=2.0&cj=1" /></noscript>

    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 4817, Column 60: general entity "c2" not defined and no default entity
    …rc="http://b.scorecardresearch.com/p?c1=2&c2=6036484&cv=2.0&cj=1" /></noscript>

    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 4817, Column 62: reference not terminated by REFC delimiter
    …rc="http://b.scorecardresearch.com/p?c1=2&c2=6036484&cv=2.0&cj=1" /></noscript>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 4817, Column 62: reference to external entity in attribute value
    …rc="http://b.scorecardresearch.com/p?c1=2&c2=6036484&cv=2.0&cj=1" /></noscript>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 4817, Column 62: reference to entity "c2" for which no system identifier could be generated
    …rc="http://b.scorecardresearch.com/p?c1=2&c2=6036484&cv=2.0&cj=1" /></noscript>

    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 4817, Column 59: entity was defined here
    …rc="http://b.scorecardresearch.com/p?c1=2&c2=6036484&cv=2.0&cj=1" /></noscript>
  • Warning Line 4817, Column 71: cannot generate system identifier for general entity "cv"
    …rc="http://b.scorecardresearch.com/p?c1=2&c2=6036484&cv=2.0&cj=1" /></noscript>

    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 4817, Column 71: general entity "cv" not defined and no default entity
    …rc="http://b.scorecardresearch.com/p?c1=2&c2=6036484&cv=2.0&cj=1" /></noscript>

    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 4817, Column 73: reference not terminated by REFC delimiter
    …rc="http://b.scorecardresearch.com/p?c1=2&c2=6036484&cv=2.0&cj=1" /></noscript>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 4817, Column 73: reference to external entity in attribute value
    …rc="http://b.scorecardresearch.com/p?c1=2&c2=6036484&cv=2.0&cj=1" /></noscript>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 4817, Column 73: reference to entity "cv" for which no system identifier could be generated
    …rc="http://b.scorecardresearch.com/p?c1=2&c2=6036484&cv=2.0&cj=1" /></noscript>

    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 4817, Column 70: entity was defined here
    …rc="http://b.scorecardresearch.com/p?c1=2&c2=6036484&cv=2.0&cj=1" /></noscript>
  • Warning Line 4817, Column 78: cannot generate system identifier for general entity "cj"
    …rc="http://b.scorecardresearch.com/p?c1=2&c2=6036484&cv=2.0&cj=1" /></noscript>

    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 4817, Column 78: general entity "cj" not defined and no default entity
    …rc="http://b.scorecardresearch.com/p?c1=2&c2=6036484&cv=2.0&cj=1" /></noscript>

    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 4817, Column 80: reference not terminated by REFC delimiter
    …rc="http://b.scorecardresearch.com/p?c1=2&c2=6036484&cv=2.0&cj=1" /></noscript>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 4817, Column 80: reference to external entity in attribute value
    …rc="http://b.scorecardresearch.com/p?c1=2&c2=6036484&cv=2.0&cj=1" /></noscript>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 4817, Column 80: reference to entity "cj" for which no system identifier could be generated
    …rc="http://b.scorecardresearch.com/p?c1=2&c2=6036484&cv=2.0&cj=1" /></noscript>

    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 4817, Column 77: entity was defined here
    …rc="http://b.scorecardresearch.com/p?c1=2&c2=6036484&cv=2.0&cj=1" /></noscript>
  • Error Line 4817, Column 85: required attribute "alt" not specified
    …rc="http://b.scorecardresearch.com/p?c1=2&c2=6036484&cv=2.0&cj=1" /></noscript>

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

Visitor Analysis

Daily Visitor
  • 8.517 visits
Daily Visitor