What is Google's Page Experience ranking signal?

Page Experience as a formal ranking signal reflects Google's broader shift toward rewarding sites that put users first, not just those that have the most backlinks or the most keyword-stuffed content. The underlying logic is straightforward: if two pages are equally relevant to a query, Google prefers the one that is faster, secure, and usable on mobile.

Core Web Vitals form the technical backbone of the signal. LCP (load speed), INP (interactivity), and CLS (visual stability) are measured using real-user data from Chrome. This means lab test scores in tools like Lighthouse do not directly map to your Search Console CWV report - what matters is how real Chrome users on real devices experience your pages.

HTTPS is a prerequisite, not a differentiator. Sites still running HTTP receive a mild ranking penalty, but switching to HTTPS will not give you a notable boost if everyone else in your niche is already on HTTPS. It is table stakes, not a competitive advantage.

Mobile-friendliness is assessed through Google's Mobile-Friendly Test criteria: text is readable without zooming, tap targets are spaced adequately, content does not overflow the viewport horizontally, and the viewport meta tag is present. With mobile-first indexing now universal, Google primarily uses the mobile version of your page for both ranking and indexing.

The absence of intrusive interstitials (pop-ups that block most of the content on mobile before the user can interact with the page) was part of the original Page Experience rollout. Cookie consent banners, subscription prompts covering more than roughly 30% of the screen, and gate-before-read paywalls can all trigger penalties if they significantly obscure content.