What Are Core Web Vitals?
Core Web Vitals are a set of standardized performance metrics Google uses to measure the quality of a user's experience on a webpage. They became official ranking factors in June 2021 as part of Google's Page Experience update. There are currently three metrics: Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS) — each measuring a distinct dimension of usability.
Largest Contentful Paint measures loading performance: how long it takes for the largest visible element on the page — typically a hero image, heading, or video — to fully load. Google's passing threshold is under 2.5 seconds. Interaction to Next Paint replaced First Input Delay in March 2024 and measures responsiveness: the delay between any user interaction (click, tap, keystroke) and the browser's next visible response. The passing threshold is under 200 milliseconds. Cumulative Layout Shift measures visual stability: how much page elements unexpectedly move during loading, which causes users to click the wrong thing. A CLS score under 0.1 is considered passing.
Google collects real-world CWV data from Chrome users through the Chrome User Experience Report (CrUX), then aggregates it at the URL and domain level. This means CWV scores reflect actual user experiences, not just lab tests — a page that performs well in testing but poorly on real devices and networks will still have failing scores.
Why Core Web Vitals Matter for Marketers
Google has confirmed CWV as a ranking signal, and failing pages are explicitly disadvantaged in competitive SERPs — particularly when competing content is of equivalent quality. The Page Experience signal functions as a tiebreaker: between two equally relevant pages, better CWV scores push you up.
Beyond rankings, the user impact is measurable. Google's research found that sites meeting Core Web Vitals thresholds see 24% fewer users abandoning page loads. For e-commerce, every second of load time correlates with a 7% reduction in conversions. Poor LCP means users don't see your product before they leave; poor INP means they can't interact with navigation or forms smoothly.
CLS has a specific UX harm: when page elements shift after initial load, users click unintended targets — ads instead of buttons, close buttons instead of links. This creates frustration, increases support requests, and reduces trust in the brand.
How to Implement Core Web Vitals
- Measure first: Use PageSpeed Insights, the Chrome DevTools Performance panel, and Google Search Console's Core Web Vitals report to identify failing URLs.
- Improve LCP: Optimize image sizes and use modern formats (WebP, AVIF). Preload hero images. Eliminate render-blocking resources that delay above-the-fold content. Use a CDN for static assets.
- Improve INP: Minimize long JavaScript tasks. Break up heavy computation with requestAnimationFrame or setTimeout. Reduce third-party script load on interaction paths.
- Improve CLS: Always set explicit width and height attributes on images and video embeds. Avoid inserting ads or banners above existing content after load. Use CSS transform for animations instead of layout-affecting properties.
- Test on real devices: Lab data from fast desktop connections is misleading. Test with Chrome's device emulation set to mid-range mobile and throttled connection to simulate real conditions.
- Monitor continuously: CWV scores can regress after design updates or new third-party scripts. Set up ongoing monitoring in Search Console and alert on failures.
How to Measure Core Web Vitals
Primary source: Google Search Console's Core Web Vitals report, which shows field data segmented by mobile and desktop, and lists URLs with "Poor" or "Needs Improvement" status. PageSpeed Insights provides per-URL field and lab data. The CrUX dashboard provides historical trend data.
Target: 75% or more of page loads should meet the "Good" threshold for all three metrics. Track your domain-level CWV pass rate monthly and after any major site updates.
Core Web Vitals and AI Search
While Core Web Vitals don't directly affect AI citation decisions, their indirect influence is real. AI crawlers — including those used by Perplexity's search infrastructure — need to successfully load and parse pages. Pages that are slow or unstable may be crawled incompletely, resulting in less content available for AI retrieval. More importantly, CWV-passing pages tend to rank higher in traditional search, where AI systems often source their retrieval results — making strong CWV a precondition for the broader visibility needed to be cited by AI-generated answers.