/GOOGLE PAGE EXPERIENCE
GOOGLE PAGE EXPERIENCE
WHAT IT MEASURES, WHAT IT DOESN’T
Page experience is Google’s term for a set of signals about how a page feels to use: how quickly the main content appears, how promptly it responds, and whether it moves under your finger. This page explains what is measured, how, and — the part usually left out — how much it is worth.
/THE THREE
CORE WEB VITALS
Each measures a different kind of frustration. Google publishes a threshold for each below which the experience is classified as good.
Largest Contentful Paint
How long until the largest piece of content in the viewport has rendered — in practice, when the page stops looking empty. Google’s published threshold for a good experience is 2.5 seconds or less. Usually governed by server response time, render-blocking resources and how the hero image is loaded.
Interaction to Next Paint
How quickly the page visibly responds after a user interacts with it, across the whole visit rather than only the first click. The published good threshold is 200 milliseconds or less. Almost always a JavaScript problem: long tasks blocking the main thread when someone taps.
Cumulative Layout Shift
How much the content jumps around while loading — the reason you tap the wrong thing on a news site. The published good threshold is 0.1 or less. Caused by images and embeds without reserved dimensions, late-loading fonts, and banners injected above existing content.
/WHAT ELSE IS
IN THE SIGNAL
Page experience is broader than the three metrics, though the rest of it is mostly hygiene that a competent build already satisfies.
- HTTPS. Non-negotiable, and by now unusual to be missing — though mixed content on individual templates is not.
- Mobile usability. Tap targets, viewport configuration and text that is readable without zooming. Assessed on the mobile version, because that is what is predominantly crawled.
- No intrusive interstitials. Content covered on arrival by a pop-up that is difficult to dismiss. Consent notices required by law are a separate matter, but a consent banner plus a newsletter modal plus a discount wheel is three of them.
- The absence of anything actively hostile. Autoplaying audio, unclosable overlays, layout that breaks on rotation. Rarely deliberate, frequently shipped.
/FIELD DATA
VERSUS LAB DATA
This distinction causes more wasted effort than anything else on the subject. Lab data is a single simulated load on defined hardware and network conditions — reproducible, useful for debugging, and not what is assessed. Field data is aggregated from real visits by real users on their real devices and connections, and it is what actually counts.
A page can score well in a lab test and fail on field data because your visitors are on older phones and slower connections than the simulation assumes. It can also improve in the field with no change to the lab score at all. Field data is only available once a page or origin has enough traffic, which is why smaller sites often have to work from lab data and inference.
The practical rule: debug with lab tools, judge with field data, and never celebrate a synthetic score. The assessment is made per URL where enough data exists, and falls back to a broader grouping where it does not — so a single slow template can affect how a whole section is judged.
/WHAT USUALLY
CAUSES EACH FAILURE
Diagnosis is faster if you know the usual suspects, and on most sites it is a short list.
- Slow largest paint — server or platform response time, a hero image loaded lazily or in the wrong format, render-blocking CSS and fonts, and third-party scripts loaded before content.
- Poor interaction responsiveness — too much JavaScript executing on the main thread, heavy hydration on frameworks that render client-side, and tag managers loading a dozen marketing scripts at once.
- Layout shift — images and iframes without width and height, web fonts swapping late, cookie banners and promotional bars inserted above the fold after render, and dynamically injected ad slots.
- All three at once — usually a theme or page builder doing far more work than the page requires. At that point the cheapest fix is frequently structural rather than incremental.
/HOW MUCH
IS IT WORTH?
Less than the tooling implies, and more than the cynics claim. Page experience is a comparatively light signal, and it does not lift a page that is a poor answer to the query above one that is a good answer. Sites that rebuild around a performance score and neglect relevance reliably end up fast and invisible.
It matters most as a tie-breaker in competitive result sets, and it matters considerably more for reasons that have nothing to do with ranking: conversion rate, bounce behavior and advertising quality signals are all sensitive to load performance. That is the honest business case, and it does not depend on any search engine’s weighting.
Our recommendation is consistent: fix indexing and relevance first, treat page experience as ongoing engineering hygiene rather than a campaign, and measure it in the field on the templates that carry your revenue rather than on the homepage.
/FREQUENTLY ASKED
QUESTIONS
WANT THIS MEASURED
ON YOUR TEMPLATES?
Performance work is worth doing on the templates that carry revenue and rarely worth doing everywhere. Send us the domain and we will tell you which templates are failing in the field, what is causing it, and which of those causes is worth the engineering time.
- Technical SEO — where performance work belongs in the sequence
- Technical audits — the engineering side of the same investigation
- Free SEO tools — measure it yourself first
- All Insights — the full index of guides, tools and updates
Start your journey
Send the domain. We will tell you which templates actually need the work.