How to Check Website Speed: 5 Free Tools and What the Numbers Mean (2026)

If you want to know how to check website speed, start with a simple fact: there is no single number that tells you how fast your site is. A speed test gives you several numbers, and each one measures something different. This guide shows you how to run the tests, what the numbers mean, and what to do about them — using free tools only.

You do not need any technical background. By the end, you will be able to test any page on your site, read the results without guessing, and know which problems are worth fixing first.

What “Website Speed” Really Means

When people say a site is slow, they usually mean one of three things. The main content took too long to appear. The page felt unresponsive when they tried to tap or click something. Or the layout jumped around while it loaded, so they tapped the wrong thing. Google measures exactly these three experiences with its Core Web Vitals, which we will explain below.

That is why two tools can give you different results for the same page, and why a page can feel fast to you but slow to a visitor on a cheaper phone and a weaker connection. A good speed check looks at the experience of a real visitor, not just one test on your own computer.

Before You Test: Pick the Right Pages

Do not test only your homepage. Your homepage is often the lightest page on your site, and it is not always the page that brings in customers. Test the pages that matter most to your business:

• Your homepage
• Your most visited service or product page
• Your most visited blog post or landing page
• Your contact or checkout page, if you have one

Write down the results and the date for each page. Without a baseline, you cannot tell whether a change you made later actually helped. Test each page twice and use the second result if the first looks odd — a single test can be thrown off by a slow moment on your connection.

Tool 1: Google PageSpeed Insights (Start Here)

PageSpeed Insights is Google’s own free speed test, and it is the best place to start. You do not need an account. Go to the site, paste the full address of the page you want to test, and click Analyze. It takes about half a minute.

Read the Mobile tab first, not the Desktop tab. Most visitors now come from phones, and Google ranks your site using the mobile version of your pages. A page that scores well on desktop but poorly on mobile still has a problem.

Field Data vs Lab Data

The report shows two kinds of data, and mixing them up is the most common beginner mistake.

Field data comes from real Chrome users who visited your page over the past 28 days. This is what visitors actually experienced, and it is what Google uses for ranking. If your page does not get much traffic, this section may be empty — that is normal for a new or small site.

Lab data comes from a simulated test run in a controlled environment. It is useful because it can be repeated and broken down into specific problems to fix. But it is one simulated visit, not your real visitors. Use field data to decide which pages to fix, and lab data to find out why a page is slow.

The 0–100 Performance Score

The big number at the top is the lab score: 90 or above is good, 50 to 89 needs improvement, and below 50 is poor. Treat it as a rough guide, not a grade. A score of 85 with good Core Web Vitals is fine. Chasing a perfect 100 can waste weeks for no real benefit to your visitors, and some pages — especially shops with lots of images — will rarely reach it.

Tool 2: GTmetrix (A Second Opinion)

GTmetrix is a free tool that also tests your page and shows how it loads, step by step. You can run a basic test without an account. It gives you a performance score, a structure score, and a waterfall chart — a timeline showing each file your page loads, in order, and how long each one took.

The waterfall chart is where GTmetrix earns its place. If one huge image or one slow script is holding everything up, you will see it as a long bar near the top of the chart. That tells you exactly what to fix first, instead of guessing.

Do not panic if GTmetrix and PageSpeed Insights disagree. They test from different locations, on different simulated devices, and they weight things differently. If both tools flag the same problem — for example, oversized images — that problem is real. If only one tool complains about something small, it is probably not your top priority.

Tool 3: WebPageTest (The Detailed View)

WebPageTest is a free, more advanced tool. It lets you pick the test location, the device, and the connection speed — for example, a mid-range phone on a slower mobile connection. That matters if your customers are not all on fast city connections.

WebPageTest also shows a filmstrip: screenshots of your page as it loads, second by second. This is the closest thing to watching a real visitor’s experience. If your page looks blank for three seconds and then everything appears at once, the filmstrip shows you that plainly, even if the final score looks fine.

You do not need WebPageTest for every page. Use it when PageSpeed Insights and GTmetrix disagree, or when you have fixed a problem and want to confirm the improvement under realistic conditions.

Tool 4: Google Search Console (The Whole Site at Once)

Testing one page at a time is fine, but it does not tell you whether a problem affects ten pages or a thousand. That is what the Core Web Vitals report in Google Search Console is for. It groups your site’s pages into good, needs improvement, and poor, so you can see whether a problem is limited to one template — like all your product pages — or spread across the whole site.

Search Console is free, but you need to verify that you own the site first. If you have not set it up yet, do it before you need it: its field data covers a rolling 28-day window, so it takes weeks to build up after you fix something. A fix you make today will not show as improved in Search Console tomorrow, and that is normal.

Tool 5: Your Own Phone (The Test Most People Skip)

After all the tools, do the simplest test of all: open the page on a real phone, on a mobile connection rather than Wi-Fi, and watch it load. Can you read the headline within about three seconds? Can you tap the main button without the layout jumping? Does anything important stay hidden or broken?

