Quick answer
Page experience is Google’s term for aspects of a page that affect how users experience it beyond its content: Core Web Vitals, HTTPS, mobile usability, the absence of intrusive interstitials and an unobtrusive ad experience.
What is page experience?
Page experience is Google's umbrella term for how pleasant a page is to use, beyond its content: how fast it loads and responds, whether the layout stays stable, whether it works on mobile, whether it is served securely, and whether ads or pop-ups get in the way.
Google introduced a "page experience update" as a ranking change in 2021. In 2023 it clarified that page experience is not a single ranking system; instead, its core ranking systems reward content that provides a good page experience, and some signals, such as Core Web Vitals, are used directly. Google's guidance is to focus on overall experience rather than chasing one score.
The aspects of page experience
| Aspect | What Google looks for | How to check |
|---|---|---|
| Core Web Vitals | Good LCP, INP and CLS at the 75th percentile of real visits | Search Console Core Web Vitals report, field data tools |
| HTTPS | Pages served securely | Search Console HTTPS report, browser |
| Mobile-friendliness | Content usable on small screens without zooming | Test on real devices, Lighthouse |
| No intrusive interstitials | No pop-ups that block the main content on arrival | Manual review on mobile |
| Ad experience | Ads do not distract from or overwhelm the content | Manual review |
| Clear main content | Easy to distinguish the main content from everything else | Manual review |
Core Web Vitals thresholds
| Metric | Good | Poor |
|---|---|---|
| Largest Contentful Paint | ≤ 2.5 s | > 4.0 s |
| Interaction to Next Paint | ≤ 200 ms | > 500 ms |
| Cumulative Layout Shift | ≤ 0.1 | > 0.25 |
A URL passes when all three are in the good range at the 75th percentile of page loads over the previous 28 days of field data.
How much does it matter for rankings?
Google describes page experience signals as one of many factors and says relevance and helpfulness come first: a page with great content and average speed can outrank a fast page with weaker content. Where several pages are similarly helpful, experience can make the difference. The larger effect is usually on users: slow, unstable or cluttered pages lose visitors and conversions regardless of rank. See dwell time for how dissatisfied visits show up.
Worked example: prioritizing fixes
A site's templates at P75 from real visits (sample data):
| Template | Share of organic visits | LCP | INP | CLS | Passes? |
|---|---|---|---|---|---|
| Blog post | 58% | 2.1 s | 140 ms | 0.04 | Yes |
| Product page | 27% | 3.6 s | 180 ms | 0.18 | No (LCP, CLS) |
| Category page | 11% | 2.4 s | 320 ms | 0.06 | No (INP) |
| Homepage | 4% | 1.9 s | 120 ms | 0.02 | Yes |
The product page template is the priority: over a quarter of organic visits, two failing metrics, and it is where purchases happen. Fixing the hero image loading and reserving space for review widgets addresses both LCP and CLS. The category page's slow filters (INP) come next.
How to improve page experience
- Measure with field data by template and device, not one lab test of the homepage.
- Fix LCP: serve and prioritize the main image, cut render-blocking resources, speed up the server.
- Fix INP: break up long JavaScript tasks, defer third-party scripts; see total blocking time.
- Fix CLS: set dimensions for images and embeds, reserve space for ads and late content.
- Remove intrusive pop-ups on mobile entry pages; use banners that do not cover content.
- Serve everything over HTTPS and avoid mixed content.
In TapCub
TapCub's performance report collects LCP, INP, CLS, time to first byte and first contentful paint from real visits, so you can read the same 75th-percentile figures Google uses, broken down by page, device, country and browser. A slowest-pages list sorted by P75 LCP and a 0–100 score that combines LCP, INP and CLS help decide which templates to fix first. See check Core Web Vitals and good page load time.
See also: Mobile first.
Sources
- Google Search Central. Understanding page experience in Google Search results.
- web.dev. Web Vitals.
- Google Search Central. Avoid intrusive interstitials and dialogs.
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.
Customer Experience Consultant
Writes about live chat, visitor conversations, and self-service, sharing practical ways to make customer communication clearer and more effective.