- Home
- Free tools
- Website speed test
Website speed test
Enter a page address and we load it in headless Chrome with Google Lighthouse, on a throttled mobile connection or on desktop. You get a performance score, the Core Web Vitals lab metrics, and a short list of what to fix first.
How to use it
- Type the page address (one page, not a whole site) and choose Mobile or Desktop. Mobile is the stricter test and the one most visitors experience.
- Wait 20 to 60 seconds. The quick checks appear first, then the Lighthouse results.
- Start with the opportunities at the top: they are sorted by estimated time saved. Re-run after each change to confirm it helped.
What it checks
- Performance score from Google Lighthouse
- Largest Contentful Paint, Cumulative Layout Shift and Total Blocking Time
- First Contentful Paint and Speed Index
- Biggest opportunities: images, scripts, render-blocking files, caching, compression
- Page weight and request count
- HTTPS, compression and server response time
- A share link, plus print and JSON export
Limits
- A single Lighthouse run from our server with simulated throttling. Scores vary between runs and differ from your visitors' real experience.
- Tests the page URL only. Pages behind a login, or that need interaction to load content, are not fully measured.
- Results are cached for a short time, so a repeat test of the same page may return the same report.
Public pages only, one page at one point in time. See the methodology and terms.
How to read the numbers
Lighthouse reports lab metrics. Google's published thresholds for a "good" result are below. They are the same bands the report colours.
| Metric | Good | Needs work | Poor |
|---|---|---|---|
| Largest Contentful Paint (LCP) | up to 2.5 s | 2.5 to 4 s | over 4 s |
| Cumulative Layout Shift (CLS) | up to 0.1 | 0.1 to 0.25 | over 0.25 |
| Total Blocking Time (TBT, lab stand-in for INP) | up to 200 ms | 200 to 600 ms | over 600 ms |
| First Contentful Paint (FCP) | up to 1.8 s | 1.8 to 3 s | over 3 s |
Lab data comes from one test location on one simulated device, so it will differ a little between runs and from what your visitors measure in the field. Use it to find problems and compare before and after, not as a promise about every visitor's experience.
Frequently asked questions
How do I test my website speed?
Enter the page address above, pick Mobile or Desktop and run the test. Test the pages that matter most (home page, a product or article page), because speed differs between pages.
Why is my mobile score lower than desktop?
Mobile tests simulate a mid-range phone on a slow 4G connection, so the same page has to download and run much more slowly. Mobile is the one to optimise first.
Why do I get a different score every time?
Lab tests depend on server load, network noise and caching. A difference of a few points between runs is normal. Run it two or three times and look at the trend.
What is a good website speed?
Aim for an LCP of 2.5 seconds or less, a CLS of 0.1 or less, and a Total Blocking Time under 200 ms. A performance score of 90 or more is good, 50 to 89 needs work.
Is this the same as Google PageSpeed Insights?
Both use Lighthouse for the lab part. PageSpeed Insights also shows field data from Chrome users when a site has enough traffic. This tool shows lab data only and runs on our own server, so numbers can differ.
What does the test not cover?
Pages behind a login, other pages of the site, and real-user (field) performance. Each run tests one public page.