This test catches problems the tools miss, like a pop-up that covers the whole screen on a small phone, or a button that is too close to another link to tap reliably. It also reminds you what your visitors actually feel, which is easy to forget when you are staring at scores.

What the Numbers Mean: Core Web Vitals Explained

These are the three numbers that matter most. Google judges each one at the 75th percentile of real visits — in plain terms, at least three out of four visits must be good for the page to pass. A page must pass all three at once.

LCP is the closest thing to the old idea of “load time.” It measures when the largest piece of content in view — usually a hero image or a big heading — appears. INP replaced an older metric called First Input Delay in March 2024, and it looks at responsiveness across the whole visit, not just the first tap. CLS measures visual stability: you have felt a bad CLS score when you went to tap a link and an ad or banner pushed it out of the way at the last second.

Two other numbers show up in most reports and are worth knowing. Time to First Byte (TTFB) shows how long your server takes to start responding; under about 0.8 seconds is a sensible target. First Contentful Paint (FCP) marks the first text or image on screen, with 1.8 seconds or less counted as good. If TTFB is slow, the problem is usually your hosting or server setup. If LCP is slow but TTFB is fine, the problem is usually something on the page itself, like a huge image.

Why Your Score Changes Between Tests

If you test the same page three times and get three different scores, nothing is broken. Lab tests vary with server load, network conditions, and even ads that load differently each time. Field data changes as your real visitors change. A score that moves by a few points between tests is noise. A score that moves by twenty points, or a metric that crosses from good to poor, is worth looking into.

That is also why you should test the same way each time: same tool, same page, same device setting. Changing tools mid-way makes it impossible to tell whether the page improved or the test just changed.

What to Fix First

A speed report can list twenty suggestions. Fix them in this order, because the first few usually account for most of the improvement:

1. Shrink oversized images. Resize them to the size they actually appear at, and compress them. This is the single most common speed problem on small business sites.
2. Remove plugins, scripts, and pop-ups you do not need. Every extra script is something the visitor’s phone must download and run.
3. Fix layout shift: give images and ads a set width and height so the page does not jump as they load.
4. Turn on caching if your host or platform offers it, so returning visitors do not re-download everything.
5. Only then, look at deeper fixes like server response time or switching hosts. Those cost money and effort, so rule out the free fixes first.

After each round of fixes, retest the same pages the same way, and write down the new numbers next to the old ones. Judge the change over a week or two, not a single test.

Mistakes That Waste Your Time

• Testing only the homepage and assuming the rest of the site is fine.
• Chasing a perfect 100 score while real visitors would already call the page fast.
• Reading only the desktop score when most of your visitors are on phones.
• Treating one bad test as a crisis. Retest before you change anything.
• Fixing five things at once. You will never know which one actually helped.
• Ignoring field data. A great lab score does not help if real visitors on real phones still wait.

How Often Should You Check Your Website Speed?

For most small sites, a quick check once a month is enough, plus a check after any big change: a redesign, a new theme, new plugins, or a batch of new images. If you run a shop, check your top product and checkout pages before busy periods, not during them. Set a simple routine: same pages, same tool, same device setting, results written down with the date. That routine is worth more than any single score.

Frequently Asked Questions

What is a good website speed?

A page that shows its main content in 2.5 seconds or less, responds to taps within 200 milliseconds, and does not jump around while loading. Those are Google’s good thresholds for Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift. A page that meets all three in real visitor data is in good shape.

Do I need a PageSpeed score of 100?

No. The score is a lab measurement, not a pass-or-fail grade. A score of 90 or above is good, 50 to 89 needs improvement, and below 50 is poor — but a page scoring 85 with good Core Web Vitals serves visitors well. Spend your time on the real problems the report lists, not on squeezing out the last few points.

Why is my mobile score lower than my desktop score?

Because the mobile test simulates a mid-range phone on a slower connection, while the desktop test simulates a fast computer. Phones have less processing power and often weaker connections, so the same page takes longer. Since most visitors and Google’s ranking use the mobile version, the mobile score is the one to fix first.

Why do PageSpeed Insights and GTmetrix give different scores?

They test from different locations, on different simulated devices, and they weight their measurements differently. They also test at different moments, so network conditions differ. If both tools flag the same problem, fix that problem. Small differences between the tools are normal.

Is website speed a Google ranking factor?

Yes, page experience — including Core Web Vitals — is one of many ranking signals, but it is not the most important one. A fast page with thin or unhelpful content will not outrank a slower page that answers the search properly. Speed matters most when it is bad enough to drive visitors away.

How long does it take for a speed fix to show up?

Lab tests show the improvement as soon as you retest. Field data in PageSpeed Insights and Search Console takes longer, because it covers real visits over a rolling 28-day window. Give a fix two to four weeks before judging it on field data.

Start today with one page: run it through PageSpeed Insights on mobile, write down its LCP, INP, and CLS numbers, and check whether the biggest problem is an image you can shrink. That one check tells you more about your site’s speed than any score on its own.

Last updated: November 2026