How to Audit Your Own Website in 15 Minutes (No Budget Needed)

Most business owners never look under the hood of their own website. They notice enquiries have gone quiet, or a competitor's turned up above them on Google, and they either shrug it off or jump straight to hiring someone. There's a step most people skip: fifteen minutes with the same free tools an agency would use on a discovery call, before you spend a dollar.

You don't need a marketing background or a developer. You need three browser tabs, your own phone, and fifteen minutes you were probably going to spend scrolling anyway. Here's the order that gets you the most information for the least effort.

Two rules before you start. First, write down what you find as you go — a note on your phone is fine — because the value of this exercise is comparing it to what you find in six months, not just knowing it once. Second, don't fix anything mid-audit. It's tempting to jump into your website builder the second you spot a problem, but you'll get a much more useful picture if you finish the full fifteen minutes first and triage afterwards.

Minutes 0–5: PageSpeed Insights tells you if speed is the problem

Open PageSpeed Insights, type in your domain, and run it. Do this twice — once for mobile, once for desktop — and pay more attention to mobile. For most Australian small businesses, more than half of local search traffic arrives on a phone, and that's the score Google actually weighs when it decides how to rank you.

The score bands are simple: 90+ is green and good, 50–89 is orange ("needs improvement"), under 50 is red and a genuine problem. If your mobile score is red, you don't need to interpret anything further — that's the finding.

Underneath the headline number you'll see three metrics worth knowing: LCP (how long the biggest visible thing takes to load), INP (how quickly the page responds when someone taps something), and CLS (whether things jump around while loading — the classic "I went to tap a button and the page moved" problem). You don't need to fix these yourself. You just need to know if they're red, because that's the language a developer will use when you eventually ask someone to look at it.

Run it a second time on whatever page actually earns you money — a service page, a booking page, a menu — not just the homepage. Homepages get disproportionate design attention and interior pages get whatever's left over. It's common to see a clean 80+ homepage score sitting next to a 30 on the page that's supposed to convert.

Minutes 5–10: Search Console tells you what Google actually sees

If you don't already have Google Search Console set up, do it now — it's free, it's Google's own data about your own site, and verification takes about five minutes with a DNS record or HTML tag your host can add. If you already have it, open it and go to three reports.

Performance shows impressions and clicks over time. If impressions are falling, Google is showing your site less often — that's a visibility problem. If impressions are steady but clicks are falling, people are seeing you and skipping you, which usually means your title or listing isn't earning the click.

Coverage (sometimes labelled "Pages" or "Indexing") shows what Google has and hasn't indexed. Watch for "Crawled — currently not indexed," which means Google visited a page and decided it wasn't worth including. A handful of these is normal. A large chunk of your site sitting in that bucket is not.

Core Web Vitals groups your URLs by performance and shows how many sit in the red, orange or green band. If this matches what PageSpeed Insights just told you, you've confirmed it's a real, site-wide pattern rather than a one-page fluke.

If what you find here looks less like a plateau and more like a drop over a specific window, we've written the longer diagnostic on splitting an SEO problem from a site problem — worth a read before you assume it's an algorithm thing.

Minutes 10–13: put the site in your own hand

Skip the desktop for this bit. Pick up your phone, turn wifi off so you're on real mobile data, and load your own site the way a stranger would.

Check four things specifically: can you see the main call-to-action — book, call, enquire — without scrolling? Does tapping your phone number actually open the dialler, or is it just text? Can you read the body copy without pinching to zoom? And does anything overlap or run off the edge of the screen when you rotate it?

Then actually use the thing you're asking customers to use. Fill in the enquiry form or booking widget yourself, on your phone, start to finish, and see where it gets annoying. Does the keyboard cover the field you're typing into? Does a dropdown open a tiny scroll wheel you can barely read? Does it ask for information twice? Most owners have never done this once. It's the single fastest way to find the exact moment a real customer gives up.

Google retired its standalone Mobile-Friendly Test tool a while back — that check now lives inside PageSpeed Insights and Search Console. But your own thumb, on your own site, on actual mobile data, still catches things a score can't: the enquiry form that's technically "mobile responsive" but genuinely painful to fill in with one hand.

Minutes 13–15: two searches that show you what everyone else sees

In Google, search site:yourdomain.com. This shows you what's actually indexed and roughly how Google's ordered it — you'll sometimes find an old staging page, a duplicate, or a page you thought was gone still sitting in the results.

Then search your business name plus your main service — the way an actual customer would — and read your own listing the way they would. Is the title clear about what you do and where? Does the description under it read like something a person wrote, or has Google pulled a random paragraph because you never set one? If you want to check the title tag directly, view the page source (right-click, "View Page Source," or Cmd+Option+U on Mac) and look at what's between the <title> tags.

What fifteen minutes won't tell you

Be honest with yourself about the limits here. These tools show you symptoms, not causes. A red PageSpeed score tells you the site is slow — it doesn't tell you whether that's an unoptimised hero image, a chat widget script loading before anything else, cheap hosting, or a platform that was never built to be fast in the first place. Search Console tells you a page isn't indexed — it doesn't tell you whether the fix is a content problem or a technical one underneath it.

That last distinction matters more than most owners expect. If your site's been running on the same page-builder for a few years and everything above is red, the honest next question is whether you're optimising a platform that has a hard ceiling. We've written the actual five-year numbers on that in our Squarespace cost comparison — it applies just as well if you're on Wix or an old WordPress theme. And if you get to the point of wanting the site rebuilt properly rather than patched, that's the work we do — the custom web design page has the detail.

Fifteen minutes gets you further than most business owners ever go on their own site. It won't get you a diagnosis of exactly what to fix or in what order — that takes someone reading the actual code, not just the dashboard numbers.

If you'd rather have the fifteen minutes done for you — the same PageSpeed and Core Web Vitals data pulled automatically, plus the on-page issues we'd flag on a discovery call, written up rather than scattered across three tabs — run our free audit. It takes about thirty seconds either way, and you keep the report regardless of what you decide to do with it.