JSHint is a tool that helps to detect errors and potential problems in Javascript code. Wielded by this app, you can consider it a whole-website code checker. It is based on Douglas Crockford’s JSLint. At the moment, this test only checks standalone files with the .js extension and are of the MIME types:

  • text/javascript
  • application/x-javascript
  • application/javascript

Inline script blocks are not checked

Error: Element title not allowed as child of element head in this context.

What It Looks Like

  • Error: Element title not allowed as child of element head in this context. (Suppressing further errors from this subtree.)

    From line 11, column 1; to line 11, column 7


    Contexts in which element title may be used:
    In a head element containing no other title elements.
    Content model for element head:
    If the document is an iframe srcdoc document or if title information is available from a higher-level protocol: Zero or more elements of metadata content.
    Otherwise: One or more elements of metadata content, of which exactly one is a title element.

What The Spec Says

Here is a nice and easy breakdown of TITLE

How To Fix

This error message is almost longer than the spec! Just make sure you have only one <title> tag and that it appears inside the <head>


Check Page Rank All Pages In Site

This test looks up a representation of the Google PageRank™ of each given document. Possible values are from 0-9 (zero through nine) and blank, which means the document does not have a PageRank™. Blank may be considered below 0 (zero) in importance.

The PageRank™ values returned from our app are only an approximation of the actual PageRank™ maintained internally by Google. The same PageRank™ approximation is publicly and freely available in many other places on the internet, although our access to it may be severed at any time. Not only is the PageRank™ given here an approximation, it may lag some months behind the actual and current value maintained internally by Google.

PageRank™ is a registered trademark of Google, Inc. held by Stanford University, CA.

New Cookie Module

Cookie schmookie right? It’s just so pat. Nothing could be more boring, that it, until it breaks. Until then we had been successfully using the cookie module hosted on the code.google website.

We were seeing a very obscure problem. With Firefox, in conjunction with the jQuery bindings, while using websockets to transfer data. The FF implemention of WS was getting killed each time a new validation job was submitted.

Looking for a replacement, one that didn’t rely on jQuery, I came across the cookie module written and so-generously shared by Scott Hamper. The code is tight and modern enough. It supports setter injection for testing, AMD, and can be used in node.js.

HTML Validator

This tool is running an instance of the HTML Validator.nu developed by Henri Sivonen, adopted by the WHATWG and eventually implemented by W3. The validator shows errors in HTML standard compliance. Warnings and Information messages are suppressed.

Reports Are Fixed

The reports are back online. The problem was that under development, they didn’t bear up under the additional website checks that were added. That problem has been fixed and we have a new, flexible report generator that will render the reports perfectly no matter what you are checking.

2 Flavors Available: PDF, HTML


Our link checker reports on missing web pages that are referred to by anchor tags. Broken links are shown in yellow for each document they appear in. Non-standard responses for pages within a website (error code 400 and above) are shown within the summary results table for each website check performed.


Our spell checker shows you all typos and/or misspellings found in each page of your website. Spelling failures are shown both in the summary view and detail view. In the detail view, you can add discovered words to your personal dictionary and the checker will not flag them again.

We currently have dictionaries to check:

  • British English (en_GB)
  • Canadian English (en_CA)
  • US English (en_US)
  • Español (es)
  • French (fr)
  • Swiss French (fr_CH)

Our text parser extracts words from the HTML on a unicode basis. So the spellchecker works best when the charset of the documents is “UTF-8″ as specified by the http headers