Page experience is Google's collection of UX signals used as a ranking factor. Bryan Collins explains Core Web Vitals, mobile usability, HTTPS, and page experience optimization.
Page experience is Google’s set of UX signals that measure how users perceive interacting with a page beyond its content. Confirmed as a ranking factor in 2021, page experience includes Core Web Vitals (LCP, INP, CLS), HTTPS, mobile usability, and the absence of intrusive pop-ups.
After 30 years in SEO, here’s everything you need to know about page experience and how to optimize for it.
What Page Experience Includes
Google’s page experience ranking signals:
- Core Web Vitals — LCP, INP, and CLS (the primary UX metrics)
- HTTPS — Secure connection required
- Mobile usability — No mobile-hostile elements (text too small, tap targets too close, content wider than screen)
- No intrusive interstitials — No full-screen pop-ups blocking content immediately on page load
Core Web Vitals Explained
LCP — Largest Contentful Paint
- What it measures: How long it takes for the main content element (usually a hero image or headline) to load
- Good: Under 2.5 seconds
- Needs improvement: 2.5–4 seconds
- Poor: Over 4 seconds
- Main fix: Optimize hero images (WebP format, correct sizing, priority loading)
INP — Interaction to Next Paint
- What it measures: How quickly the page responds to user interactions (clicks, taps, key presses)
- Replaced FID (First Input Delay) in March 2024
- Good: Under 200ms
- Needs improvement: 200–500ms
- Poor: Over 500ms
- Main fix: Reduce JavaScript execution time, break up long tasks
CLS — Cumulative Layout Shift
- What it measures: How much the page layout shifts visually while loading
- Good: Under 0.1
- Needs improvement: 0.1–0.25
- Poor: Over 0.25
- Main fix: Add explicit width/height attributes to all images; reserve space for ads before they load
How to Check Page Experience
Google Search Console The authoritative source. Shows field data (real user measurements) for LCP, INP, and CLS.
- Go to Experience > Core Web Vitals to see all pages by status (Good, Needs Improvement, Poor)
- This is what Google actually measures and uses in ranking
PageSpeed Insights (pagespeed.web.dev) Shows both lab data and real-world field data for any URL, with specific improvement recommendations.
Chrome Lighthouse In-browser audit tool (DevTools > Lighthouse tab) for detailed performance diagnostics.
Web Vitals Chrome Extension Shows real-time Core Web Vitals as you browse your site — useful for development.
Improving LCP
The LCP element is almost always the hero image or the page’s H1 headline.
For image-based LCP:
- Convert hero images to WebP or AVIF format (30–50% smaller)
- Add
fetchpriority="high"to the LCP image tag - Remove
loading="lazy"from the LCP image (lazy loading delays it) - Add
<link rel="preload" as="image" href="hero.webp">in<head> - Use a CDN to serve from servers near users
- Remove render-blocking scripts that delay loading
For text-based LCP:
- Preload key fonts
- Eliminate render-blocking CSS
- Reduce server response time (TTFB)
Fixing CLS
CLS is often the easiest Core Web Vital to fix with the highest ROI.
Primary CLS causes and fixes:
| Cause | Fix |
|---|---|
| Image without width/height | Add width and height attributes to all <img> tags |
| Ad that loads and pushes content | Reserve space with a container the same size as the ad |
| Font swap (FOIT/FOUT) | Use font-display: swap and preload key fonts |
| Lazy-loaded content near top | Only lazy-load below-fold images |
| Dynamic content injected above existing content | Insert below existing DOM elements, not above |
Run Google Search Console’s CWV report to identify which pages have CLS issues, then inspect them with PageSpeed Insights to identify the specific elements causing shift.
HTTPS
HTTPS is table stakes for modern websites — non-HTTPS sites show “Not Secure” warnings in Chrome browsers, which:
- Increases bounce rates (users leave immediately)
- Prevents form submissions (users won’t enter data on non-secure sites)
- Google has confirmed HTTPS as a minor ranking signal
HTTPS checklist:
- SSL certificate installed and valid
- All HTTP URLs 301-redirected to HTTPS equivalents
- No mixed content (HTTP resources loaded on HTTPS pages)
- HSTS header implemented
- Verified in Google Search Console under HTTPS
Mobile Usability
Google’s mobile-first indexing means Google primarily crawls and indexes the mobile version of your website. Mobile usability failures include:
- Text too small to read (under 12px font)
- Tap targets too close together (buttons/links less than 48px apart)
- Content wider than the screen (horizontal scrolling required)
- Viewport not configured (no
<meta name="viewport" content="width=device-width">tag) - Flash usage (not supported on mobile)
Check: Google Search Console > Experience > Mobile Usability
Intrusive Interstitials
Avoid full-screen pop-ups that appear immediately when a user lands from a Google search on mobile. Specifically penalized:
- Full-screen pop-ups that must be dismissed before viewing content
- Pop-ups that cover the main content immediately on page load
- Layouts where above-the-fold is primarily an interstitial
Not penalized:
- Cookie consent notices (legally required)
- Age verification for appropriate content
- Login walls for private content
Best practice: Delay any optional pop-ups 30+ seconds, or trigger on exit-intent rather than page load.
Frequently Asked Questions
What is page experience in SEO? Google’s set of signals measuring how users perceive interacting with a page beyond its information value. Includes Core Web Vitals (LCP, INP, CLS), HTTPS, mobile usability, and no intrusive interstitials. Confirmed as a ranking factor in 2021.
What are Core Web Vitals? Three specific UX metrics: LCP (Largest Contentful Paint — loading performance, good: under 2.5s), INP (Interaction to Next Paint — interactivity, good: under 200ms), and CLS (Cumulative Layout Shift — visual stability, good: under 0.1).
How do I check my page experience and Core Web Vitals? Google Search Console’s Core Web Vitals report (authoritative field data), PageSpeed Insights for individual URL analysis, Chrome Lighthouse for lab-based diagnostics, and the Web Vitals Chrome extension for real-time monitoring.
What is HTTPS and why does it matter for page experience? HTTPS encrypts the connection between browser and server. Google confirmed it as a minor ranking signal. Non-HTTPS sites show ‘Not Secure’ warnings, reducing trust and increasing bounce rates. All sites should be on HTTPS with 301 redirects from all HTTP URLs.
What are intrusive interstitials and how do they affect page experience? Full-screen pop-ups that block content immediately when a user lands from search. Google penalizes these on mobile. Exception: legally required cookie notices, age verification, login walls. Best practice: delay pop-ups 30+ seconds or trigger on exit-intent.
How much does page experience affect SEO rankings? Google frames it as a tiebreaker for equally relevant/authoritative pages. Poor page experience can suppress rankings in competitive queries. Fixing Core Web Vitals from ‘Poor’ to ‘Good’ typically produces modest but measurable ranking improvements. Highest ROI fixes: image optimization (LCP), image dimension attributes (CLS), removing intrusive pop-ups.
What is LCP and how do I improve it?
LCP measures when the page’s largest content element (usually hero image or headline) finishes loading. Good: under 2.5 seconds. Improve by: serving images in WebP, adding fetchpriority="high" to the LCP image, preloading it in <head>, using a CDN, and eliminating render-blocking JavaScript/CSS.
Bryan Collins is an SEO consultant based in Piscataway, NJ, with 30+ years of experience helping small businesses grow through content and search. He is a U.S. Marine Corps veteran and the author of Why Your Website Isn’t Ringing.