What Actually Happens During a Website Audit

Anthony Cicirello, WordPress and SEO specialist at Rocket Web Designer Anthony Cicirello · · 6 min read
Google Analytics dashboard showing website performance data

Let me pop the hood on this, because “website audit” gets used to describe a lot of different things, and most of them are not an audit. A five minute skim of your homepage is an opinion. A real audit is a process, and it looks the same whether the site belongs to a plumber or a law firm.

Here’s what that process actually covers, step by step, so you know what you’re paying for and what you should expect to walk away with.

Step 1: Pull the technical numbers first

Before anyone looks at colors or headlines, a real audit checks the plumbing. That means load time on both desktop and mobile, whether SSL is active and current, whether the sitemap is submitted and actually being read by Google, and whether pages that should be indexed are indexed. These are boring checks. They are also the checks that quietly decide whether anyone ever sees the rest of your site.

What gets measured here

  • Page load speed on a real mobile connection, not just wifi in the office
  • Whether the site is genuinely mobile responsive or just technically shrinks to fit
  • Broken links and broken images, especially on older pages nobody has opened in a year
  • Indexing status: is Google actually crawling and showing your pages
  • Image file sizes, since one uncompressed photo can drag down an entire page
  • Whether old redirects and old plugins are still quietly running in the background

None of these numbers mean much on their own. A load time of three seconds sounds fine until you learn most mobile visitors bail before a slow page ever finishes loading. Context is what turns a number into a decision.

Step 2: Check the SEO fundamentals

Next comes the on-page layer. Title tags, meta descriptions, header structure, whether your service pages are targeting the terms people in your area actually search, and whether your SEO foundation is even set up to be found. A lot of small business sites look fine and rank nowhere, and this step is usually where you find out why.

This is also where I get a peek at what’s actually driving traffic versus what’s just sitting there. Not every visit is equal.

Step 3: Watch what a visitor actually does

A technically perfect site that nobody acts on still isn’t working. This step traces the path a real visitor takes: what they see first, whether there’s an obvious next step, and where they get stuck or bail out. If your homepage looks great but the phone doesn’t ring, the problem usually lives here.

This is also where I get picky about the word “conversions.” A lot of dashboards count a button click as a conversion. A click is not a conversion. A form submission with a real phone number is a conversion. A call that lasts longer than twenty seconds is a conversion. Anything less is just someone’s thumb moving.

A real example of what this catches

An HVAC company I looked at once was convinced their website simply didn’t work for them anymore. Traffic looked fine in their old analytics. Calls had dried up. Nothing obviously changed on their end, so the assumption was that the market had just gotten tighter.

Here’s what the audit actually found. Their contact form was still receiving submissions, but the plugin sending those submissions to email had silently broken during a routine update three months earlier. Nobody got an error message. Nobody got a bounce notice. The form just quietly swallowed every lead that came through it, politely told the visitor “thanks, we’ll be in touch,” and then sent nothing anywhere. Three months of leads, gone, and the business had no idea.

That’s not a rare story. It’s the single most common thing a technical audit turns up, and it’s exactly the kind of problem you cannot see just by looking at your own homepage, because your homepage looks completely normal the whole time it’s happening.

Step 4: Security and the stuff nobody thinks about

Outdated plugins, weak admin passwords, missing backups, forms that quietly stopped sending email three months ago without anyone noticing. None of this shows up when you glance at the homepage, and all of it can cost you real leads. Checking it is not exciting. Skipping it is expensive.

Step 5: Turn all of it into a priority list

Here’s the part that actually matters to you as the owner. A pile of forty issues with no order is overwhelming and useless. A good audit sorts everything by impact: what’s costing you traffic or leads right now, what’s a slow leak, and what’s genuinely fine to leave for later.

Think of it in juice box math. If your site brings in ten leads a month and three of them come from a contact form that’s been silently broken, fixing that form is worth more than a new homepage photo. Priority order is the whole point.

What a finished audit hands you

  1. A plain-English summary of what’s actually wrong, not a jargon dump
  2. A ranked list, worst problems first, not alphabetical or random order
  3. Rough effort level for each fix, so you know what’s a five minute job and what’s a project
  4. A clear starting point, because “fix everything” is not a plan anyone can act on Monday morning

Common mistakes owners make before booking one

A few habits show up again and again, and all of them make the audit less useful than it should be:

  • Judging the site only by how it looks, when most of what’s actually broken is invisible from the front end
  • Assuming a redesign a few years ago means everything technical is still fine today, when plugins and settings drift on their own
  • Trying to fix everything at once instead of working the priority list in order
  • Skipping the mobile check because the desktop version looks great, even though most visitors never see the desktop version
  • Treating the audit as a one-time event instead of a baseline to check back against later

That last one matters more than owners expect. An audit isn’t just a snapshot, it’s a benchmark. Running one again a year later shows you whether things actually got fixed or just got talked about.

Why bother if the site “seems fine”

Because “seems fine” is measured from the inside. You know your business. You know what the site is supposed to say. A visitor doesn’t have any of that context, they just have ten seconds and a thumb. Traffic that lands on a slow, confusing, or broken step is money doing push-ups. It’s working hard and going nowhere.

Most owners find at least one real problem they had no idea existed. Not a nitpick, a genuine leak. The HVAC company above thought their site was fine too, right up until it wasn’t.

What to do this week

  1. Submit your own contact form and confirm the email actually lands somewhere someone checks
  2. Call your own business number from the website and see how long it takes to get an answer
  3. Check your SSL certificate hasn’t expired and your sitemap is still submitted correctly
  4. Write down anything that felt slow, confusing, or broken, even small things

The move: Get someone to actually click through your own site today, on a phone, on cell data, start to finish, like a stranger would.

Frequently asked questions

How long does a real website audit take?

A thorough audit usually takes a few days, not a few minutes. Technical checks are quick to run, but reviewing conversion paths and prioritizing the results properly takes actual time.

Do I need an audit if my site looks fine to me?

Yes, because you’re looking at it with context a visitor doesn’t have. Most owners find at least one real issue they didn’t know was costing them leads.

What should I do with the results first?

Start at the top of the priority list, not wherever feels most interesting. The point of ranking issues is so the highest impact fix gets handled first.