Home Sports Men's Sports Baseball Basketball Cross Country Football Golf Swimming & Diving Track & Field Wrestling Women's Sports Basketball Cross Country Golf Soccer Softball Swimming & Diving Tennis Track & Field Volleyball ...

goashlandeagles.com
  • Domain Name
    goashlandeagles.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #1840834
  • Page Size
    77 KB
  • Ip Address
    67.228.165.35
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 16 JPG, 10 PNG

Website Meta Analysis

  • Title
    Ashland University
  • Meta Keyword
  • Meta Description
    Home Sports Men's Sports Baseball Basketball Cross Country Football Golf Swimming & Diving Track & Field Wrestling Women's Sports Basketball Cross Country Golf Soccer Softball Swimming & Diving Tennis Track & Field Volleyball Atheletic Department ...

Technical Analysis

  • Webserver
    Resin/3.0.18
  • Ip Address
    67.228.165.35
  • Domain Age
    2 Years, 5 Months, 2 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sun, 29 Sep 2013 20:30:52 GMT
  • server: Resin/3.0.18
  • vary: Accept-Encoding
  • content-language: en-US
  • content-encoding: gzip
  • content-type: text/html; charset=UTF-8
  • content-length: 10394
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for goashlandeagles.com

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 382 Errors
  • 2 Warnings
Ratio Text/Html
  • 0.6050305052068139
Message Error
  • Error Line 22, Column 14: there is no attribute "forua"
    	<meta forua="true" http-equiv="Cache-Control" content="must-revalidate" />

    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 32, Column 9: document type does not allow element "strong" here; missing one of "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "pre", "address", "fieldset" start-tag
    	<strong><a href="/landing/index">News</a></strong>

    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 33, Column 2: character data is not allowed here
     | 

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 34, Column 35: document type does not allow element "a" here; missing one of "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "pre", "address", "fieldset" start-tag
    	<a href="/landing/index?c=scores">Scores</a>

    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 35, Column 6: document type does not allow element "br" here; missing one of "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "pre", "address", "fieldset" start-tag
    <br /><br />

    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 35, Column 12: document type does not allow element "br" here; missing one of "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "pre", "address", "fieldset" start-tag
    <br /><br />

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

  • Warning Line 37, Column 60: character "<" is the first character of a delimiter but occurred as data
    <p class="goBack-link"><a href="javascript:history.go(-1)"><<< Back</a></p>

    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 37, Column 61: character "<" is the first character of a delimiter but occurred as data
    <p class="goBack-link"><a href="javascript:history.go(-1)"><<< Back</a></p>

    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 37, Column 62: character "<" is the first character of a delimiter but occurred as data
    <p class="goBack-link"><a href="javascript:history.go(-1)"><<< Back</a></p>

    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 40, Column 3: document type does not allow element "b" here; missing one of "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
    <b> News</b>

    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 43, Column 33: there is no attribute "cellpadding"
    <table width="100%" cellpadding="0" cellspacing="0" border="0">

    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 43, Column 49: there is no attribute "cellspacing"
    <table width="100%" cellpadding="0" cellspacing="0" border="0">

    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 43, Column 60: there is no attribute "border"
    <table width="100%" cellpadding="0" cellspacing="0" border="0">

    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 47, Column 94: required attribute "alt" not specified
    …photos/0015/DSC1894.JPG?max_width=120"></div>    Feb 27, 2013&nbsp;-&nbsp; The…

    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 47, Column 100: end tag for "img" omitted, but OMITTAG NO was specified
    …/0015/DSC1894.JPG?max_width=120"></div>    Feb 27, 2013&nbsp;-&nbsp; The AU me…

    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 47, Column 25: start tag was here
       <div class="caption"><img src="/sports/mbkb/2012-13/photos/0015/DSC1894.JPG?…
  • Error Line 51, Column 94: required attribute "alt" not specified
    …photos/0015/DSC1974.JPG?max_width=120"></div>    Feb 27, 2013&nbsp;-&nbsp; The…

    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 51, Column 100: end tag for "img" omitted, but OMITTAG NO was specified
    …/0015/DSC1974.JPG?max_width=120"></div>    Feb 27, 2013&nbsp;-&nbsp; The AU wo…

    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 51, Column 25: start tag was here
       <div class="caption"><img src="/sports/wbkb/2012-13/photos/0015/DSC1974.JPG?…
  • Error Line 55, Column 93: required attribute "alt" not specified
    …photos/0007/DSC6832.jpg?max_width=120"></div>    Feb 26, 2013&nbsp;-&nbsp; The…

    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 55, Column 99: end tag for "img" omitted, but OMITTAG NO was specified
    …/0007/DSC6832.jpg?max_width=120"></div>    Feb 26, 2013&nbsp;-&nbsp; The AU ba…

    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 55, Column 25: start tag was here
       <div class="caption"><img src="/sports/bsb/2011-12/photos/0007/DSC6832.jpg?m…
  • Error Line 59, Column 118: required attribute "alt" not specified
    …ffin_-MBB_2-23-13-.jpeg?max_width=120"></div>    Feb 26, 2013&nbsp;-&nbsp; Che…

    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 59, Column 124: end tag for "img" omitted, but OMITTAG NO was specified
    …MBB_2-23-13-.jpeg?max_width=120"></div>    Feb 26, 2013&nbsp;-&nbsp; Check out…

    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 59, Column 25: start tag was here
       <div class="caption"><img src="/sports/mbkb/2012-13/videos/Top_5_Plays_vs_Ti…
  • Error Line 63, Column 95: required attribute "alt" not specified
    …photos/0005/DSC7829.jpg?max_width=120"></div>    Feb 24, 2013&nbsp;-&nbsp; The…

    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 63, Column 101: end tag for "img" omitted, but OMITTAG NO was specified
    …/0005/DSC7829.jpg?max_width=120"></div>    Feb 24, 2013&nbsp;-&nbsp; The AU so…

    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 63, Column 25: start tag was here
       <div class="caption"><img src="/sports/sball/2011-12/photos/0005/DSC7829.jpg…
  • Error Line 67, Column 6: document type does not allow element "br" here; missing one of "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "pre", "address", "fieldset" start-tag
    <br />

    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 68, Column 1: character data is not allowed here
    loaded on March 2 at 2:32:07 AM</p>

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 68, Column 35: end tag for element "p" which is not open
    loaded on March 2 at 2:32:07 AM</p>

    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 72, Column 70: cannot generate system identifier for general entity "m"
    …obile | <a href="/action/browser-mode?u=%2Flanding%2Findex&m=0">Desktop</a></p>

    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 72, Column 70: general entity "m" not defined and no default entity
    …obile | <a href="/action/browser-mode?u=%2Flanding%2Findex&m=0">Desktop</a></p>

    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 72, Column 71: reference not terminated by REFC delimiter
    …obile | <a href="/action/browser-mode?u=%2Flanding%2Findex&m=0">Desktop</a></p>

    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 72, Column 71: reference to external entity in attribute value
    …obile | <a href="/action/browser-mode?u=%2Flanding%2Findex&m=0">Desktop</a></p>

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

  • Error Line 72, Column 71: reference to entity "m" for which no system identifier could be generated
    …obile | <a href="/action/browser-mode?u=%2Flanding%2Findex&m=0">Desktop</a></p>

    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 72, Column 69: entity was defined here
    …obile | <a href="/action/browser-mode?u=%2Flanding%2Findex&m=0">Desktop</a></p>

Visitor Analysis

Daily Visitor
  • 62 visits