Top 9 Free Page Speed Test Tools I Actually Use (+ Tips to Fix Slow Pages)

A client once told me their new WordPress site was “lightning fast.” On their office fibre connection, it was. Then I ran it through a mobile speed test simulating an average phone on a 4G network, and the main content took almost seven seconds to appear. Their bounce rate suddenly made a lot more sense.

That’s the trap with page speed: your own experience is almost never your visitors’ experience. The only way to know how fast a page really is, is to test it properly, with the right tools. The good news is that the best free page speed test tools are genuinely excellent, and you don’t need a paid subscription to diagnose most problems.

Below are the nine tools I rely on, what each one is best at, and the specific tips I use to turn their reports into a faster site. If you’re also cleaning up the rest of your technical SEO, pair this with our guide to free website crawlers and site audit tools.

Why Page Speed Still Matters for SEO in 2026

Speed affects two things you care about: rankings and revenue. Google uses page experience signals, including Core Web Vitals, as part of how it evaluates pages. Speed isn’t going to outrank great content on its own, but when two pages are similarly helpful, the faster one has an edge.

The bigger impact is on people. Slow pages lose visitors before they ever read a word. Every extra second of waiting is another chance for someone to hit the back button.

The three Core Web Vitals in plain English

• Largest Contentful Paint (LCP): how long until the main content (usually a hero image or headline) appears. Aim for 2.5 seconds or less.
• Interaction to Next Paint (INP): how quickly the page responds when someone taps or clicks. Aim for 200 milliseconds or less. INP replaced First Input Delay as a Core Web Vital in 2024.
• Cumulative Layout Shift (CLS): how much the layout jumps around while loading. Aim for 0.1 or less.

Google explains the thresholds in detail in its official Web Vitals documentation, which is worth bookmarking if you work on site performance regularly.

Lab data vs field data (this confuses everyone)

Speed tools report two kinds of data, and mixing them up leads to bad decisions:

• Lab data comes from a simulated test run right now, on a set device and connection. It’s great for debugging because it’s repeatable.
• Field data comes from real Chrome users visiting your site over the past 28 days. It’s what Google actually uses for Core Web Vitals assessment.

A page can score well in the lab and still fail in the field, or the other way round. The best workflow uses both.

Quick Comparison: The 9 Best Free Page Speed Test Tools

Tool	Best for	Field data?	Account needed?
Google PageSpeed Insights	Quick SEO check + Core Web Vitals	Yes	No
Google Search Console (CWV report)	Site-wide Core Web Vitals issues	Yes	Yes (site verification)
Lighthouse (Chrome DevTools)	Detailed debugging on your own machine	No	No
GTmetrix	Visual waterfall + easy reports	No	Optional
WebPageTest	Advanced testing, filmstrips, real devices	No	Optional
Pingdom Website Speed Test	Simple load time + request breakdown	No	No
DebugBear Free Test	Clear Core Web Vitals breakdown	Yes (via CrUX)	No
Chrome DevTools Performance panel	Fixing slow interactions (INP)	No	No
Chrome UX Report (CrUX) tools	Real-user trends over time	Yes	No

1. Google PageSpeed Insights — The Starting Point

If you only use one tool, make it this one. PageSpeed Insights runs a Lighthouse lab test and, when your page gets enough traffic, shows real-user field data from the Chrome UX Report at the top of the results.

What I like

• Shows lab and field data side by side.
• Separate mobile and desktop results.
• A prioritised list of “Opportunities” and “Diagnostics.”

Pro tip

Always look at the field data box first. If it says “Passed,” your real users are having a decent experience, even if the lab score is lower than you’d like. Don’t chase a perfect 100 at the expense of features your visitors actually use.

2. Google Search Console Core Web Vitals Report — The Big Picture

PageSpeed Insights tests one URL at a time. The Core Web Vitals report in Search Console groups similar URLs together and tells you which groups are “Poor,” “Need improvement,” or “Good” based on real-user data.

What I like

• Shows problems across the whole site, not just one page.
• Groups URLs by template, so one fix can solve hundreds of pages.
• Lets you validate a fix and track whether it worked.

Pro tip

Click into a “Poor” group, take one example URL, and run it through PageSpeed Insights. Fix the template, not the individual page. If you haven’t connected your site yet, our Google Search Console setup guide walks you through it.

3. Lighthouse in Chrome DevTools — For Hands-On Debugging

Lighthouse is the engine behind PageSpeed Insights, and it’s built right into Chrome. Open DevTools, choose the Lighthouse tab, and run an audit locally.

What I like

• Test pages behind a login or on a staging site that public tools can’t reach.
• Audits accessibility, SEO and best practices at the same time.
• Instant re-tests while you make changes.

Pro tip

Run Lighthouse in an Incognito window. Browser extensions can add scripts to the page and quietly drag your score down, giving you a misleading result.

