Core Web Vitals are three performance metrics Google uses to measure real user experience on your website: Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift. Pages that fail these metrics rank below pages that pass them when other signals are equal. This guide explains what each metric measures, what passing and failing scores look like, and the specific fixes that improve each one.
Google has measured page speed as a ranking factor since 2010. Core Web Vitals, introduced as a formal ranking signal in 2021, made that measurement more specific. Rather than using a single speed score, Core Web Vitals break user experience on a webpage into three distinct measurements: how quickly the main content loads, how quickly the page responds to user interaction, and how stable the layout is as the page loads.
For business owners, the practical implication is that a slower, less stable version of your page can rank below a faster, more stable competitor’s page even if your content is more thorough and your site has stronger links. Performance is not a tiebreaker. It is a direct ranking input. A technical SEO audit that does not include Core Web Vitals assessment is missing one of the most actionable ranking factors available to fix.
Largest Contentful Paint, abbreviated as LCP, measures the time from when a page begins loading to when the largest visible content element within the viewport finishes rendering. This is typically a hero image, a large above-the-fold block of text, or a video thumbnail.
LCP is the most direct measurement of how quickly users perceive a page as loaded. A page that renders its main content quickly feels fast, even if background processes are still running.
An LCP of 2.5 seconds or less is rated Good. Between 2.5 and 4 seconds is Needs Improvement. Above 4 seconds is Poor.
Slow server response times, render-blocking resources such as large JavaScript or CSS files, images that are not optimised or are significantly larger than needed, and large images without pre-loading instructions.
For most small and medium business websites, LCP failures are caused primarily by unoptimised hero images and slow server response times. Google’s PageSpeed Insights tool identifies the specific LCP element on any page and provides recommendations for the root causes of delays.
Interaction to Next Paint, abbreviated as INP, replaced the older First Input Delay metric in March 2024. INP measures the latency of all user interactions with a page throughout its full lifetime, including clicks, taps, and keyboard inputs.
A page that responds slowly to clicks and taps feels broken to users. Slow interaction responsiveness typically indicates that the main thread of the browser is occupied by JavaScript tasks.
An INP of 200 milliseconds or less is rated Good. Between 200 and 500 milliseconds is Needs Improvement. Above 500 milliseconds is Poor.
INP is the newest of the Core Web Vitals and the one that many websites are most likely to fail without being aware of. Web.dev’s INP documentation provides technical detail on diagnosing and resolving INP issues.
Cumulative Layout Shift, abbreviated as CLS, measures the total amount of unexpected layout movement that occurs during the loading of a page. It captures instances where elements visually shift position after they have already appeared.
Layout shifts are among the most frustrating experiences users have on slow-loading pages. A user reading a paragraph that shifts down as an image loads above it has a poor experience regardless of how fast the page loaded overall.
A CLS score of 0.1 or less is rated Good. Between 0.1 and 0.25 is Needs Improvement. Above 0.25 is Poor. Unlike LCP and INP, CLS is a dimensionless score rather than a time measurement.
There are two types of Core Web Vitals data: lab data from automated testing tools, which simulates a page load in controlled conditions, and field data from real users who have visited your pages, which reflects actual performance across varied devices and connections.
Google uses field data, not lab data, as its ranking signal. Field data for your site is available in Google Search Console under the Core Web Vitals report. This report shows which pages have Poor, Needs Improvement, and Good scores based on real user data collected over the previous 28 days.
For businesses managing full-service digital marketing across multiple page types, monitoring Core Web Vitals at the template level is more efficient than page-by-page review.
Core Web Vitals are one component of a broader technical SEO health picture. A site with perfect Core Web Vitals scores but crawl errors, duplicate content, or schema markup errors is still underperforming relative to its potential.
The technical vs. on-page SEO breakdown on the Whissel Strategies blog explains how these different SEO layers interact. Core Web Vitals sit within the technical layer, meaning they affect the conditions under which all on-page and content work produces results.
Most small and medium business websites have at least one failing Core Web Vitals metric. The good news is that the majority of failures are caused by a small number of fixable issues: unoptimised images, render-blocking scripts, missing image dimensions, and slow server response times.
A technical SEO audit that includes Core Web Vitals assessment identifies exactly which metrics are failing on which page types, what is causing each failure, and the prioritised fixes that will produce the fastest improvement.
To find out how Core Web Vitals failures are affecting your rankings, book a free strategy call and get a performance assessment backed by a clear remediation plan.
Core Web Vitals are a confirmed ranking factor but not the dominant one. Content relevance, link authority, and on-page optimization carry more weight in most ranking decisions. However, when content quality and authority are equal between competing pages, Core Web Vitals can be the differentiating factor.
Yes. Google evaluates Core Web Vitals separately for mobile and desktop versions of pages. Most sites have lower performance scores on mobile than on desktop. Since Google uses mobile-first indexing, the mobile Core Web Vitals scores have more influence on rankings.
Core Web Vitals field data is based on real user interactions aggregated over a 28-day rolling window. A performance improvement made today will take up to 28 days to fully reflect in the field data. Rankings typically begin improving within two to eight weeks of scores moving from Poor to Good.
PageSpeed Insights shows lab data for a single test under controlled conditions. Google Search Console shows field data from real users across varied devices and connections. Search Console field data is what Google uses for ranking, so it is the more important dataset to focus on.
Some improvements are manageable without development expertise, such as installing a caching plugin on WordPress or compressing images before uploading. The most impactful fixes, including deferred JavaScript loading and server-level optimisations, typically require developer involvement.
Most ranking factors are difficult to influence directly. Core Web Vitals are not. They are the result of decisions made in code, on your hosting environment, and in your asset management practices. Those decisions are changeable. A site that fails Core Web Vitals today can pass them within a development sprint, and the ranking benefit of that improvement is measurable and sustained. Book a free strategy call to get started.
Core Web Vitals measure how real users experience your website. Whissel Strategies helps Canadian businesses track, analyze, and improve these metrics to boost rankings and engagement. Book a free strategy call to see how optimizing Core Web Vitals can grow your business.
Book a 30 minute growth call, where Bailey Whissel will personally assess your business, identify challenges and goals, and create a customized one-page growth plan.
