We have extended the benefits of the ease of use of the Snapshot feature to all audit reports.

This means that when you are looking at the problems on an individual page you will have the option of viewing the results in one of the Snapshot views. Either

• Page view
• Source view 

This means that the ease of use benefits of the Snapshot interface are available to all users looking at their audit reports.  Whether scheduled audits or ad-hoc audits.

Access to the Snapshot views is on the Page diagnostics page.  So if you click on, say, Code quality, chose Bad attribute errors this gives you a list of your web pages where the Bad attribute error occurs and clicking on the URL of one of these pages takes you to the Page diagnostics page.  This shows you ALL of the errors from ALL of the Category of tests we run as part of an audit.

The links are at the top of the left hand column.  Here's a video to talk you through how to get to the Snapshot views and what they show.

Anchor Points or Fragment Identifiers are used extensively to take users to particular parts of a Webpage.  A classic example of this being a site's FAQs page where you'd have a list of clickable FAQs at the top of the page that, when clicked, take you to the full text of the question and the answer which are either lower down the same page or perhaps are part of another page.

The problem comes when these are coded incorrectly or the page changes and the links no longer reflect what's actually on the target page.

Examples:

1. A clickable FAQ entry points to a Fragment Identifier called Q10 which should be located further down the page but Q10 doesn't exist. 
2. A clickable FAQ entry points to a Fragment Identifier called Q10 but there are TWO (or more) Q10s

These errors will be reported under Code Quality under the Unknownid for the first example and under the Bad value item for the second.  We added them to the Code Quality category as these types of error won't cause a failure in the same way as, say, a broken link would (though there are similarities) they just won't work as you intended them to.  For instance if you click on one of the clickable FAQs in the example and no Q10 Identifier exists the Webpage would remain in exactly the same place.  Or in the case of duplicate Q10 Identifiers the browser will take you to the FIRST instance of Q10 which may or may not be correct.

Fragment Identifiers may also be used by a site's Style Sheets (CSS) or by JavaScript on the site.  Again missing or duplicated Identifiers will cause unpredictable and, therefore, undesirable results.

Some sites will see these new checks impact their Code Quality score when they've made limited unrelated changes.  It's important that we extend the checks we do to identify issues on your websites.  The side effect of this could be that we find you more problems to fix but all of the issues we raise could be impacting the visitors to your site. 

During the training sessions I've been running for the past few months the are bits of the Sitemorse service that people are not taking advantage of.  Page Credits is one of them and I've already posted a couple of blogs on the subject (http://blog.sitemorse.com/2008/06/page-credits.html   & http://blog.sitemorse.com/2008/06/subscription-vs-page-credits.html). 

The other is the Inventory Page.

This page is aimed at providing a summary of all the "items" we found whilst performing the tests.

The overall benefit of the page is that you can get, at a glance, a view of all the "technology" that makes up your site and verify that it's appropriate.

File Types

We show you all the different file types that we found, how many there are of each type and the average and maximum sizes.

This allows you to quickly identify the presence of any banned file types, such as Word or Excel, that got on the site by mistake.
It also allows you to identify any oversize files such as a 30Mb PDF or a 850Kb .gif or .jpg which need optimising.  Clicking on the file type brings up a list of the 10 largest items.

Browser technology

We tell you if use JavaScripts and list the pages they are on
We tell you if you use Cookies and, if so, whether they are session or persistent  and list the pages they are on.
We tell you if you use Java and list the pages it's on
We tell you if you have Flash and tell you on which pages

That way you can police the correct use of the technology that has been sanctioned for use on the site.

Email and off-site links

We tell you how many email addresses were linked from the site and clicking the link lists them and identifies any that are in error.
We tell you how many off-site addresses were linked from the site and clicking on the link list them and identifies any that are in error.
 

So you can quickly see which of them needs to be corrected and which need to be removed.

Webserver Ident

We identify the type of Webserver served the content and the URL of the first page served.

This shows you the different types of Webserver technology involved in serving up your web pages  and how many came from each.  This can be useful where you have feeds to your website from a number of sources or perhaps you use Edge Services from someone like Akamai.

Information is king.  So take a quick look at it each time you get a new report just to make sure everything is as it should be.

A guide to the Inventory Page is available at http://www.sitemorse.com/d/guides/Inventory_Guide.pdf