4. GTmetrix — The Most Beginner-Friendly Waterfall

GTmetrix is a favourite with bloggers and agencies because its reports are easy to read and easy to share with clients. Its waterfall chart shows every file the page loads, in order, and how long each one takes.

What I like

• Clear grades and a structured report.
• A detailed request waterfall for spotting heavy files.
• A free account adds extra options such as saved test history.

Pro tip

Sort the waterfall by size. In almost every slow WordPress site I’ve audited, the culprits at the top are uncompressed images, a page builder’s bundled scripts, or a third-party chat widget.

5. WebPageTest — The Power User’s Tool

WebPageTest is the tool performance engineers reach for when they need detail. It lets you choose test locations, browsers, and connection speeds, and its filmstrip view shows exactly what a visitor sees, frame by frame.

What I like

• Filmstrip and video comparisons between two pages.
• Repeat views to measure caching.
• Highly configurable connection throttling.

Pro tip

Run a side-by-side comparison of your page against a competitor’s. Seeing your hero image appear a full second later than theirs is far more persuasive to a client or boss than any score.

6. Pingdom Website Speed Test — Simple and Fast

Pingdom’s free speed test gives you a quick load time, page size, and request count, plus a breakdown of content by type. It’s not as deep as WebPageTest, but it’s quick and readable.

What I like

• Simple summary ideal for quick checks.
• Breakdown of requests by content type and domain.
• Choice of test locations.

Pro tip

Check the “requests by domain” section. A long list of third-party domains (ad networks, trackers, fonts, widgets) is often the hidden reason a page feels sluggish.

7. DebugBear Free Website Speed Test — Clearest Core Web Vitals Breakdown

DebugBear offers a free test that combines lab results with Chrome UX Report data, presented in a way many people find easier to understand than raw Lighthouse output.

What I like

• Breaks LCP into sub-parts, so you can see whether the delay is the server, the image download, or rendering.
• Clear explanation of what each recommendation means.
• Real-user data where available.

Pro tip

Look at the LCP breakdown before you start optimising images. If most of the delay is “Time to First Byte,” your problem is hosting or caching, and compressing images won’t fix it.

8. Chrome DevTools Performance Panel — The INP Fixer

Interaction to Next Paint is the hardest Core Web Vital to fix, because it’s about JavaScript running when people click. The Performance panel in Chrome DevTools records exactly what happens during an interaction.

What I like

• Shows long tasks that block the page from responding.
• Identifies which script is responsible.
• Can show live Core Web Vitals as you interact with the page.

Pro tip

Turn on CPU throttling (4x or 6x slowdown) before recording. Your laptop is far more powerful than the average phone, and throttling exposes problems you’d otherwise never see.

9. Chrome UX Report (CrUX) Tools — Real-User Trends

The Chrome UX Report is the public dataset of real-user performance that powers field data in Google’s tools. Google offers free ways to explore it, including a dashboard view, so you can see how your site’s Core Web Vitals have changed month by month.

What I like

• Long-term trends rather than one-off snapshots.
• Compare your origin against competitors.
• Based on real Chrome users, not simulations.

Pro tip

Check CrUX data before and after a big change like a redesign or theme switch. It’s the most honest answer to “Did that actually help our users?”

How to Read a Waterfall Chart Without Getting Lost

The waterfall chart in GTmetrix, WebPageTest or Pingdom is the single most useful thing these tools show, and also the most intimidating. Each row is one file the browser downloads; each bar shows when that download started and how long it took. Here’s how I read one in under five minutes:

1. Look at the very first row. That’s your HTML document. If its bar is long before anything else starts, your server is slow to respond. That’s a hosting or caching issue.
2. Find the long bars. The widest bars are the slowest files. Hover over them to see the file name and size.
3. Spot render-blocking files. CSS and JavaScript loaded early in the head can stop the page from displaying until they finish. Many tools mark these clearly.
4. Count the third-party domains. Rows from ad networks, analytics, fonts, and widgets add up fast.
5. Locate your LCP element. Find the hero image or main font and check how late in the list it starts downloading. The later it starts, the slower your LCP.

Once you’ve done this a few times, you’ll start recognising patterns instantly, such as a giant uncompressed hero image or a slider plugin loading five scripts on pages that don’t even use it.

A Real Example: Taking a Slow Blog Post From “Poor” to “Good”

To show how these tools work together, here’s a simplified version of a fix I did on a content site running WordPress with a popular page builder.

The problem

Search Console flagged a group of blog posts as “Poor” for LCP on mobile. PageSpeed Insights field data for one example post showed LCP well above the 2.5-second target, and the lab test agreed.

The diagnosis

• DebugBear’s LCP breakdown showed server response was fine, but the hero image started downloading very late.
• The GTmetrix waterfall revealed why: the hero image was lazy-loaded, it was a 1.8 MB JPEG, and it only began loading after several page builder scripts finished.
• Pingdom’s domain breakdown showed a social sharing plugin pulling in scripts from four external domains.

