SEO

Page Experience

Also called Page experience signals, page experience update

Google's grouping of usability signals — loading, stability, responsiveness, HTTPS and mobile-friendliness — describing how a page feels to use.

Quick facts: Page Experience

Category
SEO
Also called
Page experience signals, page experience update
Level
Intermediate
Affects
Close ranking calls, bounce, conversion rate, mobile usability
Where to see it
Search Console Core Web Vitals and HTTPS reports, PageSpeed Insights, Chrome DevTools
In this article4
  1. What page experience measures
  2. Why page experience matters
  3. Common mistakes with page experience
  4. How to act on it

What page experience measures

Page experience is not one score. It is a grouping of things Google can measure about how a page behaves for the person using it: how quickly the main content appears, how quickly the page responds to a tap, whether the layout jumps about while it loads, whether it works properly on a phone, whether it is served over HTTPS, and whether an advert or intrusive interstitial covers the thing the visitor came for. The first three of those are the Core Web Vitals.

Google rolled the grouping out for mobile results in 2021 and for desktop the following year, and has since stopped presenting it as a single system. Search Console no longer keeps one page experience report; the parts are reported separately, with Core Web Vitals and HTTPS each having their own view. The idea survives as guidance rather than as a switch someone flips.

Why page experience matters

Its ranking weight is easy to overstate. Google has been consistent that it still wants to rank the page with the best information, and a fast, tidy page carrying a worse answer does not overtake a slower page carrying a better one. Page experience decides close calls; it does not decide contests between unequal pages.

The commercial case is stronger than the ranking case. A page that shifts under a thumb loses the tap. A page that takes too long on a weak connection loses the visit entirely. In Nepal, where a large share of traffic arrives on mid-range phones over mobile data, the difference between a page that behaves and one that does not shows up in enquiries long before it shows up in rankings.

Common mistakes with page experience

Testing only on office wifi with a laptop is the first. What counts is field data from real visitors’ devices, and it is usually worse than a lab test on a good connection suggests.

The second is chasing a perfect lab score while the real problems sit in the template: an oversized hero image, a chat widget that loads before the content, a cookie banner that arrives late and pushes everything down the screen. The third is treating HTTPS as an experience refinement when it is a baseline — a site without it has a bigger problem than ranking.

How to act on it

Fix things in the order a visitor feels them. Start with whatever blocks the content: pop-ups, banners, anything that covers the answer on a small screen. Then deal with the heaviest item on the page, usually an image or an embedded video. Then the scripts that load before the page is usable, most of which are tags nobody has reviewed in a year.

Measure with field data rather than a single lab run, and remember that these fixes are usually template-level, so repairing a theme once improves every page on the site. If loading time is the constraint, that is what page speed optimisation is for; if the metrics themselves are unfamiliar, start by understanding Core Web Vitals.

Do and do not

Do

  • Judge by field data from real visitors, not lab runs
  • Fix the template once so every page improves
  • Clear anything covering the content on small screens

Do not

  • Expect a fast page to beat a better answer
  • Test only on a laptop and office wifi
  • Chase a perfect score while ignoring heavy scripts

Questions people ask about this

Is page experience a ranking factor?

It contributes, but Google has been clear that it does not override relevance. A page with the better answer generally still wins against a faster page with a weaker one. Treat page experience as something that decides close calls, and as a direct influence on whether a visitor stays long enough to enquire or buy.

What counts as page experience?

How fast the main content loads, how quickly the page responds when someone interacts with it, whether the layout stays still while loading, whether the page works properly on a phone, whether it is served over HTTPS, and whether pop-ups or adverts cover what the visitor came to read. The first three are the Core Web Vitals.

Where do I check page experience?

Search Console reports the parts separately: a Core Web Vitals view built from what real visitors experienced, and an HTTPS view. PageSpeed Insights shows both field data for a URL and a lab test you can rerun after changes. Check using a phone profile rather than a desktop connection, because that is where problems actually appear.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.