About PageSpeed Insights
PageSpeed Insights (PSI) is Google's free tool for checking how fast and stable a web page feels on mobile and desktop, with suggestions on what to fix. Knowing how to read PageSpeed Insights results comes down to one rule: the field data at the top shows what real Chrome users experienced over the last 28 days, while the score lower down is a single simulated lab test. Fix what the field data flags first, and use the lab report to find the cause.
Who makes it and who is it for?
PSI is built by Google and runs at pagespeed.web.dev. It uses two Google data sources: the Chrome User Experience Report (CrUX) for real-user numbers, and Lighthouse for the lab test. You do not need an account; paste a URL and run it.
It is aimed at anyone who owns or builds websites. Bloggers use it to see why a theme feels slow, developers use it to debug, and SEOs use it because the same Core Web Vitals appear in Google Search Console.
How to read PageSpeed Insights results
A report has two halves, and mixing them up is the most common mistake beginners make.
Field data: what real visitors experienced
The top block, titled something like Discover what your real users are experiencing, comes from CrUX. Google says PSI reports real users' First Contentful Paint (FCP), Interaction to Next Paint (INP), Largest Contentful Paint (LCP) and Cumulative Layout Shift (CLS) over the previous 28-day collection period. The three Core Web Vitals are LCP, INP and CLS.
| Metric | What it measures | Good |
|---|---|---|
| LCP | When the main content has loaded | 2,500 ms or less |
| INP | How quickly the page responds to taps and clicks | 200 ms or less |
| CLS | How much the layout jumps around | 0.1 or less |
You can switch between data for this exact URL and for the whole origin (your domain). Small sites often see no data here, because CrUX only includes pages with enough Chrome traffic. In that case Google's FAQ suggests relying on a Lighthouse lab audit instead.
Lab data: the Lighthouse score
The coloured circle with a number from 0 to 100 is the Lighthouse performance score. Google's thresholds: 90 or above is good, 50 to 89 needs improvement, and below 50 is poor. On mobile, Lighthouse simulates a mid-tier phone on a mobile network; on desktop it emulates a desktop on a wired connection. That is why mobile scores are almost always lower.
Under the score you will find Diagnostics and opportunities: oversized images, render-blocking scripts, unused CSS, slow server response and so on. These are the to-do list.
Features that matter for webmasters
- Mobile and desktop tabs in one run.
- Real-user Core Web Vitals from CrUX, at URL and origin level.
- Lighthouse audits for performance, accessibility, best practices and SEO.
- Specific fix suggestions tied to the elements on your page.
- A public API for checking many URLs in bulk.
Pricing as of October 2026
The web tool is free and needs no sign-in. The API can also be used without a key, though Google recommends an API key for frequent, automated queries. Google's getting-started page does not list a price; if you plan heavy automated use, check the current quota in your Google Cloud console.
Limits and honest downsides
- Scores move between runs. Lab tests are sensitive to network and server conditions, so a few points of difference means little.
- Field data lags. It is a rolling 28-day window, so a fix you ship today takes weeks to show fully. Google's FAQ also notes PSI caches results for a short time.
- No data for low-traffic pages. Many small blogs only get origin-level field data, or none.
- A 100 score is not a ranking guarantee. Speed is one signal among many; content and links still carry more weight for most queries.
How do you get started?
- Open pagespeed.web.dev and paste the full URL of a page, not only your homepage.
- Check the field data first. Note any Core Web Vital marked as needing improvement or poor.
- Switch to the Mobile tab if you are not on it; most visitors to small sites are on phones.
- Scroll to Diagnostics and fix the items linked to the failing metric, for example image size for LCP or heavy scripts for INP.
- Re-test, then confirm the trend in the Core Web Vitals report in Search Console over the following weeks.
How it fits bloghints readers
If you are building links or submitting to directories, the pages you send people to should load well on a phone. A slow landing page wastes the traffic a good link sends. Test your key pages before a round of submissions from our directory submission guides, and if you are new to the terms above, our beginner SEO section covers the basics.
Alternatives
- Lighthouse in Chrome DevTools
- WebPageTest
- GTmetrix
Once you know how to read PageSpeed Insights results, the tool becomes quick to use: field data tells you whether real visitors have a problem, the lab score and diagnostics tell you where it comes from, and a re-test plus Search Console confirms the fix over time.
Frequently asked questions
Why is my mobile score so much lower than desktop?
Lighthouse tests mobile as a mid-tier phone on a mobile network and desktop as an emulated desktop on a wired connection. The slower simulated device and network make the same page score lower on mobile. Focus on mobile, since that is what most visitors use.
Why does PageSpeed Insights say there is no field data?
Field data comes from the Chrome User Experience Report, which only includes pages and origins with enough real Chrome traffic. Newer or low-traffic pages often do not qualify. Use the Lighthouse lab results until traffic grows.
What is a good PageSpeed Insights score?
Google treats a Lighthouse performance score of 90 or above as good, 50 to 89 as needing improvement, and below 50 as poor. For real-world checks, aim for LCP of 2.5 seconds or less, INP of 200 ms or less and CLS of 0.1 or less.
