FREE WEBSITE SPEED TEST

Website speed test: how fast does your site load?

Enter your URL to run a website speed test on mobile. You see the Core Web Vitals that Google measures, and where your page loses time.

WHAT THE TEST MEASURES

Core Web Vitals

This speed test loads your page the way a phone does and measures how long it takes before the page is on screen and responds. Of the three Core Web Vitals, the test measures LCP and CLS directly. For the third, INP, it looks at TBT.

The test simulates an average phone on slow 4G. Visitors with a faster phone or Wi-Fi often experience your site as faster than this score shows. If your page scores well on this strict measurement, it also loads quickly on a slow connection.

  • Speed score

    Overall score based on all the measurements

  • Main content on screen (LCP)

    How fast the largest element appears on screen

  • First content on screen (FCP)

    When something first appears on screen

  • Response to taps (TBT)

    How long the page doesn't respond to a tap or click

  • Layout stability (CLS)

    How much elements shift around while the page loads

  • Page size

    Total size of the page in KB/MB

LAB AND REAL WORLD

The test is a lab measurement

How the lab test works

  • A measurement on simulated slow 4G
  • An average phone
  • The same conditions every time
  • Useful for tracking down technical problems

What the test doesn't measure

  • Measurements from your real visitors
  • Differences by location and network
  • How visitors experience the speed
  • The effect of caching on a second visit

Besides LCP and CLS, the test measures FCP, TBT and an overall speed score. If your site gets enough traffic, Google also measures speed with real visitors. You'll find those numbers in Google Search Console, under Core Web Vitals.

YOUR SCORE

What does your score mean?

A score of 90+ is good. Between 50 and 89, there's room to speed up. Under 50, something is seriously in the way, usually one of the four causes further down this page.

Compare your score with others in your industry

A simple business site can reach 90 or higher, even on this strict measurement. A large online store or web app naturally scores lower, because a lot more code loads along with it. So compare your score with competitors in the same industry.

Speed is one of the signals Google looks at for SEO. Your content, your backlinks and how visitors behave on your site count too. So a perfect score won't automatically move you up in Google, but your visitors do notice a slow site right away.

GOOGLE'S THRESHOLDS

What is a good load time?

For a good load time, Google uses three thresholds, the Core Web Vitals. Stay below them and you're fine. Go above them, and you see right away which of the three needs attention.

LCPunder 2.5 s = good

The load time of the largest element on your screen, often the hero image or the headline. That's how long it takes before your visitor feels the page is there.

INPunder 200 ms = good

How fast your page responds when someone clicks or taps something. If that takes too long, the site feels slow, even when everything is already on screen.

CLSunder 0.1 = good

How much the page jumps around while it loads. A button that moves just as you want to click it: that's a high CLS.

INP can only be measured when real visitors tap and click on your page. This test runs without visitors, so it looks at TBT, the time the page doesn't respond. TBT is a good predictor: if it's high, your INP with real visitors is usually too slow as well.

CAUSES

Why is your website slow?

It usually comes down to a few familiar causes. These four are the ones I run into most often, and under each cause you'll find where to look for the fix.

Images that are too heavy

Photos of a few megabytes are the biggest slowdown, so that's usually where there's the most to gain.

Compress them and convert them to WebP or AVIF, at the size they're actually displayed at.

Too many scripts

Every plugin, tracker and widget loads code that blocks the page before it's ready.

Remove what you don't use and defer the rest until the page has loaded.

Slow hosting

On cheap, overcrowded servers it simply takes longer for the first byte to arrive.

Choose a faster host, or a setup that serves your pages from a server close to your visitors.

No caching

Without caching, your site rebuilds every page on every visit, even when nothing has changed.

Turn on browser and server caching, so returning visitors don't have to download everything again.

If your site runs on WordPress, the right technical optimization often gets you a lot more speed.

FREQUENTLY ASKED QUESTIONS

FAQ about website speed

Google uses three thresholds, the Core Web Vitals. LCP under 2.5 seconds is good: that is the load time of the largest element on your screen. INP under 200 milliseconds is good: that is how fast your page responds to a click or tap. And CLS under 0.1 is good: that means very little shifts around while the page loads. This test measures with lab data and shows TBT instead of INP, but a low TBT points to a good INP.

Core Web Vitals are three measurements Google uses to assess user experience: LCP (how fast the content appears), CLS (how much the page shifts while it loads) and INP (how fast the page responds to a click or tap). This test measures TBT instead of INP, because INP can only be measured with real visitors. If your TBT is high, your INP is usually too slow as well.

It usually comes down to a few familiar things: images that are too heavy and not optimized, too many scripts and trackers that hold up the page, slow hosting, or no caching, so everything gets rebuilt on every visit. Often the biggest gain is in the images.

Start with your images: convert them to WebP and load them at the size they're displayed at. After that, it helps to load less JavaScript and defer the rest, turn on caching and choose a fast host. If your site runs on WordPress, keep the number of plugins small and pick a lightweight theme.

Yes, speed carries weight in Google through the Core Web Vitals. Still, a fast site doesn't shoot up on its own, because content, relevance and backlinks weigh more. Speed mostly counts indirectly: a slow site drives visitors away, and Google sees that.

Lab data is measured under simulated conditions: an average phone on slow 4G. Field data comes from real measurements of visitors who use Chrome. This test works with lab data, under deliberately strict conditions. That is why visitors with a faster phone or Wi-Fi often experience your site as faster than the test score suggests.

Yes, usually. This test measures on mobile, because Google assesses your site based on the mobile version. A phone has less processing power than a desktop, so sites with a lot of JavaScript in particular score lower. Visitors on their phones notice that difference too.

Lab measurements fluctuate a little because of server load, the network and caching. A few points of difference between two runs is normal. Run the test a few times and look at the average, which tells you more than a single measurement.

Under 50, your page can get a lot faster, though it depends on the type of website. A simple business site should score higher. A web app with lots of buttons and features naturally scores lower. So look mainly at how sites in your own industry score.

VIZIBLY QUICK SCAN

Website too slow?

I build my websites for speed from the first line of code, so they load quickly on a phone too. Request the free Quick Scan, and I'll look at your site and your market and point out where your site is slow and where you're missing out on clients.

Prefer to talk first? Schedule a call.

Request the free Quick Scan

Two short steps. It takes less than a minute.

Step 1 of 2

A few short questions follow. You can leave them blank.