How-to steps · Full guide
Is page speed really your problem?
The big score out of 100 is a lab test. What matters is how fast your site is for real visitors. Here is how to read that, in minutes and for free.
Read real-visitor data first
Chapter 6
- Go to PageSpeed Insights and enter one of your priority sales pages.
- Ignore the big performance score. Look at the top section, Discover what your real users are experiencing, and its This URL and Origin tabs. That is field data from real Chrome visitors over the last 28 days.
- Read the Core Web Vitals Assessment: Passed or Failed. It covers three measures:
| Measure | What it means | Good |
|---|---|---|
| Largest Contentful Paint (LCP) | How long the main content takes to appear | 2.5 seconds or less |
| Interaction to Next Paint (INP) | How quickly the page responds to a tap or click | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | How much the page jumps around while loading | 0.1 or less |
Passed? Speed is not your problem: close the tab and spend the time on the work that moves AI visibility. Failed? It is worth fixing, starting with the measure that failed.
No field data? Two ways to check
Chapter 6
- If the page has too few visitors, PageSpeed Insights falls back to data for your whole site (the Origin tab). Use that. If even the origin shows No Data, use one of the checks below.
- Benchmark against your market with StudioHawk's free Is My Page Speed Really a Problem? tool: it compares you with the sites you actually compete with, because fast for a Perth law firm is not fast for a running-shoe store.
- The manual version: on your phone, on mobile data, load each priority page twice and time it until it is readable and steady. Write down the page, the time and what got in the way. Fix the slowest page's first obstacle first.
Why we care so little about the score: across more than 1,000 client sites, nearly half with a red score were fast for real visitors and four in ten with a green score were slow. The full story is in the video.