1. Home
  2. Guides
  3. How to test website speed
Performance guide

How to test your website's speed, step by step

Testing website speed takes a minute. Getting a useful answer takes a little more care: the right page, the right device, more than one run, and knowing which numbers to trust. This guide walks through it.

Key points

  • Test the pages that matter (home, a top landing page, a product or article), on mobile first, and run each two or three times.
  • Look at LCP, CLS and Total Blocking Time before the overall score. Aim for 2.5 s, 0.1 and 200 ms.
  • Fix the biggest opportunity first (usually images, scripts, or server response), then test again to confirm.

Test it in five steps

  1. Pick the page. Speed differs per page. Test the home page and the two or three pages that bring the most visitors or revenue.
  2. Choose mobile. Most visitors are on phones with slower processors and connections, and Google judges the mobile experience first. Test desktop second.
  3. Run the test. Use the website speed test: it loads the page in headless Chrome with Lighthouse and reports within a minute.
  4. Repeat. Run it two or three times. Lab results move a few points between runs because of network and server noise. Use the typical value, not the best one.
  5. Change one thing, retest. Fix the top opportunity, run the test again and keep a note of the score, so you know which change helped.

Which numbers matter

  • Largest Contentful Paint (LCP): when the main content appears. Good is 2.5 seconds or less.
  • Cumulative Layout Shift (CLS): how much the page jumps. Good is 0.1 or less.
  • Total Blocking Time (TBT): how long JavaScript blocks the page from responding. Good is 200 ms or less. It is the lab stand-in for Interaction to Next Paint.
  • The overall score is a weighted summary. 90 and above is good, 50 to 89 needs work, below 50 is poor. It is useful for tracking, but the individual metrics tell you what to fix.

Lab data and field data

Lab data is one controlled test on a simulated device and connection. It is repeatable and shows causes. Field data is what real visitors experienced, collected over weeks from Chrome users; it is what Google uses for ranking signals and it needs enough traffic. A lab test cannot see your visitors' real devices, networks or locations, so use it to find and fix problems, and Search Console or the Chrome UX Report to confirm real-world results.

What to fix first

  1. Heavy images. Resize to the displayed size, convert to WebP or AVIF, lazy-load below the fold, and preload the main hero image. The image checker lists the largest files.
  2. Slow server response. A first byte slower than about 600 ms delays everything. Use page caching, a CDN and a faster host. The HTTP header checker shows the time to first byte.
  3. No compression or caching. Turn on Brotli or gzip and set long cache lifetimes for static files. See compression and caching.
  4. Too much JavaScript. Remove unused libraries and trackers, defer the rest. Check the weight with the page weight checker.
  5. Layout shifts. Set width and height on images, embeds and ads.

Common mistakes

  • Testing only the home page.
  • Comparing a score from one tool with a score from another. Each runs on different hardware and settings.
  • Chasing a perfect 100. Past about 90 the user-visible gains are small.
  • Testing once, after a cache warm-up, and calling it done.
  • Ignoring mobile because the site feels fast on a fast laptop.

Want one report with speed, SEO, security headers and accessibility? Run the full website audit.

See also: Page weight explained, Mobile-friendly checklist, Website down: what to check.

FAQ

How do I test my website speed for free?

Use the website speed test on this site, Google PageSpeed Insights or Lighthouse in Chrome DevTools. All three use Lighthouse for lab data. Run each test a few times and compare like with like.

Why is my site fast for me but slow in tests?

Your browser has cached files and you probably have a fast device and connection. Tests start from an empty cache on a simulated mid-range phone, which is closer to a first-time mobile visitor.

How fast should a website load?

Aim for the main content to appear within 2.5 seconds on mobile (LCP), with minimal layout shift and quick responses to taps. Faster is better, but the gains flatten out.

Does website speed affect SEO?

Yes, modestly. Core Web Vitals are a ranking signal, but relevance matters far more. Speed also affects bounce rate and conversions directly.

Is a CDN the answer?

It helps with global delivery and caching, but it will not fix oversized images, heavy JavaScript or a slow application. Find the actual bottleneck first.

WebsiteHealthLabs Editorial
Guides explain audit results in plain English. Facts are checked against public documentation from Google, W3C and the browser vendors, and we update them when guidance changes.

↑ ↓ to moveEnter to openEsc to closeAll results