Page Experience
Page experience is the Google grouping of signals about how a page feels to use. Learn what it includes now and what changed when the report was retired.
TL;DR
Page experience is the Google term for the set of signals describing how a page feels to use, as distinct from what it says. It covers loading performance, responsiveness, visual stability, mobile usability and secure connections. Google retired the dedicated report in Search Console and stopped describing it as a discrete ranking system, folding the signals into broader quality assessment.
Why page experience matters
The individual signals still influence rankings and still determine whether visitors stay long enough to read anything.
- Ranking contribution: The component signals remain in use even though the umbrella framing was dropped.
- Conversion effect: Pages that load slowly or shift while loading lose users before the content is read.
- Tiebreaking: Between comparably relevant pages, the one that performs better has an advantage.
- Crawl capacity: Faster server responses let crawlers fetch more, which matters on large sites.
What page experience includes
Core Web Vitals
LCP for loading, INP for responsiveness and CLS for visual stability, each with published thresholds.
Mobile usability
Readable text without zooming, tap targets spaced properly, and content fitting the viewport.
HTTPS
A secure connection, now a baseline expectation rather than a differentiator.
No intrusive interstitials
Popups covering the content a visitor arrived for, particularly on mobile.
Safe browsing
Absence of malware and deceptive content, which is a disqualifier rather than a gradient.
Overall usability
Whether someone can accomplish what they came for without friction, which resists precise measurement.
Page experience vs. Core Web Vitals
Page experience: The broader grouping, including mobile usability, HTTPS and interstitial behaviour alongside performance.
Core Web Vitals: The three measurable performance metrics that form the quantifiable part of that grouping.
Vitals are the part with numbers and thresholds, which is why they receive nearly all the attention. The rest of page experience matters and is harder to put on a dashboard.
Experience signals affect human visitors far more than AI engines, which care whether they can fetch and parse a page. Findrix runs a 31-point technical audit covering rendering and crawler access, then tracks how often seven engines cite you against named competitors. Every gap comes with the fix already written: technical, content and off-site. The audit is free, takes about a minute, and requires no signup.
What changed when the report was retired
Google removed the page experience report from Search Console and stopped presenting page experience as a named ranking system. Core Web Vitals reporting continues separately.
The change was presentational rather than substantive. The signals did not stop mattering; Google stopped grouping them under a label that had encouraged teams to treat experience as a checklist to pass rather than a property of a well-built site.
Fix genuinely poor performance on pages that matter, keep the site usable on a phone, and stop covering content with popups. That was always the substance.
Frequently asked questions
Is page experience still a ranking factor?
The individual signals are. Google retired the unified framing and the Search Console report, but Core Web Vitals, mobile usability and HTTPS continue to feed ranking assessments.
What happened to the page experience report?
Google removed it from Search Console, keeping the Core Web Vitals report separate. The company said the grouped framing was causing confusion about how the signals were used.
How much does page experience affect rankings?
Modestly. Google has been consistent that content relevance and quality dominate, with experience signals acting as a differentiator between pages that are otherwise closely matched.