In May 2020, Google announced that Search would combine Core Web Vitals with existing page experience signals. The company also said page experience would become part of mobile Top Stories ranking criteria and that AMP would no longer be required for Top Stories eligibility.
That rollout is no longer in the future. The page experience update began rolling out globally in June 2021, and Google’s current Search Central guidance now frames page experience as a set of signals and questions rather than one switch you can turn on.
Google’s current guidance is also more careful than many SEO discussions make it sound. There is no single page experience signal. Core Web Vitals are used by Google’s ranking systems, but good scores in Search Console or third-party tools don’t guarantee top rankings.
What Core Web Vitals measure now
Core Web Vitals are Google’s real-world user experience metrics for loading performance, responsiveness, and visual stability. The current set is:
Largest Contentful Paint (LCP): how quickly the main content appears. Google’s recommended target is within 2.5 seconds of the page starting to load.
Interaction to Next Paint (INP): how quickly the page responds after a click, tap, or keyboard interaction. Google’s recommended target is less than 200 milliseconds.
Cumulative Layout Shift (CLS): how much the page moves around unexpectedly as it loads. Google’s recommended target is less than 0.1.
One key change since the original announcement: INP replaced First Input Delay (FID) as the Core Web Vitals responsiveness metric on March 12, 2024. If your reports, audits, or agency decks still focus on FID, they’re out of date.
Search Console data is not the same as a one-off speed test
The Core Web Vitals report in Search Console is based on field data from real users. It groups similar URLs and reports status by device type, which means a template problem can show up across many pages at once.
PageSpeed Insights, Lighthouse, and Chrome DevTools are still useful, but they don’t all answer the same question. Field data tells you what real visitors experienced. Lab tests help diagnose why a page may be slow, unstable, or difficult to interact with before changes go live.
Page experience is bigger than speed
Google’s current page experience guidance asks site owners to look beyond Core Web Vitals. It points to HTTPS, mobile display, excessive ads, intrusive interstitials, and whether visitors can easily distinguish the main content from everything around it.
A fast page can still frustrate visitors if it buries the answer under ads, opens with an aggressive popup, or makes the main action hard to find on a phone.
What this means for SEO
Helpful content still comes first
If a page doesn’t satisfy the search intent, better Core Web Vitals won’t make it the strongest result. Google’s own guidance says Search still seeks the most relevant content, even if that page has a weaker experience.
If your bigger issue is thin or search-first content, start with our guide to Google’s helpful content system. If quality varies across your site, our article on Google’s sitewide signals explains why weak sections can affect the trust you build overall.
Performance still affects business outcomes
A slow or jumpy page can cost you before rankings even enter the picture. Visitors may leave before reading, abandon a form because the tap feels delayed, or lose confidence when buttons and content move as they load.
AMP is no longer the shortcut
For publishers, the AMP change mattered because mobile Top Stories eligibility opened beyond AMP pages. Google still supports AMP, but the stronger long-term play is to make the main version of your site fast, readable, stable, and useful.
What to check first
Start with the pages and templates that affect revenue, leads, and trust. For most businesses, that means home pages, service pages, product pages, blog posts that bring qualified search traffic, forms, booking flows, and checkout pages.
Open the Core Web Vitals report in Search Console. Start with URL groups marked Poor, then move to groups marked Need improvement.
Test representative URLs in PageSpeed Insights. Compare field data with lab data so you can separate real-user issues from one-off test conditions.
Check the mobile experience by hand. Use a real phone to test menus, forms, call buttons, booking tools, search, carts, and checkout paths.
Review popups, ad blocks, and cookie notices. Make sure they don’t block the answer or make the main content hard to reach.
Map fixes by template. If one service page has poor LCP, the same issue may affect every page built from that template.
How to prioritize Core Web Vitals fixes
Don’t treat every score as equal. Fix the issue that blocks real visitors on high-value pages first.
If LCP is poor, look at large hero images, slow server response, render-blocking files, caching, fonts, and theme weight.
If INP is poor, look for heavy JavaScript, overloaded page builders, slow menus, unresponsive forms, cart scripts, chat widgets, and third-party tracking tags.
If CLS is poor, reserve space for images, videos, ads, banners, and embeds. Watch for fonts or injected elements that push the page around after loading.
If you run WordPress, theme bloat, unoptimized images, heavy page builders, ad scripts, and plugin conflicts are common places to look.
Don’t chase perfect scores for their own sake
Google says trying to get a perfect score just for SEO may not be the best use of your time. That’s good advice. A site that passes Core Web Vitals but has stale content, confusing navigation, weak calls to action, or poor trust signals still has work to do.
Use the metrics as a way to find friction. Then pair them with real business signals: conversions, scroll depth, form completion, assisted leads, repeat visits, and customer feedback.
Frequently asked questions
Is page experience a Google ranking factor?
Core Web Vitals are used by Google's ranking systems, and Google's page experience guidance is aligned with what those systems seek to reward. But there is no single page experience signal, and good scores do not guarantee top rankings.
Which Core Web Vitals should I track?
Track Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift. Google's recommended targets are LCP within 2.5 seconds, INP below 200 milliseconds, and CLS below 0.1.
Did INP replace FID?
Yes. Interaction to Next Paint replaced First Input Delay as the Core Web Vitals responsiveness metric on March 12, 2024.
Do I still need AMP for Top Stories?
No. AMP is no longer required for mobile Top Stories eligibility. Google still supports AMP, but eligibility is not limited to AMP pages.
Get new small business insights by email
Practical ideas and useful articles to help you make better business decisions.
Gabriel Nwatarali is the founder of Tech Help Canada and has worked in SEO, copywriting, and web strategy since the early 2000s. His work has helped drive more than 10 million app downloads and 2,900% organic traffic growth for startups, agencies, and brands across North America. He writes about SEO, marketing, AI, and the decisions that shape how businesses grow online, drawing on hands-on experience building websites, content systems, and digital strategies.
