Page speed
The script times every page load in your visitors’ own browsers, and the Speed page shows how fast the site is for them.
Unlike a test from your own computer, these timings come from your visitors’ own phones and connections, rated by Google’s thresholds, including the Core Web Vitals its search takes into account. The pages with the most poor loads are listed, so you know where to start. The tag you already have measures it all.

The six measures
- TTFB, time to first byte: how long the server took to start answering.
- FCP, first contentful paint: when the first text or image appeared.
- LCP, largest contentful paint: when the largest text or image appeared, usually when the page looks loaded.
- INP, interaction to next paint: how long the page took to respond to a click, tap or key press, at its slowest. Only a page the visitor used has one.
- CLS, cumulative layout shift: how much the page jumped about as it loaded, as a score rather than a time.
- PLT, page load time: when the browser finished loading the page and everything on it.
LCP, INP and CLS are Google’s Core Web Vitals.
Ratings
Each is rated good, needs improvement or poor, by Google’s thresholds. PLT has no standard, so fivebar sets its own.
| Measure | Good | Poor | Reported by |
|---|---|---|---|
| TTFB | Up to 800 ms | Over 1.8 s | Every browser |
| FCP | Up to 1.8 s | Over 3 s | Every browser |
| LCP | Up to 2.5 s | Over 4 s | Chrome, Edge, Firefox 122+, Safari 26.2+ |
| INP | Up to 200 ms | Over 500 ms | Chrome, Edge, Firefox 144+, Safari 26.2+ |
| CLS | Up to 0.1 | Over 0.25 | Chrome and Edge |
| PLT | Up to 3 s | Over 6 s | Every browser |
Anything in between needs improvement. A measure a browser can’t take is left out for that page load rather than counted as nought, so each tile says how many page loads it’s from.
The Speed page
Open it from the Overview, Speed, Errors and Bots switch under the site’s name. The dot beside Speed gives the Core Web Vitals at a glance: green when LCP, INP and CLS are all good, otherwise amber or red for the worst of them. Hover over it for each one’s figure. A measure with no page loads, such as INP where nobody clicked, is left out.
The page keeps the dashboard’s dates and filters. At the top is a tile for each measure, with:
- its 75th percentile: three in four page loads were at least this fast
- how far it moved since the period before, in the same unit, with the earlier figure in its tooltip
- its rating, and the share of page loads that were good, needed improvement and were poor
- the same figure for phones, tablets and desktops
- how many page loads it was measured on
The 75th percentile is what Google rates a site by. It reflects most visitors without letting the fastest hide the slowest, as an average would.
Below the tiles is one measure in detail, LCP unless you pick another:
- a chart of its 75th percentile for each day, week or month of the range, with dashed lines where good ends and poor begins
- its 75th percentile by device, browser and country, each with how many page loads it’s from; click any of them to filter the page
- the pages with the most poor loads, each with its 75th percentile, its page loads and the share that were poor
The API gives the six measures in a site’s stats, and the slowest pages as the
slowest-pages-lcp and slowest-pages-inp panes. An app
connected over MCP reads the Speed page with get_site_speed.
What is measured
- Each page load once, reported when the visitor leaves it or switches away, since LCP, INP and CLS aren’t final until then.
- Not the pages a single-page app moves to, which load nothing.
- Not paints made while the page was in a background tab, so a page opened in the background has no FCP or LCP, and one closed before it was ever shown has no CLS either.
- A prerendered page is timed from when the visitor went to it.
- Not error pages.
Under a filter, the Speed page times the page loads that match: filtered by a page, that page’s own. The six measures have nothing to show when the range has no measured page loads, and the page has nothing when filtered by an entry or exit page, or by a goal.
Server timing
If your server sends a Server-Timing header with a page, each entry’s name and duration are
counted too:
Server-Timing: db;dur=53, cache;desc=HIT, app;dur=47.2- A description is never sent or kept, and an entry with only a description, such as
cachehere, is left out. - The same name twice in one page load is added up.
- Up to 16 names a page load, the first 16 in the header.
- A name is up to 32 characters and a duration up to 5 minutes. An entry past either is left out and takes none of the 16.
- Only the page’s own response, not its images, scripts or API calls.
- HTTPS pages only, in Chrome and Edge 65+, Firefox 61+ and Safari 16.4+.
- Not a page load from the browser’s cache.
- Counted from 18 October 2026, so no change is shown against dates before it.
A call to an API or MCP server can send its own with its server
event, as server_timing, and is counted beside page loads.
The Speed page lists the ten names reported most at its foot, on every measure’s tab, each with its 75th
percentile, the page loads that reported it and their share of all, and how far it moved since the period before.
Where calls sent theirs, it counts page loads and calls together, and a share is out of both. The
API gives them as serverTiming in a site’s stats, and
get_site_speed as server_timing, with how many calls sent any as
serverCalls and server_timing_calls. A name that read 0 ms every time is a flag,
not a timing, and isn’t listed.