abcmouse.com

ABCmouse.com helps kids learn to read through phonics, and teaches lessons in math, social studies, art, music, and much more. For kids age 2 to Kindergarten. ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    abcmouse.com
  • Favicon
  • Alexa Rank
    #11119
  • Google Page Rank
    PR 5
  • Ip Address
    54.244.116.30
  • Page Size
    107.6 KB
  • Images
    1 GIF, 1 JPG, 86 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    15 5 0 0 0 0

Website Meta Analysis



  • Title
    ABCmouse: Kids Learning, Phonics, Educational Games, Preschool-Kindergarten Reading
  • Meta Keyword
    Learn, learning, learn to read, math, early learning, early childhood education, online books, phonics, printables, pbs, pbskids.com, starfall, starfall.com, funbrain, teacher
  • Meta Description
    ABCmouse.com helps kids learn to read through phonics, and teaches lessons in math, social studies, art, music, and much more. For kids age 2 to Kindergarten.

Technical Analysis



  • Webserver
    Apache/2.2.22 (Ubuntu)
  • Ip Address
    54.244.116.30
  • Domain Age
    6 Years, 8 Months, 2 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: no-store, no-cache
  • content-encoding: gzip
  • content-type: text/html; charset=UTF-8
  • date: Thu, 19 Sep 2013 11:44:03 GMT
  • expires: Mon, 26 Jul 1997 05:00:00 GMT
  • last-modified: Thu, 19 Sep 2013 11:44:03 GMT
  • pragma: no-cache
  • server: Apache/2.2.22 (Ubuntu)
  • vary: Accept-Encoding
  • x-host: www54.or.aofk.net
  • x-powered-by: PHP/5.4.6-1ubuntu1.1
  • content-length: 22166
  • connection: keep-alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for abcmouse.com

DNS Analysis


DNS servers
ns1.aofk.net
ns2.aofk.net
ns3.aofk.net
ns4.aofk.net


DNS Records

Answer records
abcmouse.com SOA
server: ns1.aofk.net
email: postmaster@aofl.com
serial: -1344714079
refresh: 3600
retry: 600
expire: 604800
minimum ttl: 300
300s
abcmouse.com TXT v=spf1 mx ip4:69.28.183.160/27 ip4:64.197.230.112/28 ip4:209.92.85.177/28 ip4:70.39.129.129/27 ~all 300s
abcmouse.com MX
preference: 10
exchange: aofl.totalemaildefense.com
300s
abcmouse.com MX
preference: 20
exchange: aofl-com.totalemaildefense.com
300s
abcmouse.com NS  ns2.aofk.net 300s
abcmouse.com NS  ns1.aofk.net 300s
abcmouse.com NS  ns4.aofk.net 300s
abcmouse.com NS  ns3.aofk.net 300s
abcmouse.com A 70.39.129.134 300s
abcmouse.com A 70.39.129.135 300s
abcmouse.com A 70.39.129.136 300s
abcmouse.com A 70.39.129.137 300s
abcmouse.com A 69.28.183.166 300s
abcmouse.com A 69.28.183.167 300s
abcmouse.com A 69.28.183.168 300s
abcmouse.com A 69.28.183.169 300s

Authority records

Additional records
ns1.aofk.net A 70.39.129.133 300s
ns2.aofk.net A 69.28.183.165 300s

IP 54.244.116.30 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 72 Errors
  • 76 Warnings
Ratio Text/Html
  • 0.47924001016223283
