# Google PageSpeed vs Lighthouse: how are they different? > PageSpeed Insights and Lighthouse both use the same engine but differ in scope and test conditions. Here's what each measures, why the scores don't match, and when to use which. Published: 2022-09-13T12:21:30.000Z Updated: 2026-04-24T10:00:00.000Z Author: Shameem Reza Category: WordPress Canonical: https://shameemreza.com/google-pagespeed-vs-lighthouse/ --- import Tldr from '../../components/Tldr.astro'; If you run your site through a performance test, you'll likely reach for one of two tools: PageSpeed Insights or Lighthouse. They're both free, both made by Google, and both produce a number out of 100. People often assume they're the same tool with different names. They're not. PageSpeed Insights is the web-hosted tester at `pagespeed.web.dev`. It combines lab data (from a Lighthouse run) with field data (real Chrome users via CrUX). Lighthouse is the underlying engine you can run in Chrome DevTools, from the command line, or through a CI pipeline. That distinction explains most of the confusion about why the two scores don't always match. Same engine, different context. Lighthouse is the audit engine. It runs in your browser or locally and gives you lab data only. PageSpeed Insights runs Lighthouse on Google's servers and stitches the result together with field data from real Chrome users (CrUX). Use PageSpeed Insights to check what real users are experiencing. Use Lighthouse in DevTools or CI to debug a specific page under a controlled test. The scores will often disagree, because one measures the page you just shipped and the other measures the last 28 days of real traffic. ## What is Lighthouse? Lighthouse is an open-source audit tool from Google. It's built into Chrome DevTools, available as a command-line tool, and runs on [web.dev/measure](https://web.dev/measure/). It gives you a score out of 100 for each of four categories: - Performance. - Accessibility. - Best practices. - SEO. ![Lighthouse audit running in Chrome DevTools](/uploads/GoogleLighthouse-1024x705.png) Each category comes with specific, actionable audits. The performance category breaks down the Core Web Vitals (LCP, CLS, INP), gives you a list of what's slowing the page down, and estimates how much you'd save by fixing each item. ![Lighthouse report showing scores and audit recommendations](/uploads/GoogleLighthouseReports-1024x705.png) ## What is PageSpeed Insights? PageSpeed Insights is the web-hosted version at [pagespeed.web.dev](https://pagespeed.web.dev/). You paste in a URL, it runs Lighthouse for you in the background, and then layers in field data from the [Chrome User Experience Report (CrUX)](https://developer.chrome.com/docs/crux) when it's available. ![PageSpeed Insights report for a URL](/uploads/GooglePageSpeedInsights-1024x596.png) The "field data" section is the important part. That's real-world performance for your site, based on actual Chrome users over the last 28 days. If your site doesn't have enough traffic for CrUX data, that section will be empty and you'll only see lab data from the Lighthouse run, which is the same thing you'd get from Lighthouse directly. ## Why the scores disagree You can run Lighthouse locally, get an 85, then hit PageSpeed Insights and see a 62 for the same URL. That's normal. Four things drive the gap. ### Lab vs field data Lighthouse gives you lab data: one run, one test environment, one snapshot. PageSpeed Insights blends that same lab data with field data from CrUX, which is a rolling 28-day average across real visitors on real devices and networks. If your P75 mobile user is on a cheap Android over 4G, that's the experience CrUX captures, and it will almost always be slower than a controlled lab test. ### Test location and CPU Lighthouse in your DevTools uses your actual machine and your actual network. PageSpeed Insights runs from one of a handful of Google data-center regions on a simulated slow 4G connection and a throttled CPU. The simulated device is roughly a mid-tier Android, not the MacBook you're running Chrome on. ### Network throttling PageSpeed Insights throttles to a simulated slow 4G. Lighthouse in DevTools uses whatever throttling profile you select (by default, also slow 4G on mobile). If your DevTools preset is "No throttling" while comparing to PageSpeed Insights, you're not comparing the same thing. ### Page variability A single Lighthouse run can move 5 to 10 points just from variability, third-party ads, A/B tests firing, CDN warm vs cold. Comparing one local run to one hosted run is not a reliable signal. If you want a real number, run Lighthouse three or five times, take the median, and compare to the PageSpeed Insights score for the same URL on the same day. ## When to use which Use PageSpeed Insights when you want to know how real users are experiencing your site. It's the number you should track over time and the one Google uses for the Core Web Vitals signal in Search. Use Lighthouse in DevTools or via `npx lighthouse` when you're debugging a specific page. You can re-run it as often as you want, test different device profiles, and see the detailed audit list without waiting for a hosted run. It's also the right tool for CI, so you can fail a deploy if performance regresses past a threshold. ## A shorter list of other speed tools If you want a second opinion: - [WebPageTest](https://www.webpagetest.org/): the best free tool for detailed waterfall analysis and filmstrips. - [GTmetrix](https://gtmetrix.com/): uses Lighthouse under the hood with a simpler report UI. - [Pingdom Tools](https://tools.pingdom.com/): simpler score but useful for quick checks from specific regions. - [Chrome DevTools Performance tab](https://developer.chrome.com/docs/devtools/performance/): for deeper profiling than Lighthouse alone. For most WordPress sites, PageSpeed Insights plus occasional runs of WebPageTest is enough to tell you whether the site is fast enough and, if not, exactly where to look. ## Two sides of improving site speed There's a technical side: compressing images, serving from a CDN, cutting down on JavaScript, picking a solid host. And there's an operational side: measuring the right metrics, watching them over time, and not chasing a 100/100 score at the cost of what real users actually see. If you're on WordPress, the biggest speed lever is usually your host. I work at Automattic, so my recommendation is [WordPress.com](https://wordpress.com) for most sites or [Pressable](https://pressable.com) if you want more developer control. Both include CDN and caching out of the box, which handles most of what a stack of speed plugins tries to patch on top of slower hosts.