Quick answer: Google’s page experience update is a ranking change that combines Core Web Vitals (LCP, FID and CLS) with existing signals such as mobile-friendliness, HTTPS, safe browsing and intrusive interstitial guidelines. In November 2020 Google confirmed the rollout will begin in May 2021. You still have time to measure your pages, fix the worst issues and watch Search Console before the change starts.
What Google announced and when it starts
Google first described page experience as a ranking signal in May 2020. It said Core Web Vitals would join mobile-friendliness, HTTPS, safe browsing and the interstitial guidelines already used for mobile search. It also promised at least six months’ notice before any ranking impact.
That notice arrived in November 2020: the page experience update will begin rolling out in May 2021. Google has said the rollout will take weeks, not a single day, so ranking shifts should arrive gradually rather than overnight.
For site owners writing in early January 2021, the practical takeaway is simple. The change is confirmed. The start date is known. The remaining months are for measurement and fixes, not for waiting to see what happens.
What counts as page experience
Page experience is not one score. It is a group of signals that describe how a visitor feels when they land on a page.
Core Web Vitals
These three metrics sit at the center of the update:
- Largest Contentful Paint (LCP): how long it takes for the main content in the viewport to appear. Aim for 2.5 seconds or less.
- First Input Delay (FID): how long it takes for the page to respond to the first tap or click. Aim for 100 milliseconds or less.
- Cumulative Layout Shift (CLS): how much the layout jumps while the page loads. Aim for 0.1 or less.
We covered thresholds, causes and fixes in more detail in our Core Web Vitals guide. For this checklist article, treat those three as the new work Google wants you to finish before May.
Signals that already existed
Page experience also includes:
- Mobile-friendliness. Pages that work on phones. Google’s mobile-friendly update made this a ranking factor years ago.
- HTTPS. Secure pages. If you still have mixed content after moving to SSL, fix that first. See our notes on HTTPS migration and mixed content warnings.
- Safe browsing. No malware or deceptive pages flagged in Search Console.
- Intrusive interstitials. Avoid full-screen pop-ups that hide the content people came for, especially on mobile.
Google has been clear that relevance still comes first. A page that answers the query well can outrank a faster but thinner page. Where two pages are similarly useful, page experience can tip the balance.
How to check your site right now
You do not need new tools for this. Use what Google already provides, and treat field data as more important than a single lab score.
Search Console’s Core Web Vitals report
Search Console groups URLs into “Good,” “Needs improvement” and “Poor” based on real Chrome user data (CrUX). Open the report, start with mobile, and note which templates or URL groups fail. Field data is what Google plans to use for ranking, so this report is your primary checklist source.
PageSpeed Insights
PageSpeed Insights shows both field data (when available) and lab data from Lighthouse. Use lab results to reproduce problems and test fixes. Do not treat a single lab run as the ranking score. Lab tools run on a simulated device. Field data reflects real visitors.
Chrome DevTools and Lighthouse
For layout shifts and main-thread work, DevTools Performance and Lighthouse in Chrome help you spot the scripts, images and fonts causing trouble. Re-test after each change so you know which fix actually moved the metric.
Preparation checklist before May 2021
Work through this list in order. Fixing the foundation first makes later work stick.
1. Confirm HTTPS and clean mixed content
Every important URL should load over HTTPS with no insecure images, scripts or stylesheets. Mixed content can block resources and hurt both security signals and speed.
2. Confirm mobile usability
Run Search Console’s mobile usability report. Fix viewport issues, tiny tap targets and content wider than the screen. Mobile is where most Core Web Vitals field data is judged for ranking impact.
3. Improve LCP on key templates
Focus on homepage, category/listing pages and high-traffic landing pages first.
- Reduce server response time with caching and a capable host.
- Compress and correctly size hero images. Prefer modern formats where your audience’s browsers support them.
- Inline or defer critical CSS. Avoid large render-blocking bundles in the head.
- Preload the LCP image or font when that resource is clearly the bottleneck.
Phone users often see slower LCP than desktop users on the same site. Our mobile page speed article explains why.
4. Reduce FID by cutting main-thread work
FID is a field-only metric. In the lab, Total Blocking Time is a useful proxy.
- Split and defer non-critical JavaScript.
- Remove unused third-party tags, or load them after interaction where possible.
- Prefer lighter libraries for menus, carousels and analytics.
- Avoid long tasks that block the first tap after paint.
5. Stabilize layout for CLS
Layout shift is often the easiest metric to improve once you know the cause.
- Always set width and height (or aspect-ratio CSS) on images and embeds.
- Reserve space for ads and embeds before they load.
- Avoid inserting banners above existing content after load.
- Load web fonts carefully so text does not jump when the font swaps. See web fonts and page speed.
6. Review interstitials and overlays
Cookie notices that take the whole screen, newsletter pop-ups on entry and age gates that cover content all risk the interstitial guidelines. Prefer banners that leave most of the content visible, especially on mobile.
7. Watch Search Console through the rollout
From now until after May 2021, check the Core Web Vitals report monthly. After the update starts, watch rankings and impressions for pages that moved from Poor to Good. Page experience is one factor among many, so expect small to moderate shifts rather than a full reshuffle of every keyword.
What this update does not mean
A few misconceptions are already circulating.
It is not a replacement for good content. Google has said useful, relevant pages can still rank with average page experience. Do not gut your content to chase a lab score.
It is not an AMP requirement. Once page experience launches, AMP will no longer be required for Top Stories eligibility on mobile, as long as pages meet the page experience criteria. That change is part of the same May 2021 window.
It is not live yet. Writing in January 2021, the ranking impact has not started. Use this window to fix real user problems. Panic publishing of thin “speed tips” posts will not help.
FID is still the responsiveness metric for ranking language. Google may iterate on metrics over time, but as of early 2021 the Core Web Vitals set for page experience is LCP, FID and CLS.
A sensible timeline from January to May
- January to February: Measure. Export Search Console groups. Pick the worst templates. Reproduce issues in PageSpeed Insights and DevTools.
- February to March: Fix LCP and CLS on priority templates. Deploy, re-measure field data (it lags) and lab scores.
- March to April: Tackle FID-related script work and third-party cleanup. Re-check mobile usability and HTTPS.
- April to May: Freeze major redesigns on key money pages. Monitor Search Console as the rollout begins.
SEO timelines are rarely overnight. Our piece on how long SEO takes is a useful reminder that technical fixes can show sooner than content work, but they still need crawl and reprocessing time.
Common questions
Will poor Core Web Vitals kill my rankings in May?
Unlikely on their own. Google has framed page experience as a tie-breaker when relevance is similar. Sites with severe speed or stability problems on mobile may see more movement than sites that are already “Good” or close to it.
Should I chase a perfect 100 in PageSpeed Insights?
No. Aim for Good thresholds in field data for LCP, FID and CLS. A lab score of 100 that ignores real users is less useful than Good CrUX data with a mid-range lab score.
Do I need a full redesign?
Usually not. Most LCP and CLS problems come from images, fonts, ads and a few heavy scripts. Fix those before rewriting the whole theme.
What about desktop?
Google’s page experience guidance for this update focuses on mobile ranking. Improving desktop still helps users, but prioritize mobile field data first.
The bottom line
The page experience update is a known May 2021 rollout, not a surprise. Measure with Search Console and PageSpeed Insights, fix LCP, FID and CLS on your important templates, keep HTTPS and mobile basics clean, and avoid intrusive overlays. Do the work now while there is still runway before ranking impact begins.
If you want help turning this checklist into a concrete fix list for your site, see how our Get found services work.
