Performance Optimization: Core Web Vitals Explained
Google's Core Web Vitals measure real loading speed, interactivity, and visual stability: what each metric means and why scores affect rankings.
Fredy Rodriguez
Table of Contents
Core Web Vitals are Google’s three user-experience metrics that measure how fast your page loads, how quickly it responds to clicks, and whether the layout jumps around unexpectedly. They are a confirmed ranking factor, and they directly connect to whether visitors stay or leave.
This post breaks down what each metric measures, what scores you should aim for, and why the numbers matter to your business, not just your developer.
What Core Web Vitals actually measure
There are three metrics, each targeting a distinct part of the user experience.
LCP: how fast your main content loads
Largest Contentful Paint measures how long it takes for the biggest visible element on the page (usually a hero image, a large heading, or a video thumbnail) to fully render. This is the closest proxy for “when does the page feel loaded?”
A score of 2.5 seconds or under is “Good.” Between 2.5 and 4 seconds is “Needs improvement.” Over 4 seconds is “Poor.”
The most common LCP killers are large, unoptimized images, render-blocking JavaScript, and slow server response times. If your hero image is a 3 MB JPEG served without compression, your LCP is almost certainly in the red.
INP: how fast your page responds to interaction
Interaction to Next Paint measures how long it takes for the page to visually respond after a user clicks a button, taps a menu item, or fills in a form field. Google replaced the older First Input Delay metric with INP on March 12, 2024, because FID only captured the delay before the first interaction. INP tracks every interaction across the full visit, which gives a far more accurate picture of how the site actually feels to use.
A score of 200 milliseconds or under is “Good.” Between 200 and 500 ms is “Needs improvement.” Over 500 ms is “Poor.”
Poor INP typically points to JavaScript blocking the main thread. If your site runs several third-party scripts simultaneously (chat widgets, ad pixels, analytics), each one competes for the same processing time, slowing every tap and click.
CLS: how much your layout shifts unexpectedly
Cumulative Layout Shift measures whether content moves around on screen while the page is loading. A button that jumps down just as someone is about to tap it, a headline that shifts because a font loaded late, an image that expands and pushes everything below it: all of these contribute to a high CLS score.
A score of 0.1 or under is “Good.” Between 0.1 and 0.25 is “Needs improvement.” Over 0.25 is “Poor.”
CLS is one of the easiest metrics to fix on a technical level once you know it exists. The most common cause is images without declared width and height attributes, because the browser cannot reserve the correct space before the image downloads.
The thresholds that matter
Google measures all three metrics at the 75th percentile of page views, meaning your score needs to be in the “Good” range for at least 75% of your real visitors, not just the average.
| Metric | Good | Needs improvement | Poor |
|---|---|---|---|
| LCP | ≤ 2.5 s | 2.5 – 4 s | > 4 s |
| INP | ≤ 200 ms | 200 – 500 ms | > 500 ms |
| CLS | ≤ 0.1 | 0.1 – 0.25 | > 0.25 |
As of May 2026, 55.9% of websites pass all three metrics, according to Google’s Chrome UX Report. Mobile pass rates are lower at 48%, compared to 56% on desktop. That gap matters because most of your visitors are likely on phones.
Why these scores affect your rankings and your revenue
Core Web Vitals are a confirmed Google ranking signal. Two pages with identical content and backlink profiles will not rank identically if one passes all three metrics and the other does not. In competitive local markets, that difference is enough to push your listing below a competitor’s.
The business impact goes beyond rankings. 53% of mobile site visits are abandoned when a page takes more than 3 seconds to load. A Deloitte study commissioned by Google found that a 0.1-second improvement in mobile speed produced a 9.2% increase in average order value for retail sites and measurable progression-rate improvements across every step of the purchase funnel, as detailed in the Milliseconds Make Millions research.
For a Houston service business, this is direct. A visitor searching “HVAC repair near me” or “Energy Corridor accountant” decides within seconds. A slow site does not just lose the click; it loses the lead to whichever competitor loads faster.
The web design work we did for Motion Giraffx and Detail Exchange included passing Core Web Vitals thresholds as a stated delivery requirement, not an afterthought. Both rebuilds produced sites that load well under the LCP threshold on mobile.
Understanding what the development phase of your site produces in terms of CWV scores is part of building a site with SEO value from day one. The same principles that govern on-page optimization apply here too: Google’s ranking systems evaluate the full page experience, not just the content.
How to check your scores
PageSpeed Insights (pagespeed.web.dev) is the fastest starting point. Enter any URL and it runs a Lighthouse test plus surfaces any real-user field data Google has collected for that page. The report separates mobile and desktop scores and flags exactly which elements are failing each metric.
Google Search Console shows field data across your entire site. Under “Experience” in the left navigation, the Core Web Vitals report categorizes all your URLs into Good, Needs improvement, and Poor buckets. This is the data Google’s ranking systems actually use, since it reflects real visitors on real devices and connection speeds, not a simulated test.
The difference between lab data (PageSpeed Insights simulation) and field data (Search Console) can be significant. A page might pass the lab test but fail in field data because real visitors are loading it on slow mobile connections, not on a wired connection in an office.
Start with Search Console to see whether you have a systemic problem across many pages. Then use PageSpeed Insights on your worst-performing URLs to diagnose the specific causes.
Up next in this series: image optimization techniques, the single highest-impact lever for improving LCP scores.
If your site is failing Core Web Vitals and you want to understand what it would take to fix it, reach out and we’ll take a look. Our web design work includes performance-first development as a baseline, not an upgrade.
Frequently asked questions
What are Core Web Vitals?
Core Web Vitals are three Google metrics that measure real-world page performance: Largest Contentful Paint (loading speed), Interaction to Next Paint (responsiveness), and Cumulative Layout Shift (visual stability). They are a confirmed Google ranking factor and are measured using real visitor data collected in the Chrome UX Report.
Do Core Web Vitals affect SEO rankings?
Yes. Google officially confirmed Core Web Vitals as a ranking signal and surfaces them in Google Search Console and PageSpeed Insights. Pages that score “Good” across all three metrics have a measurable advantage over pages that score “Needs improvement” or “Poor,” particularly in competitive local markets where small differences in ranking position determine whether a visitor calls you or a competitor.
What replaced First Input Delay?
Interaction to Next Paint (INP) replaced First Input Delay (FID) as a Core Web Vital on March 12, 2024. Unlike FID, which only measured the delay before the browser first responded to a click or tap, INP measures the full response time for every interaction throughout a page visit, giving a more complete picture of how a site feels to use.
How do I check my Core Web Vitals scores?
Two free Google tools cover this. PageSpeed Insights (pagespeed.web.dev) runs a lab test and shows Lighthouse scores alongside any real-user field data available for your URL. Google Search Console shows field data aggregated across all your pages, broken down by “Good,” “Needs improvement,” and “Poor” URLs. Field data reflects what actual visitors experienced; lab data reflects a single simulated test run.

Technical Director & Co-Founder
Runs the data-and-code side of Desque: SEO, GEO, AEO, PPC, copywriting, and the engineering behind every site we ship. Builds in Go and TypeScript.
Continue in series: Performance Optimization
More from the blog
Related Posts

Code Splitting and Lazy Loading
Send only the code each page needs. Code splitting and lazy loading cut JavaScript bloat and make your site faster for real visitors on real connections.

Image Optimization Techniques
Cut page weight and improve load times by choosing the right image formats, compressing correctly, and delivering images the way browsers expect.

Web development in 2026: what actually changes for your Houston business
A practitioner-level look at which web trends require action now and which can wait, written for Houston SMB owners, not designers.