File usage test
From SiteRay wiki
| SiteRay Test | |
|---|---|
| First appeared: | Sitescore 1.0 |
| Applies to: | All versions |
| Type: | Individual test |
| Scored: | Always |
What does it do?
Measures the use of files on the website, in particular how large they are (and therefore how long they take to load).
Why is it important?
Usually the biggest factor in how long a webpage takes to load is how large the files are which it uses. Slow pages have been shown to turn visitors away in droves. Conversely, fast pages give visitors a better opinion of your website and encourage them to explore more links.
If a page takes over 8 seconds to display a reasonable portion of content, most people will abandon it entirely. Many users have far lower tolerances than this.
Example results
At the top, you can see a summary of overall performance and a graph of page size distribution:
Further down, you can see a breakdown by file type and a graph of likely loading time:
How is it measured?
Sitescore looks at every file used by every webpage, downloads them and measures their size and type.
The score is based on how long the average webpage will take to load in its entirety, for the targeted bandwidth (an option you can set under Website settings). The ideal loading time - for a perfect score of 10 - is 3 seconds.
An additional, significant penalty is applied to websites with very slow homepages.
Technical explanation
To determine the type of files, Sitescore uses an intelligent combination of the MIME type reported by the server and the file extension. Where these conflict, Sitescore logs a warning in the detailed results.
Example conflicts:
example.css reports a MIME type text/plain = CSS example.txt reports a MIME type text/html = Text example.mpg reports a MIME type audio/mpeg = MPEG audio example.mpg reports a MIME type video/mpeg = MPEG video
The rules for type deduction are frequently updated.
Each connection speed is weighted down for actual download speed, not theoretical maximum. The default modifier is to use 60% of the theoretical maximum speed for estimates.
Common problems
File sizes appear too small for some files
This is particularly common with Flash and video files. Sitescore is reporting the size of the initial file, not the subsequent download which may be initiated by it (for example, the Flash may initiate a pre-loader, which then loads more Flash). There is no way to detect this. Sitescore is effectively recording the time for the Flash to start.
Some file types not found
If you are using an unrecognised file type (something very obscure), Sitescore may not recognise it. Alternatively, the webserver may be incorrectly configured and is not explaining what that file type is clearly enough to Sitescore. Other users may have problems with this file.
How to improve this score
Optimise the website to use smaller files, and less files where possible. Some general advice:
- Optimise image formats. Ensure that the correct file format is being used – generally GIF or PNG for images with solid colour, and JPEGs for photos. Ensure appropriate compression keeps the image sizes in check (e.g. reduce the palette, or use more lossy compression for JPEGs). Avoid error diffusion for GIFs unless absolutely essential, as it massively increases file size – PNGs are usually much better.
- Avoid bloated Javascript. Only include Javascript files that the page actually requires. Most webpages are better served using server-side scripting, which results in much faster pages that are also more likely to be spiderable, accessible and optimised for search engines.
How to use this test effectively
Firstly, always ensure you have set the target Connection speed correctly for your site before using this test. Increasingly, most websites target a broadband audience, but yours may vary.
Use this test as a health check to see whether your pages are loading quickly enough. Wherever possible, take measures to improve the speed of your website to an appropriate level (this depends on what you have set as the target Internet speed of your audience).
Pay particular attention to this test if your homepage is slow. Ironically despite being the page most sensitive to file size (i.e. users are most likely to leave here) it is also often the largest.
Further reading
- Yahoo: Best Practices for Speeding Up Your Web Site
- Response Time: Eight Seconds, Plus or Minus Two
- Jacob Nielsen: The Need for Speed
- Web Page Analyzer - a free speed analysis tool (not provided by Silktide)
