i-tna.org

iTNA - Irc Total Non-Stop Action is an online IRC Wrestling Federation. /server irc.i-TNA.org -j #iTNA Hope to see you soon! ...
Last updated from 19-12-2014 12:57:28  Update data

Overview Info

  • Domain Name
    i-tna.org
  • Favicon
  • Alexa Rank
    #0
  • Google Page Rank
    0
  • Ip Address
    204.45.203.218
  • Page Size
    43.9 KB
  • Images
    61 GIF, 0 JPG, 10 PNG
Heading
H1H2H3H4H5H6
0 0 0 0 0 0

Website Meta Analysis

  • Title
    Irc Total Non-Stop Action - News
  • Meta Keyword
    ITNA,Wrestling,Irc-Wrestling,I-Wrestling,WWE,XXX,Porn,BDSM,Milf,TNA,ROH,GFX WRESTLING,E-FED,warez,mp3,free shell,free mp3,free porn,free free free,play wrestling,play rpg wrestling,play games,IRC,IRC RPG,IRC WRESTLING RPG,e-fed rpg,federation wars,wrestling federations,irc wrestling federations
  • Meta Description
    iTNA - Irc Total Non-Stop Action is an online IRC Wrestling Federation. /server irc.i-TNA.org -j #iTNA Hope to see you soon!
Advertisement

Technical Analysis

  • Webserver
    Apache/2.2.16 (Debian)
  • Ip Address
    204.45.203.218
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Fri, 19 Dec 2014 00:57:25 GMT
  • server: Apache/2.2.16 (Debian)
  • x-powered-by: PHP/5.3.29-1~dotdeb.0
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 9770
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

No data whois for i-tna.org

IP 204.45.203.218 Analysis

  • Country Name
    United States
  • City
    Colorado
  • Latitude
    39.7442
  • Longitude
    -105.1049
  • IP Address Country Region City ISP
    204.45.203.218 United States Colorado Denver Fdcservers.net
      Continent Latitude Longitude Time Zone
      North America 39.7442 -105.1049 MST

Site Same Ip

Traffic Analysis

Magestic Backlinks


Daily Ranks

Rank Trend

Visitor Trend

Bounce Trend

HTML Analysis

HTML validation

  • 96 Errors
  • 65 Warnings

Ratio Text/Html

  • 0.34936489222076395

