PageSpeed Insights: How to Read Your Report and Fix What Actually Matters

PageSpeed Insights (PSI) is often the first tool marketers open when someone says the site is slow, and also the most misread. The score at the top is not what Google uses to rank pages, and a red number does not always mean a real problem for visitors. This guide explains how to read the report, based on Google's own documentation on Core Web Vitals and the PageSpeed Insights documentation.

What does PageSpeed Insights measure?

Enter a URL at pagespeed.web.dev and you get two blocks for mobile and two for desktop:

• Field data ("Discover what your real users are experiencing"): metrics collected from real Chrome users over the previous 28 days, through the Chrome User Experience Report (CrUX). It appears only if the page or the site has enough traffic.
• Lab data ("Diagnose performance issues"): a Lighthouse test run once, on a simulated mid range mobile device with a throttled connection. It produces the performance score and the list of opportunities.

The two often disagree. Field data reflects your real audience, their devices and networks. Lab data reflects one controlled test. When they differ, trust field data for the diagnosis of user experience, and use lab data to find causes.

What are the Core Web Vitals thresholds?

Core Web Vitals are three metrics Google considers essential to user experience. Each is evaluated at the 75th percentile of page loads: 75% of visits must meet the threshold.

INP replaced First Input Delay (FID) as a Core Web Vital in March 2024. PSI also reports First Contentful Paint (FCP) and Time to First Byte (TTFB), which are useful for diagnosis but are not Core Web Vitals. You can read more in our page on Core Web Vitals and on Largest Contentful Paint.

How is the performance score calculated?

The 0 to 100 score comes only from the Lighthouse lab test. It is a weighted average of five lab metrics: Total Blocking Time, Largest Contentful Paint, Cumulative Layout Shift, First Contentful Paint and Speed Index. A score of 90 or more is good, 50 to 89 needs improvement, under 50 is poor.

The score varies from one run to the next because network and server conditions change. Run the test several times and look at the trend, not at a single value. Above all, do not chase a 100: a page at 75 that passes the Core Web Vitals assessment in field data offers a better experience to real visitors than a page at 98 that fails it.

Does PageSpeed Insights affect SEO?

Core Web Vitals are part of the page experience signals used by Google's ranking systems. Google is clear that relevance and content quality come first: a fast page does not outrank a more useful one. Speed matters most as a tie breaker between comparable pages, and through its indirect effects: slow pages lose visitors before they load, convert less and are crawled less efficiently.

What PSI does not measure is just as important: content quality, search intent, backlinks or your presence in AI answers. A perfect score with thin content will not rank.

Which fixes improve the report first?

The "Opportunities" and "Diagnostics" sections list dozens of items. Prioritize by the metric that fails in field data.

If LCP is slow

• Compress and resize the main image, serve it in WebP or AVIF, and do not lazy load the image at the top of the page. A free image compressor is often enough.
• Reduce server response time (TTFB): caching, a CDN, a faster host.
• Remove render blocking CSS and JavaScript from the critical path, preload the main image and web fonts.

If INP is poor

• Reduce JavaScript: remove unused scripts and third party tags (chat widgets, trackers, A/B testing tools).
• Break up long tasks so the browser can respond to interactions.
• Avoid heavy work in click handlers, and defer non essential scripts.

If CLS is high

• Set width and height on images, videos and iframes.
• Reserve space for ads, banners and embeds.
• Load web fonts with a fallback that has similar metrics, to limit text shifts.

Page weight also matters: very heavy HTML slows down both rendering and crawling. Check yours with our page size checker.

PageSpeed Insights, Lighthouse, Search Console: which tool for what?

A practical routine: monitor the Search Console report monthly, open PSI on the URL groups flagged as poor, fix the cause, then use the "Validate fix" button in Search Console.

Speed is one part of visibility

Use PageSpeed Insights to pass the Core Web Vitals in field data, not to reach a perfect score, then put your effort into content and authority. That is where rankings and AI citations are decided. Sorank automates that part: it writes and publishes optimized articles, builds backlinks and tracks how ChatGPT, Gemini and Claude mention your brand.