Website Audit Checklist: How to Check Your Site

This website audit checklist gives a business owner a repeatable way to check a site after launch. A site that nobody reviews keeps aging quietly while browsers change, phones change shape, and search results shift around it. Nothing announces when it starts falling behind, so the first signal is usually indirect: fewer calls, fewer form submissions, or a question from a customer who could not find something.

You don't need to hire someone to find out if your website is working against you. You can do a real, useful audit yourself in about an hour, using nothing but your own eyes, your phone, and a couple of free tools. This is the same kind of walkthrough we run before proposing any fix, because many issues are visible once you know where to look.

This article gives you that checklist. Not a vague "make sure your site looks good" list — a specific, ordered set of checks you can run today, plus a fictional example showing what the results actually look like in practice.

Why most business owners never do this

Nobody budgets time for a website audit the same way they budget time for bookkeeping or inventory checks. The website was a project once — it got built, it got approved, everyone moved on. Checking on it feels like reopening a closed chapter.

But a website isn't a brochure you print once. It's a piece of equipment that degrades if nobody maintains it: forms stop working after a plugin update, contact information goes stale, mobile rendering breaks after a browser update, and pages that used to rank quietly slide down as competitors update theirs. None of that shows up unless you go looking.

The other reason owners skip this: they assume it requires technical skill. It doesn't. Most of what actually costs you inquiries is stuff you can see and judge for yourself — you just need to know what to check and in what order.

The Full Self-Check: 9 things to review, in order

Run through these in sequence. Each one takes a few minutes. Do this on your actual phone and a laptop or desktop, not just one device.

1. Load speed on mobile

Open your site on your phone using regular mobile data, not office Wi-Fi. Time how long it takes for the page to become usable — not just for something to appear, but for you to be able to tap a button or read text without it jumping around.

Then run your homepage through Google's PageSpeed Insights (free, no signup). Read the results carefully, because the page shows two different kinds of data:

• The 0–100 performance score is a lab result. It comes from a single simulated load on a simulated device and network. It is a diagnostic hint, not a measurement of your visitors' experience, and it can move several points between runs on the same unchanged page.
• The "Discover what your real users are experiencing" section is field data from the Chrome User Experience Report, when Chrome has collected enough visits for your site. That section is closer to what people actually encounter.

The mobile and desktop tabs also run under different simulated conditions, so a lower mobile score does not by itself prove the page is broken on phones. Use the score to find specific opportunities the report names — oversized images, render-blocking scripts, layout shift — and use the field data, plus your own timed load on a real phone, to judge how much any of it matters.

What not to conclude: a red score does not mean you are losing inquiries. It means the report found issues worth reviewing. Whether those issues cost you contacts is something only your own analytics and form submissions can indicate.

2. Mobile layout, not just mobile speed

Speed and layout are different problems. Scroll through every main page on your phone. Look for:

• Text that's too small to read without zooming
• Buttons or links crammed too close together to tap accurately
• Images that overflow the screen or get cut off
• Menus that don't open, or open and don't close
• Forms where the keyboard covers the field you're typing into

Before you decide how much weight to give this, check your actual device mix rather than assuming one. If you have an analytics tool installed, look at sessions by device category for the last 90 days. Search Console's device breakdown is useful too, but be clear on what it covers: it reports clicks and impressions from Google Search results, not all visits, so it will not include direct traffic, referrals, or ads.

If you have no data at all, treat the mobile layout as unverified rather than assuming a majority — and either way, fix anything on this list that makes the page unusable on a phone. A button nobody can tap is worth fixing at any traffic share.

3. The homepage's first ten seconds

Load your homepage as if you'd never seen it before. Without scrolling, can a stranger tell:

• What you do
• Who you do it for
• What they should do next (call, book, request a quote)

If the answer requires scrolling or reading a paragraph, that's a problem. Most visitors decide whether to stay or leave before they've read anything — it's the visual layout and the first line of text doing the work, not your full pitch.

4. Every contact method, tested for real

Don't assume your phone number, email, and forms work. Test them:

• Click the phone number on mobile — does it actually dial?
• Submit the contact form with a test message — does it arrive somewhere someone checks?
• Click every email link — does it open a new message to the right address?
• If you have a chat widget, is anyone actually monitoring it, or is it just sitting there unanswered?