Message Error

  • Error Line 15, 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 31, Column 114: end tag for "img" omitted, but OMITTAG NO was specified
    …er'><img src='themes/Paradox/images/banneritna2014.png' alt='' border='0'></td>

    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 31, Column 40: start tag was here
    …td align='center' class='full-header'><img src='themes/Paradox/images/bannerit…
  • Error Line 86, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><!-- Start iTNA -->

    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 86, Column 1: start tag was here
    <br><!-- Start iTNA -->
  • Error Line 87, Column 199: end tag for "img" omitted, but OMITTAG NO was specified
    …TNA.gif" alt="IRC TOTAL-NON STOP ACTION" border="0" width="88" height="31"></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 87, Column 109: start tag was here
    … Irc-Wrestling Wrestling WWE TNA ROH"><img src="/iTNA.gif" alt="IRC TOTAL-NON …
  • Error Line 90, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 90, Column 1: start tag was here
    <br>
  • Error Line 93, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><!-- Start iNXT -->

    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 93, Column 1: start tag was here
    <br><!-- Start iNXT -->
  • Error Line 94, Column 202: end tag for "img" omitted, but OMITTAG NO was specified
    …alt="iNXT Official iTNA Training Center" border="0" width="88" height="31"></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 94, Column 92: start tag was here
    …="iNXT Official iTNA Training Center"><img src="/images/iNXTLogo.png" alt="iNX…
  • Error Line 97, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 97, Column 1: start tag was here
    <br>
  • Error Line 100, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><!-- mIRC Banner - Script Begin -->

    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 100, Column 1: start tag was here
    <br><!-- mIRC Banner - Script Begin -->
  • Error Line 101, Column 155: end tag for "img" omitted, but OMITTAG NO was specified
    …m/images/mircnet.gif" width="88" height="31" border="0" alt="www.mIRC.com"></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 101, Column 47: start tag was here
    …"http://www.mirc.com" target="_blank"><img src="http://www.hawkee.com/images/m…
  • Error Line 104, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 104, Column 1: start tag was here
    <br>
  • Error Line 105, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 105, Column 1: start tag was here
    <br>
  • Error Line 113, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 113, Column 1: start tag was here
    <br>
  • Error Line 117, Column 13: end tag for "center" omitted, but OMITTAG NO was specified
            </td>

    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 99, Column 1: start tag was here
    <center>
  • Error Line 117, Column 13: end tag for "center" omitted, but OMITTAG NO was specified
            </td>

    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 92, Column 1: start tag was here
    <center>
  • Error Line 117, Column 13: end tag for "center" omitted, but OMITTAG NO was specified
            </td>

    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 85, Column 1: start tag was here
    <center>
  • Error Line 137, Column 156: required attribute "alt" not specified
    …img src='https://g.twimg.com/Twitter_logo_blue.png' width='70' height='70'></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 137, Column 160: end tag for "img" omitted, but OMITTAG NO was specified
    …img src='https://g.twimg.com/Twitter_logo_blue.png' width='70' height='70'></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 137, Column 81: start tag was here
    …ref='http://twitter.com/#!/iTNABrand'><img src='https://g.twimg.com/Twitter_lo…
  • Error Line 138, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><a href='https://www.facebook.com/iTNABrand'><img src='http://jonbennal…

    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 138, Column 1: start tag was here
    <br><br><a href='https://www.facebook.com/iTNABrand'><img src='http://jonbennal…
  • Error Line 138, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><a href='https://www.facebook.com/iTNABrand'><img src='http://jonbennal…

    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 138, Column 5: start tag was here
    <br><br><a href='https://www.facebook.com/iTNABrand'><img src='http://jonbennal…
  • Error Line 138, Column 167: required attribute "alt" not specified
    …-content/uploads/2012/08/Facebook-logo-ICON-02.png' width='70' height='70'></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 138, Column 171: end tag for "img" omitted, but OMITTAG NO was specified
    …-content/uploads/2012/08/Facebook-logo-ICON-02.png' width='70' height='70'></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 138, Column 54: start tag was here
    …='https://www.facebook.com/iTNABrand'><img src='http://jonbennallick.co.uk/wp-…
  • Error Line 139, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><a href='http://www.youtube.com/user/itna09'><img src='http://www.leean…

    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 139, Column 1: start tag was here
    <br><br><a href='http://www.youtube.com/user/itna09'><img src='http://www.leean…
  • Error Line 139, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><a href='http://www.youtube.com/user/itna09'><img src='http://www.leean…

    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 139, Column 5: start tag was here
    <br><br><a href='http://www.youtube.com/user/itna09'><img src='http://www.leean…
  • Error Line 139, Column 145: required attribute "alt" not specified
    …p://www.leeandthehotrods.co.uk/images/youtube_logo.png' width='70' height='70'>

    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 139, Column 146: end tag for "img" omitted, but OMITTAG NO was specified
    …p://www.leeandthehotrods.co.uk/images/youtube_logo.png' width='70' height='70'>

    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 139, Column 54: start tag was here
    …='http://www.youtube.com/user/itna09'><img src='http://www.leeandthehotrods.co…
  • Error Line 140, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><a href='http://www.ask.fm/iTNABrand'><img src='http://ask.fm/images/do…

    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 140, Column 1: start tag was here
    <br><br><a href='http://www.ask.fm/iTNABrand'><img src='http://ask.fm/images/do…
  • Error Line 140, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><a href='http://www.ask.fm/iTNABrand'><img src='http://ask.fm/images/do…

    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 140, Column 5: start tag was here
    <br><br><a href='http://www.ask.fm/iTNABrand'><img src='http://ask.fm/images/do…
  • Error Line 140, Column 46: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …><a href='http://www.ask.fm/iTNABrand'><img src='http://ask.fm/images/download…

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

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

  • Error Line 140, Column 134: required attribute "alt" not specified
    …'http://ask.fm/images/download/ask_fm-logo-200x200.png' width='70' height='70'>

    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 140, Column 135: end tag for "img" omitted, but OMITTAG NO was specified
    …'http://ask.fm/images/download/ask_fm-logo-200x200.png' width='70' height='70'>

    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 140, Column 47: start tag was here
    …<a href='http://www.ask.fm/iTNABrand'><img src='http://ask.fm/images/download/…
  • Error Line 141, Column 13: end tag for "a" omitted, but OMITTAG NO was specified
    </a></center>

    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 139, Column 9: start tag was here
    <br><br><a href='http://www.youtube.com/user/itna09'><img src='http://www.leean…
  • Warning Line 168, Column 128: character "<" is the first character of a delimiter but occurred as data
    …s/christmas_panel/images/19.png' alt='<strong>19th December</strong>' border='…

    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 168, Column 149: character "<" is the first character of a delimiter but occurred as data
    …as_panel/images/19.png' alt='<strong>19th December</strong>' border='0'/><br />

    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 194, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><center><img src=/images/iTNAlowbanner.png></br><br></br><br><center><b>Wel…

    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 194, Column 1: start tag was here
    <br><center><img src=/images/iTNAlowbanner.png></br><br></br><br><center><b>Wel…
  • Error Line 194, Column 22: an attribute value must be a literal unless it contains only name characters
    <br><center><img src=/images/iTNAlowbanner.png></br><br></br><br><center><b>Wel…

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

  • Error Line 194, Column 47: required attribute "alt" not specified
    …ter><img src=/images/iTNAlowbanner.png></br><br></br><br><center><b>Welcome to…

    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 194, Column 52: end tag for element "br" which is not open
    …img src=/images/iTNAlowbanner.png></br><br></br><br><center><b>Welcome to the …

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 194, Column 52: end tag for "img" omitted, but OMITTAG NO was specified
    …img src=/images/iTNAlowbanner.png></br><br></br><br><center><b>Welcome to the …

    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 194, Column 13: start tag was here
    <br><center><img src=/images/iTNAlowbanner.png></br><br></br><br><center><b>Wel…
  • Error Line 194, Column 66: end tag for "br" omitted, but OMITTAG NO was specified
    …s/iTNAlowbanner.png></br><br></br><br><center><b>Welcome to the official websi…

    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 194, Column 62: start tag was here
    …mages/iTNAlowbanner.png></br><br></br><br><center><b>Welcome to the official w…
  • Error Line 194, Column 129: end tag for "br" omitted, but OMITTAG NO was specified
    … official website of the iTNA!</b><br><center>Quick introduction:<br><center>i…

    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 194, Column 125: start tag was here
    … the official website of the iTNA!</b><br><center>Quick introduction:<br><cent…
  • Error Line 194, Column 160: end tag for "br" omitted, but OMITTAG NO was specified
    …/b><br><center>Quick introduction:<br><center>iTNA - Irc Total Non-Stop Action…

    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 194, Column 156: start tag was here
    …NA!</b><br><center>Quick introduction:<br><center>iTNA - Irc Total Non-Stop Ac…
  • Error Line 194, Column 578: end tag for "br" omitted, but OMITTAG NO was specified
    …and even championship title belts!<br><center>Sounds like fun? I thought so. W…

    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 194, Column 574: start tag was here
    …rds and even championship title belts!<br><center>Sounds like fun? I thought s…
  • Error Line 194, Column 761: end tag for "br" omitted, but OMITTAG NO was specified
    …dicated IRC server @ irc.i-TNA.org<br><center>Once there, join the action in #…

    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 194, Column 757: start tag was here
    …y dedicated IRC server @ irc.i-TNA.org<br><center>Once there, join the action …
  • Error Line 194, Column 818: end tag for "br" omitted, but OMITTAG NO was specified
    … join the action in #iTNA channel.<br><center>It's all pretty self-explanitory…

    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 194, Column 814: start tag was here
    …ere, join the action in #iTNA channel.<br><center>It's all pretty self-explani…
  • Error Line 194, Column 976: end tag for "br" omitted, but OMITTAG NO was specified
    …if you have any further questions.<br><center>All of us at Team iTNA hope to s…

    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 194, Column 972: start tag was here
    … or if you have any further questions.<br><center>All of us at Team iTNA hope …
  • Error Line 194, Column 1064: there is no attribute "HREF"
    …to see YOU in our locker room soon!<br></br><A HREF=http://www.SiteUptime.com/>

    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 194, Column 1064: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …to see YOU in our locker room soon!<br></br><A HREF=http://www.SiteUptime.com/>
  • Error Line 194, Column 1070: NET-enabling start-tag not immediately followed by null end-tag
    …to see YOU in our locker room soon!<br></br><A HREF=http://www.SiteUptime.com/>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 194, Column 1070: element "A" undefined
    …to see YOU in our locker room soon!<br></br><A HREF=http://www.SiteUptime.com/>

    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 195, Column 10: there is no attribute "SRC"
    <IMG SRC=http://www.siteuptime.com/images/sut-88x31-2.gif BORDER=0 WIDTH=88 HEI…

    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 195, Column 10: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IMG SRC=http://www.siteuptime.com/images/sut-88x31-2.gif BORDER=0 WIDTH=88 HEI…
  • Error Line 195, Column 16: NET-enabling start-tag not immediately followed by null end-tag
    <IMG SRC=http://www.siteuptime.com/images/sut-88x31-2.gif BORDER=0 WIDTH=88 HEI…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 195, Column 16: element "IMG" undefined
    <IMG SRC=http://www.siteuptime.com/images/sut-88x31-2.gif BORDER=0 WIDTH=88 HEI…

    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 196, Column 4: end tag for element "A" which is not open
    </A>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 207, Column 20: character "<" is the first character of a delimiter but occurred as data
    for( var i = 0 ; i <= 100 ; i++ )

    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 215, Column 37: character "&" is the first character of a delimiter but occurred as data
    } else if( document.documentElement && document.documentElement.scrollTop ) {

    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 215, Column 38: character "&" is the first character of a delimiter but occurred as data
    } else if( document.documentElement && document.documentElement.scrollTop ) {

    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 227, Column 37: character "&" is the first character of a delimiter but occurred as data
    } else if( document.documentElement && document.documentElement.clientHeight ) {

    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 227, Column 38: character "&" is the first character of a delimiter but occurred as data
    } else if( document.documentElement && document.documentElement.clientHeight ) {

    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 244, Column 20: character "<" is the first character of a delimiter but occurred as data
    for( var i = 0 ; i <= 100 ; i++ ) {

    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 267, Column 29: there is no attribute "name"
    <div id='styled_popup' name='styled_popup' style='width: 600px; height: 730px; …

    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 271, Column 134: required attribute "alt" not specified
    …g src='infusions/welcome_guest_panel/images/flower.gif ' border='0'></b></span>

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

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

  • Error Line 271, Column 138: end tag for "img" omitted, but OMITTAG NO was specified
    …g src='infusions/welcome_guest_panel/images/flower.gif ' border='0'></b></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 271, Column 64: start tag was here
    …e;'><b>Welcome guest&nbsp;&nbsp;&nbsp;<img src='infusions/welcome_guest_panel/…
  • Error Line 274, Column 110: required attribute "alt" not specified
    …p();'><img src='infusions/welcome_guest_panel/images/close.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 274, Column 114: end tag for "img" omitted, but OMITTAG NO was specified
    …p();'><img src='infusions/welcome_guest_panel/images/close.png' border='0'></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 274, Column 42: start tag was here
    …a href='javascript:fadeOutMyPopup();'><img src='infusions/welcome_guest_panel/…
  • Error Line 374, Column 5: end tag for "center" omitted, but OMITTAG NO was specified
    </td><td class='side-border-right' valign='top'><table width='100%' cellpadding…

    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 194, Column 976: start tag was here
    …if you have any further questions.<br><center>All of us at Team iTNA hope to s…
  • Error Line 374, Column 5: end tag for "center" omitted, but OMITTAG NO was specified
    </td><td class='side-border-right' valign='top'><table width='100%' cellpadding…

    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 194, Column 818: start tag was here
    … join the action in #iTNA channel.<br><center>It's all pretty self-explanitory…
  • Error Line 374, Column 5: end tag for "center" omitted, but OMITTAG NO was specified
    </td><td class='side-border-right' valign='top'><table width='100%' cellpadding…

    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 194, Column 761: start tag was here
    …dicated IRC server @ irc.i-TNA.org<br><center>Once there, join the action in #…
  • Error Line 374, Column 5: end tag for "center" omitted, but OMITTAG NO was specified
    </td><td class='side-border-right' valign='top'><table width='100%' cellpadding…

    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 194, Column 578: start tag was here
    …and even championship title belts!<br><center>Sounds like fun? I thought so. W…
  • Error Line 374, Column 5: end tag for "center" omitted, but OMITTAG NO was specified
    </td><td class='side-border-right' valign='top'><table width='100%' cellpadding…

    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 194, Column 160: start tag was here
    …/b><br><center>Quick introduction:<br><center>iTNA - Irc Total Non-Stop Action…
  • Error Line 374, Column 5: end tag for "center" omitted, but OMITTAG NO was specified
    </td><td class='side-border-right' valign='top'><table width='100%' cellpadding…

    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 194, Column 129: start tag was here
    … official website of the iTNA!</b><br><center>Quick introduction:<br><center>i…
  • Error Line 374, Column 5: end tag for "center" omitted, but OMITTAG NO was specified
    </td><td class='side-border-right' valign='top'><table width='100%' cellpadding…

    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 194, Column 66: start tag was here
    …s/iTNAlowbanner.png></br><br></br><br><center><b>Welcome to the official websi…
  • Error Line 374, Column 5: end tag for "center" omitted, but OMITTAG NO was specified
    </td><td class='side-border-right' valign='top'><table width='100%' cellpadding…

    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 194, Column 5: start tag was here
    <br><center><img src=/images/iTNAlowbanner.png></br><br></br><br><center><b>Wel…
  • Error Line 410, Column 30: required attribute "type" not specified
    <script language="javascript">

    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 452, Column 41: character ";" not allowed in attribute specification list
          for (var i=0; i<this.flakes.length; i++) {
  • Error Line 452, Column 41: element "this.flakes.length" undefined
          for (var i=0; i<this.flakes.length; i++) {

    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).
  • Warning Line 477, Column 22: character "&" is the first character of a delimiter but occurred as data
        if (!flakeBottom && s.flakes) {

    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 477, Column 23: character "&" is the first character of a delimiter but occurred as data
        if (!flakeBottom && s.flakes) {

    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 478, Column 38: character ";" not allowed in attribute specification list
          for (var i=0; i<s.flakes.length; i++) {
  • Error Line 478, Column 38: element "s.flakes.length" undefined
          for (var i=0; i<s.flakes.length; i++) {

    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 494, Column 38: character ";" not allowed in attribute specification list
          for (var i=0; i<s.timers.length; i++) {
  • Error Line 494, Column 38: element "s.timers.length" undefined
          for (var i=0; i<s.timers.length; i++) {

    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 511, Column 39: character ";" not allowed in attribute specification list
        for (var i=0; i<this.flakes.length; i++) {
  • Error Line 511, Column 39: element "this.flakes.length" undefined
        for (var i=0; i<this.flakes.length; i++) {

    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).
  • Warning Line 536, Column 60: character "&" is the first character of a delimiter but occurred as data
    …his.o.src = imagePath+this.type+(pngHandler.supported && usePNG?'.png':'.gif');

    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 536, Column 61: character "&" is the first character of a delimiter but occurred as data
    …his.o.src = imagePath+this.type+(pngHandler.supported && usePNG?'.png':'.gif');

    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 538, Column 30: character "&" is the first character of a delimiter but occurred as data
        if (pngHandler.supported && usePNG) pngHandler.transform(this.o);

    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 538, Column 31: character "&" is the first character of a delimiter but occurred as data
        if (pngHandler.supported && usePNG) pngHandler.transform(this.o);

    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 551, Column 22: character "&" is the first character of a delimiter but occurred as data
          if (this.vX>=0 && this.vX<0.2) {

    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 551, Column 23: character "&" is the first character of a delimiter but occurred as data
          if (this.vX>=0 && this.vX<0.2) {

    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 551, Column 32: character "<" is the first character of a delimiter but occurred as data
          if (this.vX>=0 && this.vX<0.2) {

    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 553, Column 25: character "<" is the first character of a delimiter but occurred as data
          } else if (this.vX<0 && this.vX>-0.2) {

    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 553, Column 28: character "&" is the first character of a delimiter but occurred as data
          } else if (this.vX<0 && this.vX>-0.2) {

    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 553, Column 29: character "&" is the first character of a delimiter but occurred as data
          } else if (this.vX<0 && this.vX>-0.2) {

    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 556, Column 22: character "&" is the first character of a delimiter but occurred as data
          if (this.vY>=0 && this.vY<0.2) {

    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 556, Column 23: character "&" is the first character of a delimiter but occurred as data
          if (this.vY>=0 && this.vY<0.2) {

    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 556, Column 32: character "<" is the first character of a delimiter but occurred as data
          if (this.vY>=0 && this.vY<0.2) {

    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 566, Column 19: character "&" is the first character of a delimiter but occurred as data
          if (this.vX && screenX-this.x<flakeWidth+this.vX) { // X-axis scroll check

    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 566, Column 20: character "&" is the first character of a delimiter but occurred as data
          if (this.vX && screenX-this.x<flakeWidth+this.vX) { // X-axis scroll check

    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 566, Column 47: character "+" not allowed in attribute specification list
          if (this.vX && screenX-this.x<flakeWidth+this.vX) { // X-axis scroll check
  • Error Line 566, Column 47: element "flakeWidth" undefined
          if (this.vX && screenX-this.x<flakeWidth+this.vX) { // X-axis scroll check

    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).
  • Warning Line 568, Column 25: character "<" is the first character of a delimiter but occurred as data
          } else if (this.vX<0 && this.x<0-flakeWidth) {

    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 568, Column 28: character "&" is the first character of a delimiter but occurred as data
          } else if (this.vX<0 && this.x<0-flakeWidth) {

    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 568, Column 29: character "&" is the first character of a delimiter but occurred as data
          } else if (this.vX<0 && this.x<0-flakeWidth) {

    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 568, Column 37: character "<" is the first character of a delimiter but occurred as data
          } else if (this.vX<0 && this.x<0-flakeWidth) {

    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 572, Column 28: character ")" not allowed in attribute specification list
          if (yDiff<flakeHeight) {
  • Error Line 572, Column 28: element "flakeHeight" undefined
          if (yDiff<flakeHeight) {

    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).
  • Warning Line 576, Column 26: character "<" is the first character of a delimiter but occurred as data
              for (var i=0; i<2; i++) {

    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 625, Column 21: character "&" is the first character of a delimiter but occurred as data
        if (snowCollect && !waiting) { // !active && !waiting

    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 625, Column 22: character "&" is the first character of a delimiter but occurred as data
        if (snowCollect && !waiting) { // !active && !waiting

    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 625, Column 47: character "&" is the first character of a delimiter but occurred as data
        if (snowCollect && !waiting) { // !active && !waiting

    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 625, Column 48: character "&" is the first character of a delimiter but occurred as data
        if (snowCollect && !waiting) { // !active && !waiting

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 629, Column 31: character ")" not allowed in attribute specification list
        if (active<flakesMaxActive) {
  • Error Line 629, Column 31: element "flakesMaxActive" undefined
        if (active<flakesMaxActive) {

    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).
  • Warning Line 631, Column 26: character "&" is the first character of a delimiter but occurred as data
            if (!snowCollect && active == 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 631, Column 27: character "&" is the first character of a delimiter but occurred as data
            if (!snowCollect && active == 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.
  • Error Line 642, Column 26: character ";" not allowed in attribute specification list
        for (var i=0; i<limit; i++) {
  • Error Line 642, Column 26: element "limit" undefined
        for (var i=0; i<limit; i++) {

    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).
  • Warning Line 654, Column 20: character "<" is the first character of a delimiter but occurred as data
        for (var i=0; i<8192; i++) {

    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 669, Column 15: character "&" is the first character of a delimiter but occurred as data
      if (screenX && screenY && !this.disabled) {

    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 669, Column 16: character "&" is the first character of a delimiter but occurred as data
      if (screenX && screenY && !this.disabled) {

    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 669, Column 26: character "&" is the first character of a delimiter but occurred as data
      if (screenX && screenY && !this.disabled) {

    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 669, Column 27: character "&" is the first character of a delimiter but occurred as data
      if (screenX && screenY && !this.disabled) {

    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 696, Column 56: character "&" is the first character of a delimiter but occurred as data
      return ((eventType.toLowerCase().indexOf('load')>=0) && document.body);

    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 696, Column 57: character "&" is the first character of a delimiter but occurred as data
      return ((eventType.toLowerCase().indexOf('load')>=0) && document.body);

    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 792, Column 28: character "&" is the first character of a delimiter but occurred as data
      this.isIEMac = (this.isIE&&!this.isWin);

    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 792, Column 29: character "&" is the first character of a delimiter but occurred as data
      this.isIEMac = (this.isIE&&!this.isWin);

    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 793, Column 28: character "&" is the first character of a delimiter but occurred as data
      this.isIEWin = (this.isIE&&this.isWin);

    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 793, Column 30: cannot generate system identifier for general entity "this.isWin"
      this.isIEWin = (this.isIE&&this.isWin);

    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 793, Column 30: general entity "this.isWin" not defined and no default entity
      this.isIEWin = (this.isIE&&this.isWin);

    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 793, Column 40: reference not terminated by REFC delimiter
      this.isIEWin = (this.isIE&&this.isWin);

    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 793, Column 40: reference to entity "this.isWin" for which no system identifier could be generated
      this.isIEWin = (this.isIE&&this.isWin);

    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 793, Column 29: entity was defined here
      this.isIEWin = (this.isIE&&this.isWin);
  • Warning Line 839, Column 29: character "&" is the first character of a delimiter but occurred as data
        if (o.nodeName != 'IMG' && !(this.isIE && this.isMac)) { // ie:mac PNG supp…

    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 839, Column 30: character "&" is the first character of a delimiter but occurred as data
        if (o.nodeName != 'IMG' && !(this.isIE && this.isMac)) { // ie:mac PNG supp…

    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 839, Column 44: character "&" is the first character of a delimiter but occurred as data
    …f (o.nodeName != 'IMG' && !(this.isIE && this.isMac)) { // ie:mac PNG support …

    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 839, Column 45: character "&" is the first character of a delimiter but occurred as data
    … (o.nodeName != 'IMG' && !(this.isIE && this.isMac)) { // ie:mac PNG support b…

    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 863, Column 19: character "&" is the first character of a delimiter but occurred as data
        if (this.isIE && this.isWin && this.ver >= 5.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 863, Column 20: character "&" is the first character of a delimiter but occurred as data
        if (this.isIE && this.isWin && this.ver >= 5.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 863, Column 33: character "&" is the first character of a delimiter but occurred as data
        if (this.isIE && this.isWin && this.ver >= 5.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 863, Column 34: character "&" is the first character of a delimiter but occurred as data
        if (this.isIE && this.isWin && this.ver >= 5.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 866, Column 27: character "&" is the first character of a delimiter but occurred as data
        } else if (!this.isIE && this.ver < 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 866, Column 28: character "&" is the first character of a delimiter but occurred as data
        } else if (!this.isIE && this.ver < 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 866, Column 39: character "<" is the first character of a delimiter but occurred as data
        } else if (!this.isIE && this.ver < 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 871, Column 27: character "&" is the first character of a delimiter but occurred as data
        } else if (!this.isIE && this.ver >= 5 || (this.isIE && this.isMac && this.…

    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 871, Column 28: character "&" is the first character of a delimiter but occurred as data
        } else if (!this.isIE && this.ver >= 5 || (this.isIE && this.isMac && this.…

    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 871, Column 58: character "&" is the first character of a delimiter but occurred as data
    …s.isIE && this.ver >= 5 || (this.isIE && this.isMac && this.ver >= 5)) { // ve…

    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 871, Column 59: character "&" is the first character of a delimiter but occurred as data
    ….isIE && this.ver >= 5 || (this.isIE && this.isMac && this.ver >= 5)) { // ver…

    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 871, Column 72: character "&" is the first character of a delimiter but occurred as data
    ….ver >= 5 || (this.isIE && this.isMac && this.ver >= 5)) { // version 5+ brows…

    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 871, Column 73: character "&" is the first character of a delimiter but occurred as data
    …ver >= 5 || (this.isIE && this.isMac && this.ver >= 5)) { // version 5+ browse…

    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 891, Column 31: character ";" not allowed in attribute specification list
      for (var i=0; i<nodes.length; i++) {
  • Error Line 891, Column 31: element "nodes.length" undefined
      for (var i=0; i<nodes.length; i++) {

    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 907, Column 9: end tag for "nodes.length" omitted, but OMITTAG NO was specified
    </script></td>

    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 891, Column 18: start tag was here
      for (var i=0; i<nodes.length; i++) {
  • Error Line 907, Column 9: end tag for "limit" omitted, but OMITTAG NO was specified
    </script></td>

    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 642, Column 20: start tag was here
        for (var i=0; i<limit; i++) {
  • Error Line 907, Column 9: end tag for "flakesMaxActive" omitted, but OMITTAG NO was specified
    </script></td>

    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 629, Column 15: start tag was here
        if (active<flakesMaxActive) {
  • Error Line 907, Column 9: end tag for "flakeHeight" omitted, but OMITTAG NO was specified
    </script></td>

    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 572, Column 16: start tag was here
          if (yDiff<flakeHeight) {
  • Error Line 907, Column 9: end tag for "flakeWidth" omitted, but OMITTAG NO was specified
    </script></td>

    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 566, Column 36: start tag was here
          if (this.vX && screenX-this.x<flakeWidth+this.vX) { // X-axis scroll check
  • Error Line 907, Column 9: end tag for "this.flakes.length" omitted, but OMITTAG NO was specified
    </script></td>

    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 511, Column 20: start tag was here
        for (var i=0; i<this.flakes.length; i++) {
  • Error Line 907, Column 9: end tag for "s.timers.length" omitted, but OMITTAG NO was specified
    </script></td>

    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 494, Column 22: start tag was here
          for (var i=0; i<s.timers.length; i++) {
  • Error Line 907, Column 9: end tag for "s.flakes.length" omitted, but OMITTAG NO was specified
    </script></td>

    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 478, Column 22: start tag was here
          for (var i=0; i<s.flakes.length; i++) {
  • Error Line 907, Column 9: end tag for "this.flakes.length" omitted, but OMITTAG NO was specified
    </script></td>

    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 452, Column 22: start tag was here
          for (var i=0; i<this.flakes.length; i++) {

Visitor Analysis

In Page Analysis