Why is my page experience poor?

Page experience combines Core Web Vitals, mobile usability, HTTPS, and lack of intrusive interstitials.

• Core Web Vitals fail (LCP, FID, CLS) Mobile usability issues Non-HTTPS or
• Use PageSpeed Insights and Search Console Page Experience report Check Core Web
• Fix Core Web Vitals (see individual guides) Resolve mobile issues Ensure HTTPS

Page experience combines Core Web Vitals, mobile usability, HTTPS, and lack of intrusive interstitials. When these are poor, your pages may be demoted or not favoured in search. Improving speed, mobile experience, and avoiding intrusive overlays supports both rankings and user satisfaction. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not…

Core Web Vitals fail (LCP, FID, CLS). Mobile usability issues. Non-HTTPS or mixed content. Intrusive interstitials (e.g. pop-ups that block content). Slow or janky experience. Ads or layout that hurt usability.

Common examples

A real-world example: after a site update, a business saw visibility drop for "Page experience". They checked Search Console, found the blocking issue, fixed it, and regained impressions over the following crawl cycles.

How to diagnose

Use PageSpeed Insights and Search Console Page Experience report. Check Core Web Vitals, mobile usability, HTTPS, and interstitials. Test on real devices. Identify the weakest areas.

Recommended fixes

Fix Core Web Vitals (see individual guides). Resolve mobile issues. Ensure HTTPS everywhere. Remove or reduce intrusive interstitials. Improve loading and interactivity. Re-test and monitor. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task.