What is PageSpeed Insights?
PageSpeed Insights is a web page at pagespeed.web.dev where you paste a URL and get a report. It returns two kinds of data. The first is field data: how the page actually performed for Chrome users over the last 28 days, drawn from the Chrome User Experience Report and measured against Core Web Vitals. The second is lab data: a fresh load of the page by Lighthouse, Google's auditing engine, on a simulated slow device and connection, with a performance score from 0 to 100 and a list of opportunities and diagnostics.
It reports mobile and desktop separately, and the mobile report is the one that stings. A page that scores 95 on desktop can score 40 on mobile, because the simulated phone is slow and the connection is throttled on purpose. That is the point: it shows the page at its worst, which is how a lot of people meet it.
Why it matters
Why PageSpeed Insights matters
It is the tool Google uses to tell you whether you pass Core Web Vitals, which feed its page experience signals. The field data at the top of the report is the same data Google ranks on. If it says a page fails Largest Contentful Paint, that is not an opinion from a third party; it is the search engine telling you what it sees.
It is also free, instant and specific. Where a general audit says the site is slow, PageSpeed Insights says the hero image is 2.1 megabytes, three render-blocking scripts load before the fonts, and the layout jumps when the web font swaps in. That turns speed from an argument into a to-do list.
In practice
How PageSpeed Insights works in practice
- 01
Run it on the pages that matter, not just the homepage: the campaign landing page, the top product pages, the work page with the reel on it. Read the field data first, because it is what visitors experienced. Then read the lab opportunities in order of estimated savings and hand them to whoever builds the site, with a note about which ones touch the design.
- 02
Treat it as a loop, not a verdict. Fix the biggest items, deploy, run it again, and keep a record of scores by page over time. Field data lags by weeks, so a fix that looks good in the lab today shows up in the Core Web Vitals assessment next month. For ongoing monitoring, the Core Web Vitals report in Search Console covers the whole site at once.
Watch out
What people get wrong about PageSpeed Insights
Reading the lab score as the ranking signal. It is a single simulated run on a slow device and it varies between runs. Google ranks on the field data; the lab score is there to help you find what to fix.
The other mistake is running it once, before launch, on the homepage. Speed decays as content, plugins and tags pile up, and the pages that drive the business are rarely the homepage. Check the pages people actually land on, and check them after every release.
