Most website audits arrive as a PDF with a number on the front page. The number feels useful and rarely is. A score of 72 tells you nothing about what to fix first, what it costs, or whether it matters to your business at all.
A useful audit works more like reading a map. You start wide to see the shape of the terrain, then move in close on the parts that matter. Here is what that actually involves.
Performance and Core Web Vitals
Load time is the part everyone measures and the part most often measured wrong. A synthetic test on a fast connection tells you very little. What matters is field data: how the site behaves on a mid-range phone on mobile data, which is how a large share of your visitors arrive.
The common culprits are unoptimised images, render-blocking scripts, and third-party embeds that nobody remembers adding. Fixing the first two is usually straightforward. Removing the third is a conversation about what those tools are actually delivering.
Structure and Crawlability
Search engines need to find your pages, understand what each one is about, and know which version is canonical. This breaks in quiet ways. Duplicate content across language versions, missing or conflicting canonical tags, orphaned pages with no internal links pointing at them, sitemaps that list URLs which redirect somewhere else.
None of this is visible to a visitor. All of it affects how much of your site gets indexed.
Content That Answers a Real Question
Every page should have a reason to exist that you can state in one sentence. If a page exists because the navigation looked thin without it, that is not a reason. Thin pages dilute the site rather than expanding it.
The stronger test is whether the page answers something a prospective customer would actually type. Pages built around what a company wants to say tend to rank poorly against pages built around what someone wants to know.
Accessibility
Colour contrast, keyboard navigation, form labels, alt text, heading order. This is partly a legal question in the EU and increasingly enforced, but it is also just a proxy for build quality. Sites that fail accessibility checks usually fail them because the markup is sloppy, and sloppy markup causes other problems too.
Privacy and Compliance
Which third parties receive visitor data, whether consent is collected before anything loads, whether your privacy policy matches what the site actually does. The gap between the stated policy and the observed network requests is where most GDPR problems live.
The Output That Matters
A good audit ends with a short ordered list: what to fix, roughly what it costs, and what happens if you do not. Three items you will act on beat forty items you will not.
If you want a second pair of eyes on your own site, that is the format we work in.