The short verdict
- A useful audit tells you the few things that matter most, in order, and what each would take to fix.
- An automated tool export with your logo on it is not an audit.
- Judge an audit by whether you know what to do next when you finish reading it.
01The problem with most audits
Many audits are a crawler’s output turned into a PDF. Hundreds of warnings: images missing alt text, titles too long, a script that could be deferred. Every item is technically true. Very few are ranked, and almost none are tied to what the site needs to do. Owners read three pages and put it in a folder.
02What a useful audit covers
- Goal fit. Does the site do its main job? Can a visitor tell what you do, for whom, and what to do next?
- Structure and copy. Is the page order right for the buyer? Is the copy specific or generic?
- Design. Hierarchy, spacing, type, and whether it looks like you or like a default.
- Mobile. Tested on real devices, not just a resized window.
- Function. Forms delivering, links working, integrations firing.
- Search basics. Titles, descriptions, rendering, indexing, redirects.
- Speed and accessibility. Real-user data where it exists, and the main barriers.
- Platform. Whether the site can be edited and grown where it is, or should move.
03How findings should be presented
Ranked by impact, not grouped by category. The top of the list should be the two or three things that cost you most, with a plain explanation of why. Each finding should say what to change and roughly how big the job is. And the audit should end with a recommendation: fix these in place, or rebuild.
04What to ignore
- Raw scores out of 100 with no context. A score is not a problem.
- Hundreds of minor warnings for pages nobody visits.
- Generic best practice that does not apply to a site of your size.
- Urgent language designed to sell you the fix. “Critical” should mean something is broken.
“An audit is not measured in pages. It is measured in decisions it helps you make.”
05Free or paid
A free review, like our verdict, gives you the headline: what is holding the site back and what it would take to fix. That is often enough to decide what to do next. A paid, in-depth audit makes sense when the site is large, when several teams need a shared list to work from, or when you plan to do the fixes yourself and need every detail written down.
Whichever you choose, ask to see an example first. If the example is a tool export, you know what you will get.
06Questions people ask
Can I audit my own site?
Partly. Tools like Lighthouse, WAVE and Search Console catch technical issues. An outside view catches what you have stopped noticing, like generic copy or a confusing page order.
How often should a site be audited?
After any major change, and about once a year otherwise. Forms and key pages are worth checking monthly.
Does a free audit come with strings?
Ours does not. You get the verdict whether or not you work with us.
What does your verdict include?
A clear read on what is holding the site back and what it takes to fix. Send the link to get one.
