Guides
Website Audit Checklist: What a Good Review Checks
A website audit checklist for small business owners: what to measure for speed, search and accessibility, and how to tell a real review from a score sheet.
IO Creative5 min read
A good website audit checklist covers three things, measured on your live site: speed, search visibility and accessibility. Every finding should come with evidence, such as a measurement or an annotated screenshot, and every fix should be sized so you can tell what is quick and what is a project. A score on its own is not an audit.
If you run a small business, you probably want to know three things: is the site fast for customers, can people find it, and can everyone use it. This checklist walks through each, shows what to look for in a report, and gives you a short pass you can do yourself before you pay anyone.
Website audit checklist: speed
Speed is the easiest part to measure and the easiest to get wrong. Google's web.dev guidance names three Core Web Vitals and gives a target for each:
- Loading (Largest Contentful Paint): the main content should appear within 2.5 seconds of the page starting to load.
- Interactivity (Interaction to Next Paint): the page should respond in 200 milliseconds or less.
- Visual stability (Cumulative Layout Shift): the page should not jump around, with a score of 0.1 or less.
web.dev says to judge these at the 75th percentile of page loads, split across mobile and desktop. In plain words: the targets should hold for most of your visitors, on a phone as well as on a desktop.
What to look for in a review:
- Results for a phone and for a desktop, not one number.
- A real first visit with the cache off, because that is what a new customer downloads.
- The heaviest files named. Oversized photos and video are the usual cause.
On our own client work, a first desktop visit to one rebuilt site dropped from 33.1 MB to 4.0 MB, 88% less to download. The cause was media that had never been prepared for the web, and it only showed up when we measured a cold visit. The full story is in our case study, Making a site 88% lighter.
Search: what Google can actually see
Search checks are about whether your pages can be found at all, before anyone talks about ranking. A review should look at:
- Which pages Google has, and which it misses. A page that is not in Google cannot be found there.
- Page titles. Each page needs its own, saying what the page is about. Missing titles are a common quick fix.
- The sitemap. It should list your pages and be known to Google, so new pages are picked up.
- Names and basics. Search for your business name and see which pages come up and what they say.
Ask for this page by page, not as a sample. On one client site we measured, all 43 of its 43 sitemap pages were on Google.
Accessibility: checked against WCAG
Accessibility means the site works for people who use a screen reader, a keyboard instead of a mouse, or who have trouble with small or low-contrast text. The standard reviewers use is the Web Content Accessibility Guidelines (WCAG). The W3C, which publishes it, describes WCAG 2.2 as 13 guidelines organised under four principles: perceivable, operable, understandable and robust. Each guideline has testable success criteria at three levels: A, AA and AAA.
You do not need to read the standard to read a review. You need the review to say which criteria failed, where, and what the fix is. Common failures include a form field with no label, an image with no description, and text that is hard to read against its background.
Evidence: how to tell a real audit from a score sheet
A tool can print a score in seconds. That is a starting point, not a review. A review you can act on has:
- The page and the measurement, so you can check it yourself.
- An annotated screenshot, with the problem outlined on the page.
- A real browser, on a phone and on a desktop, rather than a one-line automated result.
- Plain words, so you can hand it to your own developer without a translator.
If a report lists forty items with no proof, you cannot tell which matter.
Fixes in order, with sizes
The last part of the checklist is the one owners value most: what to do first. A useful report orders fixes by what the problem costs you and marks each as quick, half a day or a project. In the example report on our review page, the list runs: compress the home page photo (quick), add page titles for search (quick), label the booking form (half a day), and move off the site builder (a project).
Sizing matters because most sites have a handful of quick wins that cost little and a couple of big jobs that need a decision. Without sizes, you cannot tell which is which.
A 15-minute check you can do yourself
Before you commission anything, try this.
- Run your home page through PageSpeed Insights, which reports the three Core Web Vitals, and note the phone result first.
- Open your site on your phone on mobile data, not Wi-Fi. Is it quick to show something useful?
- Search for your business name. Does the right page come up, with a sensible title?
- Use the keyboard only. Press Tab through your contact or booking form. Can you reach every field, and can you see where you are?
- Check that every page you care about has its own title.
Write down what you find. It will make the call with a reviewer shorter.
What happens after the review
On our side, you send the address of the site and what worries you about it. We open it like a visitor, in a real browser, on a phone and on a desktop, and write down each finding with its screenshot and measurement. Each fix gets a price, ordered by what the problem costs you. Then you choose: we fix it, or your team does. The report is yours either way, and you can give it to your own developer.
Read how it works on our website review page. If the review shows the site needs rebuilding, see website development, or contact us with the address and your questions.
Sources
- web.dev, "Web Vitals": https://web.dev/articles/vitals
- W3C Web Accessibility Initiative, "WCAG 2 Overview": https://www.w3.org/WAI/standards-guidelines/wcag/
