Docs Speed
PageSpeed performance and Core Web Vitals
How the Speed score works: it is Google's mobile PageSpeed performance score, shown with LCP, CLS, TBT, a desktop score and the biggest savings.
What it checks
We ask the Google PageSpeed Insights API to test your homepage with its mobile settings. PageSpeed loads the page in Lighthouse on Google's servers and measures it. This is a lab test of one load, not data from your real visitors, so results can move a few points between runs.
Your Speed score is the mobile performance score from that run, out of 100. The rows in the Speed section explain it, but none of them is weighted on its own:
Mobile performance score (psi-score): the score itself. Pass at 90 or higher, warning at 50 to 89, fail under 50.
Largest Contentful Paint (psi-largest-contentful-paint): when the biggest piece of content, usually the hero image or headline, appears. Pass up to 2.5 seconds, warning up to 4 seconds, fail above.
Cumulative Layout Shift (psi-cumulative-layout-shift): how much the page jumps around while it loads. Pass up to 0.1, warning up to 0.25, fail above.
Total Blocking Time (psi-total-blocking-time): how long the page is too busy running scripts to respond to taps. Pass up to 200 ms, warning up to 600 ms, fail above.
Savings (psi-opp- plus the audit name): up to 4 of Lighthouse's suggestions that would save more than 0.3 seconds each, biggest first, shown as warnings.
Desktop performance score (psi-desktop): a second run with desktop settings, with the same 90 and 50 bands. Shown for comparison only. It does not affect the Speed score.
If PageSpeed does not return a result, for example because it timed out, Speed shows as n/a and the overall score is the average of the other three pillars. A metric PageSpeed did not report shows as info.
- PassScore 90 or higher, or a metric inside the good range above.
- WarningScore 50 to 89, or a metric in the middle range. Savings rows are always warnings.
- FailScore under 50, or a metric past the upper limit.
- InfoPageSpeed did not return this result. Not scored.
Why it matters
Visitors leave pages that are slow to show anything, that jump while they try to tap, or that freeze when they scroll. Mobile matters most because phones have slower processors and connections than the computer the site was built on.
Largest Contentful Paint and Cumulative Layout Shift are two of Google's Core Web Vitals, and the pass limits here match the limits Google publishes for good.
How to fix it
For Largest Contentful Paint: make the main image smaller and in a modern format, do not lazy-load the image at the top of the page, and cut the CSS and JavaScript that must load before anything shows. A faster server or a CDN helps too.
For Cumulative Layout Shift: give images, videos and embeds a fixed size, and keep space for banners, ads and cookie notices so they do not push content down.
For Total Blocking Time: remove scripts you do not need, load the rest later, and look hard at third-party tags such as chat widgets, trackers and ad scripts.
Then work through the savings rows in your report, biggest first. PageSpeed Insights shows the files behind each one.
Platform notes
A caching plugin, an image optimisation plugin and fewer plugins overall usually make the biggest difference. Page builders and sliders add a lot of CSS and JavaScript.
Every app can add scripts to the storefront. Remove apps you no longer use and check the theme for leftover app code.
Compress images before upload, use fewer heavy sections such as video backgrounds and galleries at the top of the page, and limit third-party embeds.
Compress images, limit interactions and animations above the fold, and keep custom scripts to a minimum.
Caching HTML at the edge and Cloudflare's image tools can cut load time, but they cannot fix a page that ships too much JavaScript.
Use next/image with explicit sizes and mark the main image as high priority, use next/font for fonts, and keep components that do not need the browser as server components.
Your report shows what this check found on your site. Pro shows the exact fix for your site. See pricing.
Questions
Why does my Speed score change between scans?
PageSpeed runs a fresh lab test each time, and network and server conditions change between runs. Moves of a few points are normal, so look at the trend over several scans.
Why is my mobile score lower than desktop?
The mobile test simulates a slower phone and connection, so the same page scores lower. The Speed score uses the mobile result.
Free, about 30 seconds, with every other check included.