PageSpeed Insights: What the Scores Mean and What to Fix

PageSpeed Insights is Google's free tool for checking how fast a web page loads and how well it responds, on mobile and on desktop. It gives you two different things that are easy to mix up: real-world data from Chrome users, and a simulated test that produces the score out of 100. The real-world data is the part that matters most.

Key takeaways

• The score out of 100 comes from a simulated test. It is useful for debugging, but it is not what real visitors experience.

• The section called Core Web Vitals Assessment uses real Chrome users over the last 28 days.
• Three numbers matter most: LCP, INP and CLS.
• A page can score 70 and still pass Core Web Vitals, or score 95 and fail.
• Fix your most visited templates first, not every page one at a time.

What is PageSpeed Insights?

PageSpeed Insights, often shortened to PSI, is a Google tool at pagespeed.web.dev. Paste in an address and it reports on that page. It runs Lighthouse, Google's automated page testing tool, and it also pulls real-visitor data from the Chrome User Experience Report (CrUX).

Those two sources explain most of the confusion around the tool, so it is worth knowing which is which before you change anything.

Field data vs lab data: what is the difference?

Field data sits at the top of the report under Core Web Vitals Assessment. It comes from real people using Chrome, over a rolling 28-day period. It shows what actually happened on real phones and real connections.

Lab data sits lower down and produces the Performance score. Google runs Lighthouse once on a simulated device and network. It is repeatable and good for spotting problems, but it may miss things real visitors hit.

If your page does not get enough visits, PSI has no field data for that page and may show data for your whole site instead. Small sites often see this, and it is normal. Use the lab results and the advice in the report as your guide until the traffic builds up.

What do the PageSpeed Insights scores mean?

The Performance score bands, from Google's documentation:

The score moves from run to run, because each test is a single simulated load. A change of a few points usually means nothing. Do not chase 100. The last few points tend to cost a lot of work and do little for real visitors.

What are the Core Web Vitals thresholds?

Core Web Vitals are the three measures Google treats as the core of page experience. PSI reports each at the 75th percentile, which means the figure reflects the slower end of what visitors see, not the average.

Does PageSpeed Insights affect SEO?

Yes, but less than most people think, and not through the score itself. Google's Search documentation says Core Web Vitals are used by its ranking systems, and also says that good results do not guarantee good rankings. Relevance comes first. A slow page that answers the search well will often beat a fast page that does not.

The better reason to fix speed is your visitors. A slow page on a phone loses people before they read a word. So treat speed as a problem worth fixing once your content is doing its job, and do not put off better content to win a few more points.

How do you fix common PageSpeed Insights problems?

The report lists opportunities and diagnostics. These are the ones that come up most often, in rough order of how much they help.

Slow LCP

This is usually a large image at the top of the page. Compress it, serve a modern format such as WebP or AVIF, and make sure it does not load lazily. If the page takes a long time to start responding, look at your hosting or add caching before you touch the page.

Poor INP

This usually means too much JavaScript. Remove plugins and third-party scripts you do not need, starting with old chat widgets and tracking tags. Each one you drop gives the browser less to do.

High CLS

This means things move as the page loads. Set a width and height on images and videos, reserve space for banners and adverts, and load fonts so they do not make text jump.

High Total Blocking Time

This is a lab measure, and it often points at the same scripts as INP. Delay anything that is not needed straight away, and see whether large scripts can be split up.

How do you use PageSpeed Insights across a whole site?

PSI checks one page at a time, which is fine for a homepage and slow for anything larger. A sensible routine for a small site:

1. Test one page of each type: homepage, a service or product page, a blog post, a contact page.
2. Fix the problems in the shared template, because that fixes every page built on it.
3. Run the test again and compare it with your first result.
4. Check Core Web Vitals in Google Search Console, which groups pages together and shows trends over time.

Our guide to Google Search Console explains where to find that report.

UtilitySEO runs the same Google checks across a sample of your pages during a site scan, then explains each problem in plain English and shows how to fix it. Start with a free SEO scan to see where your site stands. Plans start from £39 a month.