Page Title: Department of Mathematics | University of Hawaiʻi at Mānoa

  • This webpage makes use of the TITLE meta tag - this is good for search engine optimization.

Page Description:

  • This webpage DOES NOT make use of the DESCRIPTION meta tag - this is NOT GOOD for search engine optimization.

Page Keywords:

  • This webpage DOES NOT make use of the KEYWORDS meta tag - whilst search engines nowadays do not put too much emphasis on this meta tag including them in your website does no harm.

Page Text: Our mission within the College of Natural Sciences at the University of Hawaii at Manoa includes: To prepare students to function in a world of rapid scientific and technological change. To prepare students for significant positions in the increasingly technological societies of Hawai‘i, the United States, the Pacific Rim or the nations of the world. To create new knowledge in Mathematics; to apply that knowledge for the betterment of people everywhere. To bring to the people of Hawai‘i a sense of excitement about important mathematical discoveries, both old and new.

  • This webpage has 86 words which is NOT between the recommended minimum of 250 words and the recommended maximum of 2500 words.

Header tags:

  • It appears that you are using header tags - this is a GOOD thing!

Spelling errors:

  • This webpage has 1 words which may be misspelt.

Possibly mis-spelt word: Manoa

Suggestion: Mania
Suggestion: Manna
Suggestion: Manor
Suggestion: Manta
Suggestion: Manga
Suggestion: Norman

Broken links:

  • This webpage has 3 broken links.

Broken image links:

  • This webpage has no broken image links that we can detect - GOOD WORK.

CSS over tables for layout?:

  • It appears that this page uses DIVs for layout this is a GOOD thing!

Last modified date:

  • We were unable to detect what date this page was last modified

Images that are being re-sized:

  • This webpage has no images that are being re-sized by the browser - GOOD WORK.

Images that are being re-sized:

  • This webpage has no images that are missing their width and height - GOOD WORK.

Mobile friendly:

  • After testing this webpage it appears NOT to be mobile friendly - this is NOT a good thing!

Links with no anchor text:

  • This webpage has no links that are missing anchor text - GOOD WORK.

W3C Validation:

  • This webpage has 37 W3C validation errors - this is NOT a good thing. View / Hide errors
  • warning On line 35 column 114, Issue is:The “type” attribute is unnecessary for JavaScript resources.

  • warning On line 36 column 125, Issue is:The “type” attribute is unnecessary for JavaScript resources.

  • warning On line 37 column 126, Issue is:The “type” attribute is unnecessary for JavaScript resources.

  • warning On line 38 column 144, Issue is:The “type” attribute is unnecessary for JavaScript resources.

  • warning On line 46 column 50, Issue is: The “type” attribute for the “style” element is not needed and should be omitted.

  • warning On line 65 column 59, Issue is:The “banner” role is unnecessary for element “header”.

  • warning On line 73 column 95, Issue is:The “navigation” role is unnecessary for element “nav”.

  • On line 205 column 217, Issue is:The “frameborder” attribute on the “iframe” element is obsolete. Use CSS instead.

  • warning On line 210 column 31, Issue is:Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).

  • On line 217 column 217, Issue is:The “frameborder” attribute on the “iframe” element is obsolete. Use CSS instead.

  • warning On line 222 column 31, Issue is:Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).

  • warning On line 238 column 342, Issue is:The “charset” attribute on the “script” element is obsolete.

  • On line 363 column 9, Issue is:No “p” element in scope but a “p” end tag seen.

  • warning On line 433 column 64, Issue is:The “contentinfo” role is unnecessary for element “footer”.

  • warning On line 494 column 32, Issue is:The “type” attribute is unnecessary for JavaScript resources.

  • warning On line 499 column 140, Issue is:The “type” attribute is unnecessary for JavaScript resources.

  • warning On line 500 column 111, Issue is:The “type” attribute is unnecessary for JavaScript resources.

  • warning On line 501 column 125, Issue is:The “type” attribute is unnecessary for JavaScript resources.

  • warning On line 502 column 133, Issue is:The “type” attribute is unnecessary for JavaScript resources.

  • warning On line 503 column 141, Issue is:The “type” attribute is unnecessary for JavaScript resources.

  • warning On line 169 column 26, Issue is:Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).

  • warning On line 157 column 26, Issue is:Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).

  • warning On line 241 column 26, Issue is:Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).

  • warning On line 109 column 26, Issue is:Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).

  • warning On line 477 column 86, Issue is:Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).

  • warning On line 460 column 94, Issue is:Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).

  • warning On line 438 column 78, Issue is:Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).

  • warning On line 449 column 76, Issue is:Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).

  • warning On line 121 column 26, Issue is:Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).

  • warning On line 145 column 26, Issue is:Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).

  • warning On line 197 column 126, Issue is:Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).

  • warning On line 238 column 74, Issue is:Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).

  • warning On line 368 column 93, Issue is:Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).

  • warning On line 133 column 26, Issue is:Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).

  • warning On line 74 column 30, Issue is:Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).

  • warning On line 182 column 54, Issue is:Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).

  • warning On line 386 column 93, Issue is:Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).

Print friendly?:

  • It appears that the webpage does NOT use CSS stylesheets to provide print functionality - this is a BAD thing.

GZIP Compression enabled?:

  • It appears that the serrver does NOT have GZIP Compression enabled - this is a NOT a good thing!