What a good website audit looks like

A good audit measures one thing at a time with everything else held equal, ranks what it finds by likelihood and impact, and ends with options you can act on without the auditor.

Quick scan

  • Google's documentation says Lighthouse scores vary from run to run and that taking the median of several runs reduces the variance, so a single quoted run is noise.
  • Nearly half the flaws disclosed in 2025 had no fix on the day, so a fully updated plugin can still leave a site exposed.
  • Ask whether every figure says how and when it was measured, whether findings are ranked, whether there is more than one option, and whether it is useful without the auditor.
Read the full article4 minutes
In this article

Most website audits are a sales document with a score on the front. You can tell because the recommendation is always the same, whatever the site: hire the auditor. A good audit is different in three ways. It measures rather than opines, it ranks what it finds, and it ends with options you could act on with somebody else. This piece says what each of those means and how the Website Risk Analysis does them.

Measure one thing at a time

A measurement is only worth having if it can be repeated. So an audit states, for every figure, the tool, its version, the settings, the date and how many times it was run. Google’s own documentation for its testing tool says the score varies from run to run and that taking the median of several runs reduces the variance. An audit that quotes one run is quoting noise.

It also keeps everything else equal. If a page is slow, the question is what makes it slow, and the only way to answer is to change one thing and measure again: remove the tag manager, measure; shrink the hero image, measure. An audit that lists twelve problems and says “fix them all” has not found out which one matters. The Risk Analysis names the three biggest causes in order of effect, because that is what the one-at-a-time method produces.

The four areas

Speed. The homepage and the three pages that matter most to the business, on a mobile phone and a desktop. Where Google has real-visitor data for the site, that is the measure, because it is what Google uses. Where it does not, the lab test in PageSpeed Insights, run several times, with the median quoted and the settings stated. Page weight and the number of requests, because those are what the fixes change. A waterfall from WebPageTest, which shows what the page waits for and in what order.

Security. The platform and every plugin, by version, checked against the public databases of known flaws; nearly half the flaws disclosed in 2025 had no fix on the day, so a plugin can be fully updated and still exposed. Plugins that have been abandoned by their developers. Whether the admin login is public and how it is protected. Encryption and the response headers, graded by Mozilla’s HTTP Observatory, which anyone can run. Whether backups exist, how old they are, and whether one has ever been restored. Where you give access, a look at the files and the user accounts for signs of past compromise. Where you do not, the report says which findings that limits.

Code. A crawl of every page: broken links, duplicate addresses, redirect chains, pages that cannot be indexed. Markup checked with a validator. Accessibility spot-checked against WCAG 2.2 AA on the pages that matter, with a tool and then by hand, keyboard only, at 200 per cent zoom, with a screen reader. Every third-party script and tag listed, with what it does and whether it fires at all; a surprising number do not.

Search. Whether the site can be indexed, the sitemap and robots file, titles and descriptions, structured data that validates. How the site presents to the AI crawlers: whether the content is in the page or fetched by script, which crawlers are allowed. And, with Search Console access, the pages that earn visits and the pages that waste them, which decides what to keep if the site moves.

Rank what you find

A list of 200 findings is not a result. Each finding in the security section is ranked by two things: how likely it is to be exploited, and how much damage that would do. An abandoned plugin with a known flaw and a public exploit is top of the list. A missing header on a page that sets no cookies is near the bottom. The code section ranks by severity in the same way. The summary page shows one rating for each area and the one thing to know about each.

End with options, not a pitch

The report ends with three options: fix in place, move the site, or do nothing yet. Each comes with what it involves, an honest cost range, what it fixes and what it leaves. We recommend one, and sometimes the recommendation is to do nothing yet, or to fix three things and stop. The cost ranges are there so you can take the report to anyone and get a quote against it. The report is yours. There is no obligation to proceed with us, and the fee is credited if you do.

How to tell a good audit from a sales document

Ask four questions of any audit you are offered. Does every figure say how it was measured and when? Does it rank what it found, or just list it? Does it end with more than one option? And would it be useful if you never spoke to the auditor again? If the answer to any of those is no, it is a pitch with a score on the front.

The Website Risk Analysis is a fixed price, five working days from access, and the report is yours.

  • NextWhy a website that is launched and left decays, and what looking after it involvesThe old agency model is built to win and launch projects, not to keep them working, so most sites start failing in year two for want of anyone whose job it was to look, and looking after a site is a set of tasks on cadences set by published standards, priced for the work and not as a share of the build.
  • PreviousOwning your own websiteA business owns its website only when it can name who holds the domain, the hosting, the code and the editor sign-in, and can move each without the supplier's goodwill, and most owners have never checked.

Sources (6)

  1. Lighthouse score variability Google, Lighthouse project, Current. Accessed 28 October 2026.
  2. Lighthouse performance scoring Google, Chrome for Developers, Current. Accessed 28 October 2026.
  3. Core Web Vitals report in Search Console Google, Current. Accessed 28 October 2026.
  4. HTTP Observatory tests and scoring MDN, Current. Accessed 28 October 2026.
  5. State of WordPress Security in 2026 Patchstack (vendor), 25 February 2026, covering 2025. Accessed 28 October 2026.
  6. What's new in WCAG 2.2 W3C, 5 October 2023. Accessed 28 October 2026.