Message Error
  • Warning Line 135, Column 37: character "&" is the first character of a delimiter but occurred as data
    			if(swf("rolloverplayer") != null && (typeof swf("rolloverplayer").startSound…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 135, Column 38: character "&" is the first character of a delimiter but occurred as data
    			if(swf("rolloverplayer") != null && (typeof swf("rolloverplayer").startSound…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 149, Column 37: character "&" is the first character of a delimiter but occurred as data
    			if(swf("rolloverplayer") != null && (typeof swf("rolloverplayer").cacheFile …

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 149, Column 38: character "&" is the first character of a delimiter but occurred as data
    			if(swf("rolloverplayer") != null && (typeof swf("rolloverplayer").cacheFile …

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 162, Column 37: character "&" is the first character of a delimiter but occurred as data
    			if(swf("rolloverplayer") != null && (typeof swf("rolloverplayer").cacheFile …

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 162, Column 38: character "&" is the first character of a delimiter but occurred as data
    			if(swf("rolloverplayer") != null && (typeof swf("rolloverplayer").cacheFile …

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 194, Column 29: character "&" is the first character of a delimiter but occurred as data
    			if(homepageVersion == 42 && getCookie("freeSiteAudio") == "") {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 194, Column 30: character "&" is the first character of a delimiter but occurred as data
    			if(homepageVersion == 42 && getCookie("freeSiteAudio") == "") {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 207, Column 27: character "&" is the first character of a delimiter but occurred as data
    			if(!VideoPlayer.isOpen && !FlowVideoPlayer.isOpen && homepageVersion == 158)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 207, Column 28: character "&" is the first character of a delimiter but occurred as data
    			if(!VideoPlayer.isOpen && !FlowVideoPlayer.isOpen && homepageVersion == 158)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 207, Column 54: character "&" is the first character of a delimiter but occurred as data
    			if(!VideoPlayer.isOpen && !FlowVideoPlayer.isOpen && homepageVersion == 158)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 207, Column 55: character "&" is the first character of a delimiter but occurred as data
    			if(!VideoPlayer.isOpen && !FlowVideoPlayer.isOpen && homepageVersion == 158)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 245, Column 18: character "<" is the first character of a delimiter but occurred as data
    				if(marginTop < 0) { marginTop = 4; }

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 292, Column 18: character "<" is the first character of a delimiter but occurred as data
    				if(marginTop < 0) { marginTop = 4; }

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 357, Column 29: character "&" is the first character of a delimiter but occurred as data
    				var forceSurvey = false && /siteoverview/.test(file);

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 357, Column 30: character "&" is the first character of a delimiter but occurred as data
    				var forceSurvey = false && /siteoverview/.test(file);

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 363, Column 65: character "&" is the first character of a delimiter but occurred as data
    …t(file) || inArray(file, signUpVids)) && (homepageVersion == 211 || homepageVe…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 363, Column 66: character "&" is the first character of a delimiter but occurred as data
    …(file) || inArray(file, signUpVids)) && (homepageVersion == 211 || homepageVer…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 388, Column 32: character "&" is the first character of a delimiter but occurred as data
    					if(homepageVersion >= 222 && getCookie("elog") == "") {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 388, Column 33: character "&" is the first character of a delimiter but occurred as data
    					if(homepageVersion >= 222 && getCookie("elog") == "") {

    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 393, Column 96: document type does not allow element "div" here
    …nd_video_popup" style="display: none;"><iframe src="/email_special/3/multi/211…

    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 393, Column 258: there is no attribute "allowtransparency"
    …="0" scrolling="no" allowtransparency="true" style="background-color:transpare…

    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 396, Column 57: ID "end_video_popup" already defined
    …ideoPopupCondfig = { popup: '<div id="end_video_popup" style="display: none;">…

    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 393, Column 57: ID "end_video_popup" first defined here
    …ideoPopupCondfig = { popup: '<div id="end_video_popup" style="display: none;">…
  • Error Line 396, Column 96: document type does not allow element "div" here
    …nd_video_popup" style="display: none;"><iframe src="/email_special/3/multi/211…

    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 400, Column 41: character "&" is the first character of a delimiter but occurred as data
    				} else if(/siteoverview/.test(file) && homepageVersion >= 208) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 400, Column 42: character "&" is the first character of a delimiter but occurred as data
    				} else if(/siteoverview/.test(file) && homepageVersion >= 208) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 409, Column 34: character "&" is the first character of a delimiter but occurred as data
    				if(/siteoverview/.test(file) && homepageVersion == 207) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 409, Column 35: character "&" is the first character of a delimiter but occurred as data
    				if(/siteoverview/.test(file) && homepageVersion == 207) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 421, Column 43: character "&" is the first character of a delimiter but occurred as data
    					if(getCookie("firstMonthFree") == "" && homepageVersion == 202) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 421, Column 44: character "&" is the first character of a delimiter but occurred as data
    					if(getCookie("firstMonthFree") == "" && homepageVersion == 202) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 426, Column 35: character "&" is the first character of a delimiter but occurred as data
    					if(/siteoverview/.test(file) && (getCookie("firstMonthFree") != "" || home…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 426, Column 36: character "&" is the first character of a delimiter but occurred as data
    					if(/siteoverview/.test(file) && (getCookie("firstMonthFree") != "" || home…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 436, Column 38: character "&" is the first character of a delimiter but occurred as data
    				if(swf("learn-more-btn") != null && (typeof swf("learn-more-btn").stopAnima…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 436, Column 39: character "&" is the first character of a delimiter but occurred as data
    				if(swf("learn-more-btn") != null && (typeof swf("learn-more-btn").stopAnima…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 515, Column 14: character "<" is the first character of a delimiter but occurred as data
    				if(pos.y < 10) pos.y = 10;

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 633, Column 18: character "<" is the first character of a delimiter but occurred as data
    				if(marginTop < 5) { marginTop = 5; }

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 743, Column 20: character "<" is the first character of a delimiter but occurred as data
    				for(var x=0; x < images.length; x++) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 744, Column 51: character "&" is the first character of a delimiter but occurred as data
    					if(images[x].getAttribute("onclick") == null && isAPopup(images[x].id)) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 744, Column 52: character "&" is the first character of a delimiter but occurred as data
    					if(images[x].getAttribute("onclick") == null && isAPopup(images[x].id)) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 759, Column 20: character "<" is the first character of a delimiter but occurred as data
    				for(var x=0; x < popupsInfo.length; x++) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 770, Column 20: character "<" is the first character of a delimiter but occurred as data
    				for(var x=0; x < popupsInfo.length; x++) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 790, Column 31: character "<" is the first character of a delimiter but occurred as data
    					position.x = (position.x < 0) ? 0 : position.x;

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 791, Column 31: character "<" is the first character of a delimiter but occurred as data
    					position.y = (position.y < 0) ? 0 : position.y;

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 809, Column 30: character "&" is the first character of a delimiter but occurred as data
    				} else if( document.body && ( document.body.scrollLeft || document.body.scr…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 809, Column 31: character "&" is the first character of a delimiter but occurred as data
    				} else if( document.body && ( document.body.scrollLeft || document.body.scr…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 813, Column 41: character "&" is the first character of a delimiter but occurred as data
    …		} else if( document.documentElement && ( document.documentElement.scrollLeft…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 813, Column 42: character "&" is the first character of a delimiter but occurred as data
    …	} else if( document.documentElement && ( document.documentElement.scrollLeft …

    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 913, Column 226: document type does not allow element "iframe" here
    …no" allowtransparency="true" style="background-color: transparent;"></iframe>';

    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 914, Column 273: document type does not allow element "iframe" here
    …lute; left: 32%; top: 0px; background-color:transparent;z-index:400;"></iframe>

    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 986, Column 27: character "&" is the first character of a delimiter but occurred as data
    				if(VideoPlayer.isOpen && videoPlayerId >= 0) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 986, Column 28: character "&" is the first character of a delimiter but occurred as data
    				if(VideoPlayer.isOpen && videoPlayerId >= 0) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 990, Column 44: character "&" is the first character of a delimiter but occurred as data
    …f(getCookie("survey-completed") == "" && ((homepageVersion != 88 && homepageVe…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 990, Column 45: character "&" is the first character of a delimiter but occurred as data
    …(getCookie("survey-completed") == "" && ((homepageVersion != 88 && homepageVer…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 990, Column 71: character "&" is the first character of a delimiter but occurred as data
    …ed") == "" && ((homepageVersion != 88 && homepageVersion != 89 && homepageVers…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 990, Column 72: character "&" is the first character of a delimiter but occurred as data
    …d") == "" && ((homepageVersion != 88 && homepageVersion != 89 && homepageVersi…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 990, Column 96: character "&" is the first character of a delimiter but occurred as data
    …ersion != 88 && homepageVersion != 89 && homepageVersion != 134 && homepageVer…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 990, Column 97: character "&" is the first character of a delimiter but occurred as data
    …rsion != 88 && homepageVersion != 89 && homepageVersion != 134 && homepageVers…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 990, Column 122: character "&" is the first character of a delimiter but occurred as data
    …rsion != 89 && homepageVersion != 134 && homepageVersion != 151) || forceSurve…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 990, Column 123: character "&" is the first character of a delimiter but occurred as data
    …sion != 89 && homepageVersion != 134 && homepageVersion != 151) || forceSurvey…

    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 1027, Column 46: document type does not allow element "div" here
    				var errorMessage = '<div id="errorsPopup">' +

    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 1038, Column 111: required attribute "alt" not specified
    …se.com/home/survey-popup/ok-btn.png" onclick="closeSurveyErrorMessage();" />' +

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

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

  • Warning Line 1065, Column 37: character "&" is the first character of a delimiter but occurred as data
    				// necessary for Safari: mobile & desktop

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1086, Column 22: character "&" is the first character of a delimiter but occurred as data
    				if(pixel != null && getCookie("wait-popup") == "")

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1086, Column 23: character "&" is the first character of a delimiter but occurred as data
    				if(pixel != null && getCookie("wait-popup") == "")

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1135, Column 31: character "&" is the first character of a delimiter but occurred as data
    				if(FlowVideoPlayer.isOpen && FlowVideoPlayer.currentInstance) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1135, Column 32: character "&" is the first character of a delimiter but occurred as data
    				if(FlowVideoPlayer.isOpen && FlowVideoPlayer.currentInstance) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1144, Column 31: character "&" is the first character of a delimiter but occurred as data
    				if(homepageVersion == 379 && getCookie("sweepstakes_popup") == "") {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1144, Column 32: character "&" is the first character of a delimiter but occurred as data
    				if(homepageVersion == 379 && getCookie("sweepstakes_popup") == "") {

    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 1317, Column 32: document type does not allow element "script" here; assuming missing "body" start-tag
    	<script type="text/javascript">
  • Error Line 1329, Column 79: document type does not allow element "body" here
    </script>	<body onunload="track('homepageExit');" onclick="removeWaitPixel();">

    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 1336, Column 279: document type does not allow element "iframe" here
    …k; background-color:transparent; margin: 0px; position: relative;"></iframe>');

    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 1353, Column 28: there is no attribute "src"
                    <embed src="/artwork/home/rolloverplayer.swf" wmode="transparen…

    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 1353, Column 69: there is no attribute "wmode"
    …rtwork/home/rolloverplayer.swf" wmode="transparent" name="rolloverplayer" widt…

    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 1353, Column 88: there is no attribute "name"
    …rplayer.swf" wmode="transparent" name="rolloverplayer" width="1" height="1" al…

    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 1353, Column 111: there is no attribute "width"
    …nsparent" name="rolloverplayer" width="1" height="1" allowScriptAccess="always…

    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 1353, Column 122: there is no attribute "height"
    …ame="rolloverplayer" width="1" height="1" allowScriptAccess="always" type="app…

    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 1353, Column 144: there is no attribute "allowScriptAccess"
    …idth="1" height="1" allowScriptAccess="always" type="application/x-shockwave-f…

    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 1353, Column 158: there is no attribute "type"
    …t="1" allowScriptAccess="always" type="application/x-shockwave-flash" pluginsp…

    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 1353, Column 202: there is no attribute "pluginspage"
    …cation/x-shockwave-flash" pluginspage="http://www.macromedia.com/go/getflashpl…

    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 1353, Column 249: element "embed" undefined
    …x-shockwave-flash" pluginspage="http://www.macromedia.com/go/getflashplayer" />

    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 1361, Column 125: there is no attribute "onload"
    …regpath/html5/nmhp/bg_top.png" onload="loader(this);" border="0" alt="ABC mous…

    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 1401, Column 840: required attribute "alt" not specified
    …timonial.png" onload="loader(this);" />					<div style="position: absolute; bo…

    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 1401, Column 1185: required attribute "alt" not specified
    …1/awards.png" onload="loader(this);" />					</div>				</div>				<div style="fl…

    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 1401, Column 1335: there is no attribute "onload"
    …iframe id="specialOfferIframe" onload="loader(this);" src="/email_special/1/mu…

    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 1436, Column 855: reference not terminated by REFC delimiter
    …class='sectionpreviewquotesign'>&#8212Crystal, mother of 3- and 5-year-old gir…

    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 1446, Column 822: reference not terminated by REFC delimiter
    …class='sectionpreviewquotesign'>&#8212Sarah, mother of a 5-year-old girl and a…

    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 1467, Column 1001: reference not terminated by REFC delimiter
    …class='sectionpreviewquotesign'>&#8212Morgyn, mother of a 2-year-old girl		</d…

    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 1467, Column 3383: reference not terminated by REFC delimiter
    …t of the ABCmouse.com curriculum&#8212whether it is the sound of a letter, the…

    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 1467, Column 3489: reference not terminated by REFC delimiter
    …13;5, or the seasons of the year&#8212is explained in child-friendly language …

    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 1516, Column 955: reference not terminated by REFC delimiter
    …class='sectionpreviewquotesign'>&#8212Jennifer, mother of a -2-year-old boy an…

    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 1534, Column 989: reference not terminated by REFC delimiter
    …class='sectionpreviewquotesign'>&#8212Rosanne, mother of 1 and 3-year-old girl…

    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 1552, Column 1005: reference not terminated by REFC delimiter
    …class='sectionpreviewquotesign'>&#8212Yvonne, mother of a 2-year-old boy		</di…

    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 1571, Column 812: reference not terminated by REFC delimiter
    …class='sectionpreviewquotesign'>&#8212Amanda, mother of a 3-year-old girl		</d…

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

  • Error Line 1571, Column 4098: required attribute "alt" not specified
    …bcmouse.com/home/homepage/blank.png' /></div><div id='tripleSection2' class='t…

    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 1571, Column 6495: required attribute "alt" not specified
    …bcmouse.com/home/homepage/blank.png' /></div><div id='tripleSection3' class='t…

    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 1571, Column 8708: required attribute "alt" not specified
    …bcmouse.com/home/homepage/blank.png' /></div>    <div  style="text-align: cent…

    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 1573, Column 13: ID "top" already defined
    			<div id="top"></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 1028, Column 16: ID "top" first defined here
    					'<div id="top">' +
  • Error Line 1601, Column 13: ID "bottom" already defined
    			<div id="bottom"></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 1041, Column 16: ID "bottom" first defined here
    					'<div id="bottom"></div>' +
  • Error Line 1626, Column 31: ID "shellContent" already defined
                        <area id="shellContent" shape="rect" coords="73,19,562,373"…

    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 1617, Column 31: ID "shellContent" first defined here
                        <area id="shellContent" shape="rect" coords="73,19,562,373"…
  • Warning Line 1643, Column 111: character "&" is the first character of a delimiter but occurred as data
    …howInfoPopup('art', event);" alt="Art & Colors" class="clickable" href="javasc…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1666, Column 113: character "&" is the first character of a delimiter but occurred as data
    …howInfoPopup('art', event);" alt="Art & Colors" class="clickable" href="javasc…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 1682, Column 160: character "&" is the first character of a delimiter but occurred as data
    …ry Board</a> | <a href='/tandc'>Terms & Conditions</a> | <a href='/privacy'>Pr…

    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 1683, Column 309: required attribute "alt" not specified
    …abcmouse.com/misc/info_faq_icon.png" /></a></span> <span style="font-weight: b…

    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 1688, Column 19: ID "closeIcon" already defined
            	<div id="closeIcon" onclick="closeFacebookPopup();"></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 1032, Column 17: ID "closeIcon" first defined here
    						'<div id="closeIcon" onclick="closeSurveyErrorMessage();"></div>' +
  • Error Line 1693, Column 19: ID "closeIcon" already defined
            	<div id="closeIcon" onclick="closeAffiliatesPopup();"></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 1032, Column 17: ID "closeIcon" first defined here
    						'<div id="closeIcon" onclick="closeSurveyErrorMessage();"></div>' +
  • Error Line 1720, Column 129: required attribute "alt" not specified
    …mepage/cookie.gif" onclick="im_cookie_onclick(); this.style.display = 'none'"/>

    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 1729, Column 126: required attribute "alt" not specified
    …e?ad_id=27993;evt=20576;cat1=27281;cat2=27282" width="1" height="1" border="0">

    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 1729, Column 127: end tag for "img" omitted, but OMITTAG NO was specified
    …e?ad_id=27993;evt=20576;cat1=27281;cat2=27282" width="1" height="1" border="0">

    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 1729, Column 7: start tag was here
          <img src="http://media.fastclick.net/w/tre?ad_id=27993;evt=20576;cat1=272…
  • Error Line 1730, Column 129: required attribute "type" not specified
    …-6494a8641155d785fd7172d2a9663cd4fd473d85d6be8ba15d6bc12effe27cf2.js"></script>

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

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

  • Error Line 1732, Column 7: end tag for "body" omitted, but OMITTAG NO was specified
    </html>

    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 1317, Column 2: start tag was here
    	<script type="text/javascript">

Visitor Analysis

Daily Visitor
  • 16.333 visits

In Page Analysis