Website Speed Test Tools Explained: PageSpeed Insights, Lighthouse and More
How to use website speed tools like PageSpeed Insights, Lighthouse and Search Console, why scores vary between tests, lab vs field data, and which numbers to act on.
On this page
- Lab tests diagnose problems; field data shows real user experience.
- Scores vary between runs, so look at trends and repeated tests.
- Act on Core Web Vitals and specific opportunities, not chasing a perfect 100.
Run a speed test twice and you may get two different scores. Different tools measure different things. Here's how to read speed tools without getting confused, and which numbers actually matter.
Lab data vs field data
- Lab data: a simulated test on a set device and network (for example Lighthouse). Useful for diagnosing problems; varies from run to run.
- Field data: real measurements from actual Chrome users over the past weeks (shown in PageSpeed Insights and Search Console when there's enough traffic). This reflects real experience.
The main tools
PageSpeed Insights
Shows field data (if available) at the top and a Lighthouse lab report below, with specific suggestions. Test key pages on mobile.
Lighthouse (in Chrome DevTools)
Runs a lab test in your browser, covering performance, accessibility, best practices and SEO. Test in an incognito window to avoid extensions skewing results.
Search Console: Core Web Vitals
Groups your pages by real-user experience (good, needs improvement, poor). Best for tracking progress site-wide.
Other testing tools
Various third-party tools show waterfall charts of every file loaded, which helps diagnose what's slow.
Why scores vary
- Server response time changes from moment to moment
- Test location and simulated network differ between tools
- Third-party scripts (ads, chat, analytics) load differently each time
- Caching: first visits vs repeat visits
Run tests a few times and look at trends, not single scores.
Which numbers to act on
- Core Web Vitals (LCP, INP, CLS), especially from field data; see Core Web Vitals explained
- Server response time
- The specific opportunities listed: large images, render-blocking resources, unused JavaScript
Don't chase 100
A perfect score isn't the goal; a fast experience for real visitors is. A page scoring 85 that loads quickly on phones and converts well beats a 100 with no content.
For fixes, see why WordPress sites are slow or speed optimization.
Need help with your website?
I'm Sameer, a freelance WordPress developer building fast, SEO-friendly websites since 2020. Tell me what you need and I'll reply with a plan and a fixed quote within 24 hours.
Freelance WordPress developer and founder of Samverse, building websites for clinics, manufacturers, agencies and online stores since 2020.
More about me