This is worth testing rather than assuming, because form delivery can fail invisibly. Consider a hypothetical case: a plugin update changes how a site sends mail, the form still shows its success message, and the messages stop arriving. Nothing looks broken from the outside, so the only way to catch it is to submit the form yourself and confirm the message lands in the inbox you expect.

5. Calls to action on every page

Go page by page and ask: if someone landed here first, would they know what to do? Every page — not just the homepage — needs a clear next step. That could be "Call now," "Request a quote," "Book an assessment," whatever fits your business. Pages with no call to action, or three competing ones, both cause visitors to leave without acting.

6. Trust signals

Look at your site the way a stranger who's never heard of you would. Is there anything that tells them you're legitimate and good at what you do? Check for:

• Real photos of your work, team, or location — not generic stock images
• Reviews or testimonials, ideally with names or specifics attached
• Clear information about who runs the business and where you're located
• Certifications, licenses, or affiliations relevant to your industry, if you have them

Absence of these doesn't mean you're not trustworthy — it means the website isn't doing the job of proving it.

7. Content that's gone stale

Read through your service pages, hours, pricing (if listed), and any "latest news" or blog section. Look for:

• Prices or offers that no longer apply
• Services you no longer provide, or new ones missing entirely
• Blog posts referencing events, promotions, or years that have long passed
• A footer copyright year that no longer matches the current year

Be precise about what matters here. An out-of-date copyright year is not a search penalty on its own; Google does not publish any such rule. It is a small credibility detail some visitors notice, and it is quick to correct. What genuinely needs attention is content that is now inaccurate: wrong prices, discontinued services, old hours, superseded instructions.

The opposite mistake is just as common. An older article that is still accurate and useful does not need to be touched, and changing its date to look fresh without changing anything real is not an improvement. Update facts, not timestamps.

8. Search visibility, the simple way

Search Google for your business name plus your city or service. Does your site show up? Then search for a service you offer plus your city, without your business name (like "[service] in [city]"). If you don't show up on the first page for a search that should obviously include you, that's worth noting — though ranking is a longer conversation than this checklist covers.

9. Security basics

Check that your web address starts with "https" and does not show a "not secure" warning. HTTPS protects data moving between the visitor and the site. Treat a browser warning as a priority because it can undermine trust before a visitor reaches your content.

Where to record what you find

A checklist is only useful if you write down the results somewhere you'll actually look at again. You don't need anything fancy — a single page in a notebook or a plain document works. For each of the nine checks, note three things: what you found, how confident you are that it's actually a problem versus a minor annoyance, and whether it's something you could fix yourself or something that needs help.

That third column matters more than it seems. Some of what you'll find — an outdated copyright year, a missing review, a stale promotion — is a five-minute fix once you know it's there. Other things, like a form that silently fails because of a backend integration issue, or a mobile layout problem tied to how the site's theme was built, take more digging. Separating the two keeps you from either ignoring easy wins or getting stuck trying to fix something that needs a developer's attention.

It also helps to date your notes. A self-check you ran in January means less by the following December — browsers update, your services change, and competitors' sites move. Treating the checklist as a recurring habit, not a one-time event, is what actually keeps a website from quietly drifting out of date again.

Common mistakes owners make when self-auditing

A few patterns show up often enough to call out directly.

Only checking on a desktop. Phones and desktops render the same page differently, so a desktop-only check misses a whole class of problems. Rather than assuming which share of your visitors is on a phone, look at your own device data — and run the full list on a phone regardless, because that is where cramped buttons, overflowing images, and keyboard-covered form fields appear.

Judging the site by how it looks to you, not a stranger. You already know what your business does, so gaps in the homepage message don't register the same way for you as they do for someone landing on the page for the first time. Where possible, ask someone unfamiliar with your business to look at the homepage for ten seconds and tell you what you do. Their answer tells you more than your own read of the page.

Stopping at the homepage. Most audits get lazy after the front page. But visitors don't only land on your homepage — they land on service pages from search results, on location pages from map listings, on blog posts from search queries. A page with no call to action or a broken layout costs you the same inquiry whether it's the homepage or a page three clicks deep.

Confusing "it looks fine to me" with "it works." Visual inspection catches layout and content issues, but it won't catch a form that fails silently, a broken tracking pixel, or a slow-loading script that only shows up under a real speed test. That's why the checklist mixes visual review with a couple of actual functional tests — submitting the form, timing the load, running the PageSpeed tool — rather than relying on eyeballing alone.

