A slow website is losing you customers right now, quietly, without ever telling you. Someone searches for "emergency plumber Geelong", taps your listing, waits, and taps back to Google before your homepage finishes loading. You never see that lost enquiry — it just doesn't happen. Before you spend money on a redesign or a developer's invoice, run your own website speed audit first. It takes under an hour, costs nothing, and tells you exactly what's worth fixing.
Why a Speed Audit Matters
Speed isn't just a technical nicety — it's tied directly to whether people stay on your site and whether Google shows it to them in the first place.
- Lost enquiries. Most visitors are on their phones, often on patchy mobile data, and a page that drags on loses people before it renders.
- Search rankings. Google uses page experience signals, including Core Web Vitals, as part of how it ranks pages. A consistently slow site works against itself.
- Wasted ad spend. Sending Google Ads clicks to a slow landing page means paying for visitors who bounce before converting — see SEO vs Google Ads for how the two work together.
- Wasted trust. A site that stutters and jumps around as it loads reads as unprofessional, even with lovely design.
A speed audit gives you evidence instead of a hunch that "the site feels a bit slow" — specific numbers and a specific list of causes, which is exactly what you need before asking a developer to fix anything, or before fixing it yourself.
The Four Tools You Need
Four free tools, used together, will tell you almost everything about how your site performs.
Google PageSpeed Insights
Built on Google's own Lighthouse engine, this shows both a simulated lab test and, if your site gets enough traffic, real-world data from actual visitors. It gives a 0–100 score for mobile and desktop separately, plus a list of specific opportunities to improve.
GTmetrix
GTmetrix lets you choose the test server location and connection speed, and it's particularly good at showing a visual "waterfall" of exactly which files are loading slowly and in what order. Handy for spotting one enormous image or a script holding everything else up.
WebPageTest
The most technical of the four, best for testing from multiple real-world locations and connection types, including repeat views (how fast the site loads for a returning visitor thanks to caching). It's more detail than most business owners need day-to-day, but worth running once to double-check the simpler tools.
Lighthouse in Chrome DevTools
Built directly into Chrome. Right-click any page, choose "Inspect", open the "Lighthouse" tab, and run a report without leaving your browser. Same engine as PageSpeed Insights, so scores are consistent, and it's the fastest way to re-test a page after making a change.
| Tool | Best for | Shows real visitor data? | Multiple locations? |
|---|---|---|---|
| Google PageSpeed Insights | Quick overall score + fixes | Yes (if enough traffic) | No |
| GTmetrix | Visual waterfall of what's loading slowly | No | Limited (choose one) |
| WebPageTest | Deep technical testing, repeat views | No | Yes |
| Lighthouse (Chrome DevTools) | Fast re-testing during fixes | No | No |
For a fuller rundown of when to use each one, our guide to the best website speed testing tools goes deeper on this.
Making Sense of the Scores
The overall 0–100 score is useful, but the real gold is in three metrics known as Core Web Vitals.
- LCP (Largest Contentful Paint) — how long the biggest visible thing on the page (usually a hero image or heading) takes to fully appear. This is your visitor's sense of "has the page actually loaded?"
- INP (Interaction to Next Paint) — how quickly the page responds when someone taps a button or link. A high INP feels like the site is ignoring you.
- CLS (Cumulative Layout Shift) — how much the page jumps around as it loads. Think "I went to tap the button and an image loaded above it, so I clicked the wrong thing."
Google rates each of these "Good", "Needs Improvement" or "Poor". Aim for "Good" on all three, particularly on your homepage and any page you send ads traffic to. For a full breakdown, read our Google Core Web Vitals guide, and for what "fast enough" looks like in practice, see how fast should a website load.
A Real Example: The Bendigo Mechanic
Picture a mechanic's workshop in Bendigo with a perfectly nice-looking site built a few years back. Business was steady, but online enquiries had quietly dried up. Running PageSpeed Insights told the story in under a minute: a mobile score in the 30s, LCP well over five seconds, and the culprit obvious on the waterfall — a gallery of workshop photos, each several megabytes straight from a phone camera, none resized or compressed before being uploaded.
Nothing about the workshop or the business had changed. The photos alone were quietly costing enquiries every day. Oversized images are still the single biggest cause of slow small-business websites in Australia, ahead of clunky plugins or bad hosting.
The Complete Website Speed Audit Checklist
Work through this in order — most steps take minutes and none require coding knowledge.
- Test your homepage on PageSpeed Insights — record mobile and desktop scores separately. Mobile matters most for Australian visitors.
- Test your key pages — contact page, main service/product pages, and any page your Google Ads point to.
- Run the same pages through GTmetrix — check the waterfall for any single file that loads far slower than the rest.
- Run one page through WebPageTest — choose a location near your customers (Sydney or Melbourne) and note the repeat-view result, which reflects caching.
- Check your image sizes — use PageSpeed Insights' "Diagnostics" section to spot oversized or uncompressed images.
- Check your font loading — a flash of invisible or unstyled text usually means fonts aren't set up efficiently.
- List every plugin and third-party script — chat widgets, booking tools, tracking pixels, review widgets. Each adds load time, and not all earn their keep.
- Check your hosting — a "Time to First Byte" over roughly half a second usually points to underpowered or overloaded hosting.
- Check whether caching is switched on — repeat-view results should be noticeably faster than the first visit. See caching explained for what to look for.
- Test on an actual phone, on mobile data — not wifi — and time how long the site genuinely feels to load.
- Note every "Poor" or "Needs Improvement" flag — write down specific issues, not just the overall score.
- Re-test after every change — fix one thing at a time and re-run Lighthouse in Chrome DevTools to see the direct impact.
If you're on WordPress, most of what this checklist uncovers has a known fix — see speeding up a WordPress website and common website speed mistakes before you start changing anything.
What the Audit Usually Uncovers
The same handful of issues show up again and again:
- Oversized, uncompressed photos (the Bendigo mechanic problem)
- Too many plugins or apps doing similar jobs
- No caching, or a caching plugin installed but never actually configured
- Budget hosting shared with hundreds of other sites
- Fonts loading from slow third-party sources
- Chat widgets, popups and tracking scripts stacking up over the years
None of these are unfixable, and none require a full rebuild — they just need to be found first. Pair this checklist with our mobile speed optimisation guide for fixes specific to phones and tablets.
Key Takeaways
- Run your homepage and key pages through PageSpeed Insights, GTmetrix, WebPageTest and Lighthouse before paying anyone to fix speed issues.
- Focus on LCP, INP and CLS — the three Core Web Vitals — rather than chasing a single overall score.
- Test on mobile and from an Australian location wherever possible, since that's how most of your customers browse.
- Oversized images are the single most common cause of a slow small-business website.
- Write down specific issues as you find them, fix them one at a time, and re-test after each change.
Frequently Asked Questions
How often should I run a website speed audit?
Run a full audit whenever you add new features, plugins or a redesign, and do a quick check every few months even if nothing's changed. Third-party scripts and plugin updates can slow a site down over time without you touching anything.
Do I need technical skills to run a speed audit?
No. Running the tools takes a few clicks and no coding knowledge. Understanding the results well enough to know what to fix is the harder part, which is where a developer becomes useful even if you've done the testing yourself.
What's a good PageSpeed Insights score to aim for?
Aim for "Good" ratings on Core Web Vitals rather than fixating on the 0–100 number. As a general guide, a mobile score above roughly 70 to 80 with all three Core Web Vitals in the "Good" range is a solid result for a small business site.
Why does my site score differently in different tools?
Each tool tests under slightly different conditions — simulated connection speeds, server locations and test methods — so scores vary between them. Look for the same issues showing up across multiple tools rather than chasing an identical number everywhere.
Is a slow website actually hurting my Google rankings?
Page experience, including Core Web Vitals, is one signal Google considers among many, alongside content quality and relevance. A slow site won't automatically sink your rankings, but on a level playing field with a competitor, speed can be the deciding factor.
What should I do first if I don't have time to fix everything?
Start with images — usually the biggest single win and the easiest to fix without technical help. Compress and correctly size every photo before uploading it, particularly on your homepage and top service pages.
Can plugins alone fix a slow website?
Caching and image-optimisation plugins genuinely help, but they can't fix underpowered hosting, a bloated theme or a page stacked with unnecessary third-party scripts. Treat plugins as one part of the fix, not the whole solution.
Get a website that loads fast and keeps customers
Running your own audit puts you in control before you spend a cent. If you'd rather hand the process over, or want help fixing what it uncovered, have a chat with Pixel and Pine. We build and maintain Australian small business websites that load fast on day one and stay that way.
