Book a call Free rebuild
Home/Glossary/Performance/PageSpeed Insights

PageSpeed Insights

January 20, 2026 Updated November 16, 2026 4 min read

Performance glossaryPageSpeed Insights is Google's free tool that scores a page's speed with Lighthouse and shows its Core Web Vitals from real Chrome users.

PageSpeed Insights (PSI) is Google's free tool for checking how fast a page is, at pagespeed.web.dev. Enter a URL and it returns two kinds of results: field data showing how real Chrome users have experienced the page, and a lab test run with Lighthouse, with a score and a list of suggested fixes. It is often the first tool we open when a WordPress site feels slow.

Field data: what real visitors experience

The top of the report comes from the Chrome UX Report (CrUX). It covers the previous 28 days of visits by Chrome users, for the URL and for the whole origin, shown separately for mobile and desktop.

It includes the three Core Web Vitals (Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift) plus First Contentful Paint and Time to First Byte. The Core Web Vitals assessment passes when all three vitals are good at the 75th percentile.

Pages without enough traffic show no URL-level field data, and small sites may have none at all, leaving only the lab results.

Lab data: the Lighthouse test

The lower part of the report is a Lighthouse test run on Google's servers. The mobile test simulates a mid-range phone on a slow mobile connection; the desktop test uses a desktop profile. The performance score, from 0 to 100, is a weighted blend of five lab metrics: First Contentful Paint, Speed Index, Largest Contentful Paint, Total Blocking Time, and Cumulative Layout Shift. A score of 90 or more is good, 50 to 89 needs improvement, and under 50 is poor.

Below the score, Lighthouse lists insights and diagnostics, such as render-blocking requests, image delivery, unused JavaScript, and long main-thread tasks, each with the files responsible. The report also scores accessibility, best practices, and SEO.

How to read the report

  • Field data wins. Google uses field data, not the lab score, for Core Web Vitals in Search. A page can score 60 in the lab and pass in the field, or the reverse.
  • Mobile matters most. The mobile test is deliberately harsh and is where most problems show up.
  • The score varies. Lab scores move a few points between runs because network and server conditions change. Run a test several times before drawing conclusions.
  • Field data lags. After a fix, the lab result changes at once, but the 28-day field data takes up to four weeks to reflect it fully.
  • A perfect 100 is not the goal. Passing Core Web Vitals and a fast experience for real visitors are.

Using it on a WordPress site

Test the templates that matter, not only the home page: a single post, a product page, and a category archive, each as a logged-out visitor. The most common findings on WordPress sites are a slow server response without page caching, oversized images, render-blocking CSS and JavaScript from plugins and page builders, and heavy third-party scripts. For specific fixes, see our guides to reducing LCP and fixing layout shifts.

FAQs

What are Core Web Vitals metrics and why do they matter?

Core Web Vitals are three measures of real-user experience: Largest Contentful Paint for loading, Interaction to Next Paint for responsiveness, and Cumulative Layout Shift for visual stability. Google uses them in its page experience signals for Search, and they track problems visitors notice, such as slow main content, laggy buttons, and jumping layouts.

How does Google PageSpeed Insights collect performance metrics?

From two sources. Field data comes from the Chrome UX Report, which aggregates real Chrome users' visits over the previous 28 days. Lab data comes from a Lighthouse test that PageSpeed Insights runs on Google's servers when a URL is submitted, simulating a mobile or desktop device.

Can PageSpeed Insights help improve both desktop and mobile versions?

Yes. It reports mobile and desktop separately, each with its own field data, lab score, and suggestions. Mobile results are usually worse, because the test simulates a slower device and connection, so that is the place to start.

What common issues affect the Google PageSpeed Insights score?

The most common are a slow server response, render-blocking CSS and JavaScript, large or unoptimized images, too much JavaScript on the main thread, heavy third-party scripts, and images or ads without reserved space, which cause layout shifts.

How often should I check my PageSpeed Insights performance metrics?

After any significant change, such as a new theme, plugin, page layout, or third-party script, and otherwise about once a month for key templates. Field data covers 28 days, so a fix takes up to four weeks to show fully. Google Search Console's Core Web Vitals report is a convenient way to watch the whole site between checks.

WP Services

WordPress services at revolutionary pricing.

Productized WordPress services, from builds to care, delivered by Seahawk and tracked in one app. For the WordPress lovers.