A website audit that opens with a mood board has skipped the work. The first list is operational: which URLs return an error, which templates visitors actually land on, which forms fail or flood the inbox with spam. Add the scripts that block the first paint. A redesign may still be the right project. It’s the wrong first sentence when the contact form posts nowhere and the service page is a 404 from an ad you’re already paying for.
Scope the audit to pages that take traffic or take money: home, the main service paths, pricing if you have it, and the contact or application form. A 2017 blog archive can wait unless it’s a landing page. Write findings as “this URL, this behavior, this evidence,” not “the site feels dated.” Dated is a taste argument. A form that returns a blank 500 error is a fact.
What should a website audit list first?
Broken paths come first. Click every item in the main menu and every button that claims to start a project. Note redirects that chain more than once, links that leave the canonical host, and buttons that are styled divs with no destination. A menu item that looks fine and leads to a draft is a sales problem, not a font problem.
Speed findings stay tied to a template, not to one lab score. If the home page ships a full-screen video and three sliders before the headline is readable, say that. Say what a lighter first view would keep. If an interior page is fast and the home page isn’t, the audit shouldn’t recommend rebuilding every template. One heavy header included everywhere is a smaller job than a new theme. It should be priced that way so the client can choose. Core Web Vitals gives you shared vocabulary for the numbers.
Forms and tracking are the quiet failures. Submit the form with a normal message, then with an empty required field. Confirm the message arrives somewhere a person reads, not only that the button said thank you. If analytics is installed, confirm the form success is recorded as an event. A site that “gets no leads” and never fires an event can’t be redesigned into clarity. You’d be painting over a mailbox that was never connected.
What is the audit allowed to recommend?
Order recommendations by what they unblock. Fix the form and the broken service URL before a visual pass. Fix a shared script that throws an error on every page before a new homepage illustration. A redesign recommendation is honest when the current templates can’t carry the offer: the structure has no place for the services you really sell, or the theme can’t be updated without forking it. That’s a build argument. “Modernize the look” without that constraint is a preference, and it belongs in a separate estimate so nobody confuses taste with the outage.
Before any rebuild is proposed, pair the audit with a content inventory, so you know which pages are worth carrying over.
How should the findings be delivered?
Hand over a short table the next person can work from: URL, severity, evidence, suggested fix. Also say whether the fix is content, a plugin setting, or template code. Screenshots help. A 40-page brand narrative doesn’t. If one finding needs a developer and another needs the client to rewrite a paragraph, label them differently. Mixing them in one “phase two” is how small text fixes wait behind a redesign that hasn’t been approved.
Do a basic security look at the same time. Outdated plugins and an abandoned form add-on are audit findings, and the security pass post covers how to handle them without a rebuild.
Why do this before design?
It keeps the first invoice attached to something a visitor can already feel: the page loads, the path exists, the message arrives. Visual work after that has a stable floor. If you want this done for your site, the website audit service page spells out the engagement. How it works shows where it sits in a project. You can also contact us to ask about one.