FICTIONAL EXAMPLE: A self-audit for "Ridge & Co. Plumbing"

To show what this looks like in practice, here's a fictional example. Ridge & Co. Plumbing is a made-up local plumbing company, used here only to illustrate the process — not a real client or a promised outcome.

The fictional owner runs through the nine checks above on a Sunday morning:

• Mobile speed: in this made-up scenario, PageSpeed Insights returns a mobile lab score in the low 30s and flags three large, uncompressed photos loading before any text appears. The owner treats the flagged images as the finding, not the score itself.
• Mobile layout: The main menu opens fine but the "Call Now" button is hidden below the fold on phones — visitors have to scroll to find it.
• First ten seconds: The homepage headline reads "Welcome to Ridge & Co." with no mention of plumbing, location, or service area until the second scroll.
• Contact methods: The phone number is a live link and works. The contact form, though, silently fails — a test submission never arrives in the fictional owner's inbox because the form was pointed at an old email address from a previous site.
• Calls to action: The homepage has a "Call Now" button, but the emergency service page has none — just a paragraph of text.
• Trust signals: No reviews are shown anywhere on the site, despite (in this fictional scenario) having dozens on Google.
• Stale content: The footer still reads "© 2019," and a "current promotions" page references a fictional spring discount that expired years earlier.
• Search visibility: Searching "[fictional city] emergency plumber" doesn't surface the site on the first page.
• Security: The site loads over https with no warning.

None of these individually would sink the business. Together, they explain a plausible pattern in this fictional example: reasonable traffic, but a low rate of inquiries relative to that traffic. The fix list that comes out of an audit like this is usually short and concrete — reconnect the form, compress the images, move the call button up, add a handful of real reviews, update the footer year. That's the value of doing the check: turning a vague feeling that "the website isn't working" into a specific, fixable list.

Your exercise: run this on your own site today

Set aside 45 minutes. Open your site on your phone and a laptop side by side. Go through the nine checks above in order, and for each one, write down a single sentence: pass, fail, or "not sure." Don't fix anything yet — just document what you find. At the end, you'll have a short list of specific issues instead of a vague sense that something's off. That list is what makes a follow-up conversation with anyone — us or otherwise — productive, because you'll already know what's actually wrong instead of guessing.

The Geek Heros angle

Over nine years, Geek Heros has built more than 350 websites and served more than 1,300 businesses — two separate figures, since most of the businesses we have worked with came to us for support, review, or repair rather than a new build. That mix is why this checklist leans toward unglamorous, checkable things: whether a form delivers, whether a button is reachable on a phone, whether the homepage says what the business does. We are not claiming a measured pattern across every site we have seen; these are simply the checks that most often surface something worth fixing.

We're a veteran and first-responder owned shop — our founder is a Marine veteran and a firefighter/paramedic — and the way we approach a website is the same way you'd approach any equipment check: go through it systematically, note what's actually wrong, and don't guess. The same systematic approach guides an outside review: document what is working, identify what is not, and separate observable problems from assumptions.

Sources and further reading

• Google PageSpeed Insights — Google's free tool for checking page performance; reports both lab results and, where available, real-user field data.
• web.dev: Lab and field data — explains why a lab score and real-user metrics can disagree, and how to use each.
• MDN: Transport Layer Security — primary technical documentation explaining HTTPS/TLS protections.

FAQs

How often should I audit my own website?

Twice a year is a reasonable baseline for most small business sites. If you've recently changed your services, moved, run a marketing campaign, or noticed a drop in inquiries, run the check sooner — those are the moments things are most likely to have changed or broken.

Do I need any paid tools to do this?

No. Everything in this checklist uses things you already have — your phone, a browser, your own analytics if it is installed, and Google's free PageSpeed Insights tool. You don't need paid software or an agency to find most of these issues.

What if I find several problems at once — what should I fix first?

Start with anything that stops someone from contacting you, like a broken form or an unreachable contact method. Those directly prevent an inquiry. After that, use your own traffic data to decide how heavily to prioritize mobile speed and layout, then move to trust signals and stale content.

I ran the checklist and everything passed — does that mean my website is fine?

It means the visible, checkable basics are solid, which matters. It doesn't rule out deeper issues like search ranking factors, site structure, or conversion patterns that need more than a visual check. If your basics pass but results still feel off, that's worth a closer look rather than more guessing.