Type your website into the wrong tool and you'll get a scary red score with no idea what it means or whether it actually matters. Type it into the right one and you'll know exactly what's slowing your site down and what to fix first. There are only a handful of website speed testing tools worth your time, and each one answers a slightly different question. Here's what each does, who it's for, and which one to reach for first.
Why Bother Testing Your Own Site
You might assume your web designer or developer keeps an eye on this. Sometimes they do. Often they don't, especially once a project has shipped and everyone's moved on to the next job. Speed also drifts over time — a new plugin, a bigger hero image, an extra tracking script from your marketing team, and a site that once loaded quickly starts to lag.
Testing your own site takes a few minutes and tells you:
- Whether your pages meet Google's Core Web Vitals thresholds.
- Whether a recent change (new host, new theme, new plugin) helped or hurt.
- Which specific files or scripts are the biggest offenders.
- How your site compares between mobile and desktop.
You don't need to become a performance engineer to get value from this. You just need to know which tool to open and what to look at.
Google PageSpeed Insights: Start Here If You're Not Technical
If you only ever use one tool, make it Google PageSpeed Insights. It's free, it's from Google, and it's the closest thing to "the truth" when it comes to how Google itself judges your site's speed.
PageSpeed Insights gives you two kinds of data. The first is field data — real-world performance from actual visitors who've used Chrome, pulled from the Chrome UX Report. The second is lab data — a simulated test run at the moment you check, similar to what Lighthouse produces. You get a score out of 100 for both mobile and desktop, plus a breakdown of your Core Web Vitals: Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift.
Best for: business owners who want a fast, credible answer with no setup. Cost: free. What it measures: Core Web Vitals, overall performance score, and a prioritised list of opportunities (like "reduce unused JavaScript" or "serve images in next-gen formats").
If you want to understand what those Core Web Vitals numbers actually mean and why Google cares about them, our Core Web Vitals guide walks through each metric in plain English.
Lighthouse: The Engine Under the Bonnet
Lighthouse is built directly into Chrome. Open Chrome DevTools (right-click any page, choose "Inspect", then find the Lighthouse tab), pick "Mobile" or "Desktop", and run an audit. It's the same engine that powers the lab data half of PageSpeed Insights, so the scores will look familiar.
The advantage of running Lighthouse directly is control. You can test a page that isn't live yet, test behind a login, throttle the network to simulate a slow connection, and dig into categories beyond speed — accessibility, best practices and SEO all get scored too.
Best for: developers and technically confident business owners doing a quick, thorough check. Cost: free, built into every Chrome browser. What it measures: performance, accessibility, best practices and SEO, all from a single simulated test run.
Lighthouse is a great companion to a broader technical review — see our website speed audit checklist for a step-by-step process that uses it alongside other checks.
GTmetrix: Deeper Diagnosis and History Over Time
GTmetrix takes things a step further. It runs your site from real servers in locations around the world, produces a detailed waterfall chart showing every file your page loads and how long each one took, and — crucially — lets you track your scores over time if you create a free account.
That historical tracking is genuinely useful. Instead of a single snapshot, you can see a graph of your load time over the past weeks and instantly spot the day a plugin update or a new banner image made things worse.
Best for: business owners who want more detail than PageSpeed Insights gives, and developers diagnosing a specific slow page. Cost: free tier available; paid plans unlock more test locations, more frequent monitoring and video capture. What it measures: load time, total page size, number of requests, a waterfall breakdown, and historical trend graphs.
WebPageTest: The Advanced Option for Developers
WebPageTest is the most powerful tool on this list and, honestly, overkill for most small business owners. It's built for developers who need to test from very specific global locations — say, simulating a visitor in Perth versus one in London — on specific browsers and connection speeds, then compare the results side by side.
Its standout feature is the filmstrip view: a frame-by-frame series of screenshots showing exactly what a visitor sees as your page loads, second by second. This is brilliant for spotting layout shift or a slow-loading hero image that PageSpeed Insights might only summarise as a number.
Best for: developers and agencies doing detailed performance work, or diagnosing issues for visitors in specific regions. Cost: free for public tests, with private/paid instances available for teams. What it measures: granular waterfall data, filmstrip and video playback of page load, multi-location and multi-browser comparisons.
Comparing the Tools at a Glance
| Tool | Best For | Cost | Standout Feature |
|---|---|---|---|
| Google PageSpeed Insights | Business owners wanting a quick, credible check | Free | Real-world (field) data plus Core Web Vitals scoring |
| Lighthouse (Chrome DevTools) | Developers and confident owners doing a technical check | Free | Scores performance, accessibility, SEO and best practices together |
| GTmetrix | Diagnosing issues and tracking progress over time | Free tier, paid plans available | Waterfall charts and historical trend tracking |
| WebPageTest | Developers needing advanced, location-specific testing | Free (paid for private instances) | Filmstrip view showing exactly how a page renders |
You could also try Pingdom Website Speed Test, another free option with a clean, simple report — handy as a quick second opinion if a result from another tool surprises you.
Making Sense of the Results
Every one of these tools will hand you a wall of numbers, and it's easy to get lost. Focus on three things first:
- Your Core Web Vitals status — pass, needs improvement, or fail. This is what Google actually uses as a ranking signal, and it's also visible over time in Google Search Console's Core Web Vitals report, which is worth checking alongside any of the tools above.
- The top two or three recommendations — most tools rank their suggestions by potential impact. Fix those first rather than chasing every minor warning.
- Mobile before desktop — most Australian visitors are browsing on their phone, and mobile scores are almost always worse than desktop. Our mobile speed optimisation guide covers the fixes that matter most here.
If your site runs on WordPress, a slow score is very often traceable to a handful of common causes — an overloaded plugin list, unoptimised images or a budget host. Our guide to speeding up a WordPress website and our rundown of common website speed mistakes both cover the usual suspects.
A Real-World Example
A Launceston accounting firm had been on a cheap shared hosting plan for years and suspected it was costing them enquiries during tax season, when their site got busiest. Before switching providers, they ran their homepage and a service page through PageSpeed Insights and noted the scores and load times.
After moving to a better host, they ran the same two pages through the same tool again. The improvement was clear enough in the before-and-after scores that it justified the extra monthly hosting cost — no guesswork required, just a simple test run twice. That's the real value of these tools: not the score itself, but being able to prove whether a change actually worked.
How Often Should You Test
You don't need to test daily, but a few checkpoints make sense:
- Before and after any major change — a new theme, a hosting switch, a redesign, or adding a new marketing script.
- Quarterly, as a general health check, even if nothing obvious has changed.
- Whenever a page feels slow to you or a customer mentions it.
- After adding new plugins or third-party embeds like booking widgets, chat tools or review carousels — these are common culprits for sudden slowdowns.
If you're not sure where your site currently stands, running through a website speed audit checklist once gives you a baseline to test against every time after that. And if your scores aren't moving despite your best efforts, our guide on achieving a 90+ PageSpeed score covers the fixes that tend to make the biggest difference.
Key Takeaways
- Google PageSpeed Insights is the best starting point for non-technical business owners — free, credible and Core Web Vitals-focused.
- Lighthouse in Chrome DevTools gives the same lab data plus accessibility and SEO scoring, ideal for a quick technical check.
- GTmetrix adds waterfall charts and historical tracking, useful for diagnosing and monitoring progress.
- WebPageTest is the most advanced option, built for developers needing location-specific, frame-by-frame detail.
- Test before and after any major site change, and periodically even when nothing's changed.
Frequently Asked Questions
Which website speed testing tool should I use first?
Start with Google PageSpeed Insights. It's free, takes seconds, and gives you the same Core Web Vitals data Google uses when assessing your site, so you know you're looking at what actually matters.
Do these tools give different scores for the same page?
Yes, and that's normal. Each tool tests from different servers, at different moments, with slightly different methods, so scores will vary a little. Focus on the trend and the recommendations rather than chasing an exact number.
Is GTmetrix better than PageSpeed Insights?
They're better at different things. PageSpeed Insights is quicker and includes real-world field data; GTmetrix gives you a more detailed waterfall breakdown and lets you track scores over time with a free account.
Do I need to understand code to use these tools?
Not for PageSpeed Insights or GTmetrix's summary reports — the top-level scores and recommendations are written in plain enough language. WebPageTest and the deeper Lighthouse detail are more useful once you (or your developer) understand terms like render-blocking scripts and time to first byte.
Why does my mobile score look so much worse than desktop?
Mobile devices generally have less processing power and often slower connections, so the same page takes longer to become interactive. This is normal, but it means mobile performance deserves extra attention since most visitors arrive on a phone.
How often should a small business test its website speed?
Test after any meaningful change — new host, new theme, new plugins — and do a general check every few months even if nothing's changed, since speed can drift as content and scripts accumulate.
Can a slow score actually hurt my Google rankings?
Core Web Vitals are one of many ranking signals Google uses, and a genuinely poor experience can work against you, especially against competitors with faster sites. It's rarely the single biggest ranking factor, but it's one you can control directly, so it's worth fixing.
What's the difference between lab data and field data?
Lab data is a simulated test run at a single moment, which is what Lighthouse and GTmetrix primarily show. Field data is aggregated from real visitors over the past 28 days, which is what powers the Chrome UX Report portion of PageSpeed Insights and Search Console. Both are useful; field data reflects reality, lab data is easier to reproduce and debug.
Get a Website That Tests Well and Performs Even Better
Running your site through these tools is a great habit, but acting on what they tell you is where the real improvement happens. If your scores keep coming back disappointing no matter what you try, or you'd simply rather have someone who understands this properly handle it, have a chat with Pixel and Pine. We build and maintain sites that pass these tests comfortably, not just scrape by.