The fix

1. Excluded the featured image from lazy-loading and added a preload hint.
2. Converted featured images to WebP and resized them to their real display width.
3. Replaced the social sharing plugin with lightweight static share links.
4. Enabled page caching and a CDN.

The result

The lab LCP dropped dramatically on the next test, and over the following few weeks the field data in Search Console moved the whole group of URLs into “Good.” Fixing the post template meant every blog post improved at once, not just the one I tested.

Extra Notes for WordPress Sites

Most seostackhub readers run WordPress, so a few platform-specific points are worth knowing:

• Test with your caching plugin active, but also check the uncached response time. A cache can hide a slow server that hurts first-time visitors and logged-in users.
• Watch your theme and page builder. Heavy builders can load large CSS and JavaScript files on every page. Many now offer settings to load assets only where they’re used.
• Be careful with “optimisation” plugins. Combining or deferring scripts can break features. Change one setting at a time and re-test.
• Keep your plugin count lean. It isn’t the number of plugins that matters so much as what each one loads on the front end. Use the waterfall to see which ones actually cost you.
• Check your SEO plugin’s output too. Well-built SEO plugins add very little front-end weight, but duplicated features across several plugins can add up.

Which Free Page Speed Test Tool Should You Use?

You don’t need all nine every time. Here’s the simple workflow I follow:

1. Start with Search Console to find which page groups have problems.
2. Run PageSpeed Insights on one example URL from each problem group.
3. Use GTmetrix or WebPageTest to see the waterfall and find heavy or slow files.
4. Use DebugBear’s LCP breakdown to confirm where the delay really comes from.
5. Open the DevTools Performance panel if INP is the problem.
6. Watch CrUX trends over the following weeks to confirm real users benefit.

9 Practical Tips to Fix a Slow Page

Testing is only half the job. Here are the fixes I apply most often, roughly in order of how much difference they make:

1. Compress and resize images. Serve images at the size they’re displayed and use modern formats like WebP or AVIF. Our list of image compressor tools for SEO covers the best free options.
2. Don’t lazy-load your hero image. Lazy-loading is great below the fold, but applying it to the main above-the-fold image delays LCP.
3. Preload the LCP image so the browser fetches it early.
4. Use page caching and a CDN. This cuts server response time, especially for visitors far from your host.
5. Upgrade weak hosting. If Time to First Byte is consistently slow, no front-end tweak will fully fix it.
6. Remove unused plugins and scripts. Each one can add CSS and JavaScript to every page.
7. Delay or limit third-party scripts like chat widgets, heatmaps and social embeds until they’re needed.
8. Reserve space for images, ads and embeds with width and height attributes to stop layout shifts (CLS).
9. Break up long JavaScript tasks to improve INP, and avoid heavy work on every click.

Common Mistakes When Testing Page Speed

• Testing only the homepage. Your blog posts and product pages often get more traffic and may be slower.
• Testing only on desktop. Google primarily uses the mobile version of your site, and mobile results are usually worse.
• Trusting one test run. Lab results vary. Run a test three times and look at the typical result.
• Obsessing over the score. The 0–100 score is a summary. Core Web Vitals and real-user data matter more.
• Comparing different tools’ numbers directly. Each tool uses different devices, locations and settings, so their numbers won’t match exactly.

Frequently Asked Questions

What is the best free page speed test tool?

For most people, Google PageSpeed Insights is the best starting point because it combines a Lighthouse lab test with real-user Core Web Vitals data. Add GTmetrix or WebPageTest when you need a detailed waterfall.

Why do different speed test tools show different results?

Each tool tests from different locations, with different simulated devices and network speeds. Use one tool consistently to track progress over time rather than comparing numbers across tools.

What is a good PageSpeed Insights score?

A score of 90 or above is considered good, but passing Core Web Vitals in the field data matters more for SEO than the score itself.

How often should I test my website speed?

Test after any significant change, such as installing a plugin, switching themes, or adding a new script, and check Search Console’s Core Web Vitals report at least monthly.

Does page speed directly affect Google rankings?

Page experience, including Core Web Vitals, is one of many signals Google considers. It rarely outweighs relevance and content quality, but it can make a difference between similar pages and has a big impact on conversions. Google’s own Search Central guidance on Core Web Vitals explains how it fits in.

Final Thoughts

The best free page speed test tools give you everything you need to diagnose a slow site without spending a penny. Start with Search Console and PageSpeed Insights to find where real users are struggling, dig into the waterfall with GTmetrix or WebPageTest, and use DevTools when you need to get surgical.

Most importantly, test like your visitors browse: on mobile, on a normal connection, and on the pages that actually bring in traffic. Fix the biggest problems first, re-test, and watch your real-user data improve. A faster site isn’t just better for SEO. It’s better for every person who visits.