What a proper web audit actually looks at
“We need an audit” often means “something feels wrong and we want a list.” The wrong audit produces charts. The right audit produces a sequenced plan: what to fix first, why it matters, and what can wait.
Here is what a proper web audit covers when we run one.
Performance and Core Web Vitals
We measure real user experience signals where possible, not only lab scores. LCP, INP, and CLS on key templates (home, product/service, article) tell us whether the site feels responsive under normal conditions.
- Hero and above-the-fold weight
- Font and third-party script cost
- Image delivery and caching headers
- Layout shifts from late-loading UI
Crawl, index, and technical SEO
Search cannot reward pages it cannot understand. We check robots rules, canonicals, sitemap hygiene, status codes, redirect chains, duplicate titles, thin templates, and structured data that actually matches the page.
A perfect Lighthouse score on a page blocked from indexing is still invisible.
Accessibility and usability
We look for keyboard traps, missing labels, contrast failures, focus states, and mobile tap targets. Accessibility issues are often conversion issues in disguise — especially on forms and checkout.
Content and information architecture
Does the site answer the questions buyers ask? Are service pages differentiated or copy-paste? Is blog content indexed noise? We map important URLs against intent and flag orphans, overlaps, and dead ends.
Conversion path
Audits that ignore the business goal are incomplete. We walk the primary paths: enquire, book, buy. Friction, missing trust, unclear pricing cues, and broken CTAs get the same priority as technical debt when they cost revenue.
Security and maintenance basics
- HTTPS, mixed content, and outdated dependencies where relevant
- Form spam exposure and obvious injection surfaces
- Backup / deploy hygiene if the stack is in scope
What you should receive
Not a dump of every warning. A short severity list: critical (fix now), important (this sprint), and later (nice when capacity allows). Each item with evidence, affected URLs, and a concrete remediation.
That is what a proper web audit looks at — and why the output should feel like a build plan, not a report to file away.