Skip to content

Ecommerce · 10 min read

Core Web Vitals Explained for Business Leaders: Speed, Rankings and Revenue

A plain-language guide to LCP, INP and CLS: what good looks like, how Google uses Core Web Vitals, the business evidence and a practical plan to improve them.

Close-up of a stopwatch on a black background
On this page 13 sections
  1. What Core Web Vitals are, in plain terms
  2. The thresholds: what “good” means
  3. How much do Core Web Vitals affect Google rankings?
  4. The business case: speed, engagement and revenue
  5. How Core Web Vitals are measured: field data versus lab data
  6. What usually causes poor scores
  7. A prioritized improvement plan
  8. Platform-specific considerations
  9. Common misconceptions to avoid
  10. Estimating the value before you invest
  11. Questions to ask your team or agency
  12. The bottom line
  13. FAQs

Core Web Vitals are three Google metrics that measure real users’ experience of a page: loading (Largest Contentful Paint), responsiveness (Interaction to Next Paint) and visual stability (Cumulative Layout Shift). Google uses them in its ranking systems, but relevance still comes first. Their bigger business value is fewer frustrated visitors and smoother paths to purchase or inquiry.

This guide explains each metric in plain language, what “good” looks like, how much they matter for search, what the evidence says about revenue, and how to prioritize fixes without turning your roadmap into an endless speed project.

What Core Web Vitals are, in plain terms

Core Web Vitals are part of Google’s Web Vitals initiative, which gives site owners a small, stable set of measurements for user experience. According to web.dev, each metric captures a distinct aspect of how a page feels to use:

  • Largest Contentful Paint (LCP) — how quickly the main content appears. Usually this is the hero image, a product photo or a large block of text.
  • Interaction to Next Paint (INP) — how quickly the page visibly responds when someone taps, clicks or types. Think of opening a menu, adding to cart or selecting a filter.
  • Cumulative Layout Shift (CLS) — how much content jumps around unexpectedly while the page loads, such as a button moving just as someone goes to tap it.

For a business leader, the simplest translation is: does the page show up fast, react instantly and stay still? If the answer to all three is yes for most of your real visitors, you’re in good shape.

The thresholds: what “good” means

Google publishes specific thresholds for each metric. They are assessed at the 75th percentile of page loads, separately for mobile and desktop — meaning at least three out of four visits need to hit the target, not just your fastest ones.

MetricMeasuresGoodNeeds improvementPoor
LCPLoading2.5 seconds or less2.5–4 secondsOver 4 seconds
INPResponsiveness200 milliseconds or less200–500 millisecondsOver 500 milliseconds
CLSVisual stability0.1 or less0.1–0.25Over 0.25

Thresholds are from web.dev’s Web Vitals documentation. A page passes the Core Web Vitals assessment when it meets all three at the 75th percentile.

One change leaders sometimes miss: INP replaced First Input Delay (FID) as a Core Web Vital on March 12, 2024. FID only measured the delay before the first interaction was handled; INP looks at responsiveness across interactions throughout a visit. Sites that looked fine under FID sometimes fail INP, particularly those heavy with JavaScript and third-party scripts.

How much do Core Web Vitals affect Google rankings?

Google is direct about this. Its Search Central documentation states that Core Web Vitals are used by its ranking systems, but also that there is no single page experience signal, and that Google Search “always seeks to show the most relevant content, even if the page experience is sub-par.”

In practice, that means:

  • Relevance and helpfulness come first. A fast page with thin content will not outrank a genuinely better answer because of speed alone.
  • Experience can be a differentiator. Google notes that where many pages are similarly helpful, a better page experience can contribute to success.
  • Assessment is mostly page-level. Google says its systems generally evaluate content on a page-specific basis, with some site-wide assessments.

Google’s Core Web Vitals documentation recommends site owners achieve good Core Web Vitals for success with Search and for a good user experience generally. Our view: treat Core Web Vitals as a hygiene factor for SEO and a genuine lever for conversion. Don’t expect a jump from “needs improvement” to “good” to transform rankings on its own. And if you’re investing in visibility in AI-driven search as well, our guide to generative engine optimization covers what else matters.

The business case: speed, engagement and revenue

The stronger argument for Core Web Vitals is commercial. Several published studies, all on specific sites, show measurable effects:

Two cautions keep these numbers honest. First, they are specific results from specific sites; your outcome depends on your audience, traffic mix and how slow you are to begin with. Second, many performance projects change several things at once, so attribution is imperfect. The Vodafone example is useful precisely because it isolated the change in an A/B test. Where you can, measure your own impact the same way.

Where most websites stand today

If your site doesn’t pass, you are in large company. The HTTP Archive’s 2025 Web Almanac, based on Chrome real-user data, reports that 48% of websites had good Core Web Vitals on mobile and 56% on desktop. On mobile, 62% had good LCP, 77% good INP and 81% good CLS.

Two practical conclusions follow. LCP is the metric most sites struggle with, so it is often the first place to look. And because roughly half of sites still don’t pass on mobile, getting there is a real competitive advantage in many categories, not just table stakes.

How Core Web Vitals are measured: field data versus lab data

This distinction causes more confusion in business conversations than anything else.

Field data (real users)Lab data (simulated)
SourceChrome User Experience Report (CrUX), your own real-user monitoringLighthouse, Chrome DevTools, PageSpeed Insights lab section
What it tells youWhat visitors actually experienced, across devices and networksHow a page performs in one controlled test run
Used by Google SearchYes — this is what the Search Console report reflectsNo — useful for diagnosis only
Best forDeciding whether you have a problem and whether fixes workedFinding causes and testing fixes before release

Google’s Search Console Core Web Vitals report is based on real-world usage data from CrUX and groups URLs with similar experiences together. When you mark an issue fixed, Search Console tracks it for 28 days to validate the fix. Low-traffic pages may not have enough data to appear individually.

A common mistake is chasing a Lighthouse score of 100. Lab scores help engineers diagnose issues, but INP in particular needs real interactions to measure; web.dev notes Lighthouse uses Total Blocking Time as a lab proxy for it. Report field data to leadership, and use lab tools in development.

What usually causes poor scores

Slow LCP

Google breaks LCP into four parts: server response time, the delay before the main image or text starts loading, how long it takes to download, and the delay before it renders. The web.dev LCP guide highlights common causes and fixes:

  • Slow hosting or uncached pages, which inflate time to first byte. A CDN and good caching help.
  • Hero images that are oversized, poorly compressed or discovered late by the browser.
  • Lazy-loading the main image — web.dev advises never lazy-loading your LCP image.
  • Render-blocking CSS and JavaScript that delay the page from painting.

Poor INP

Responsiveness problems usually come from too much JavaScript running on the browser’s main thread. The web.dev INP guide breaks each interaction into input delay, processing time and presentation delay. Typical culprits include tag managers loaded with marketing scripts, chat widgets, heavy page builders, very large DOMs and event handlers that do too much work at once.

High CLS

Layout shifts are usually caused by content that arrives without space reserved for it. The web.dev CLS guide lists images without dimensions, ads and embeds, late-injected banners, web fonts swapping in and animations that move layout. Cookie banners and promotional bars pushing content down are frequent offenders on business sites.

A prioritized improvement plan

A good plan starts from business priorities, not from whichever metric looks worst on a report.

  1. Identify the pages that matter. List the templates driving revenue or leads: home, category, product, landing pages, pricing, forms, checkout. Check their field data by mobile and desktop.
  2. Find the failing metric per template. Search Console and PageSpeed Insights show which metric fails and on which URL groups.
  3. Fix templates, not individual pages. One change to a product page template improves every product page at once.
  4. Audit third-party scripts. Every tag, pixel, widget and personalization tool has a cost. Remove what nobody uses, delay what isn’t needed at load, and assign an owner to each script.
  5. Ship and verify with field data. Deploy fixes, then confirm the improvement in real-user data rather than assuming a lab score reflects reality.
  6. Put guardrails in place. Set performance budgets, test in your release process and monitor real users so regressions are caught early.

Platform-specific considerations

The fixes available depend heavily on how your site is built.

WordPress and page builders

Themes and builders often load large amounts of CSS and JavaScript on every page, and plugins add more. Performance plugins help with caching and image optimization, but lasting improvement often means reducing plugins, simplifying templates and controlling which scripts load where.

Hosted ecommerce platforms

On hosted platforms you control less of the infrastructure, so apps and themes become the main levers. Each app that injects scripts into the storefront can affect INP and LCP; review them with the same discipline as marketing tags. Our ecommerce transformation work often starts with exactly this kind of audit.

JavaScript-heavy and headless sites

Single-page applications and headless builds can be very fast, but only if rendering strategy is right. Client-side rendering can delay LCP, and large bundles hurt INP. Server-side rendering or static generation for key pages, code splitting and careful hydration usually matter more than micro-optimizations.

Common misconceptions to avoid

  • “We need a perfect score.” The goal is passing thresholds for real users on the pages that matter, not a 100 in Lighthouse.
  • “Speed will fix our rankings.” Google is clear that relevance leads. Core Web Vitals support good content; they don’t replace it.
  • “Desktop is fine, so we’re fine.” Mobile and desktop are assessed separately, and mobile is where most sites fall short.
  • “It’s a one-time project.” New features, campaigns and scripts erode performance constantly. Without monitoring and budgets, scores drift back.
  • “Performance is only an engineering problem.” Marketing tags, content choices, design decisions and vendor tools all affect Core Web Vitals, so ownership needs to span teams.

Estimating the value before you invest

Performance work competes with every other item on your roadmap, so it helps to size the opportunity before committing budget. You don’t need industry averages to do this; your own data is more relevant.

  1. Segment conversion by experience. In your analytics or real-user monitoring tool, compare conversion rate, bounce rate and revenue per session for visits with good versus poor load and responsiveness. The gap is not proof of cause, since slower visits often come from weaker devices or networks, but it shows where friction and value overlap.
  2. Focus on high-value templates. A slow product or checkout template usually matters far more than a slow blog archive. Multiply each template’s traffic by its conversion value to rank where improvements could matter most.
  3. Run a controlled test where you can. As the Vodafone example shows, splitting traffic between an optimized and a baseline version gives a far more reliable read on impact than a before-and-after comparison affected by seasonality and campaigns.
  4. Count the non-revenue benefits. Removing unused scripts and simplifying templates often reduces maintenance effort, vendor costs and risk. These benefits are real even when conversion effects are hard to isolate.

This approach keeps the conversation about business outcomes rather than scores, and it gives you a baseline to report against after changes ship. It also connects naturally to broader growth work: speed is one input into conversion alongside messaging, offers, trust and usability, and it is most effective when improved as part of that bigger picture rather than in isolation.

Questions to ask your team or agency

If you’re a leader overseeing this work, these questions keep it grounded:

  • What share of our key templates pass all three metrics on mobile in field data?
  • Which metric is failing, on which templates, and what is the root cause?
  • Which third-party scripts do we load, who owns each one and what does it cost in performance?
  • How will we measure the business impact of improvements — ideally with a controlled test?
  • What stops performance from regressing after launch?

Performance is also a core part of any rebuild. If you’re planning one, factor it into the specification from day one; our guide to redesigning without losing rankings covers the SEO side of that transition.

The bottom line

Core Web Vitals give you a clear, Google-endorsed definition of a fast, responsive and stable page: LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less, for at least 75% of real visits. They are one of many ranking signals rather than a shortcut to the top, but published case studies show they can move engagement and sales. Focus on the templates that drive revenue, measure with real-user data and keep third-party scripts under control.

If you’d like help diagnosing and improving your site’s performance, explore our Web & Digital Experience services or get in touch.

Sources

FAQ

Questions, answered.

What are the three Core Web Vitals?

The three Core Web Vitals are Largest Contentful Paint (LCP), which measures loading of the main content; Interaction to Next Paint (INP), which measures how quickly the page responds to clicks, taps and typing; and Cumulative Layout Shift (CLS), which measures unexpected movement of content while the page loads and is used.

What is a good Core Web Vitals score?

Google's recommended thresholds are LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less. They are assessed at the 75th percentile of page loads, separately for mobile and desktop, so at least three in four real visits need to meet each target for a page to pass.

Are Core Web Vitals a Google ranking factor?

Google's Search Central documentation says Core Web Vitals are used by its ranking systems, but that there is no single page experience signal and that Google always seeks to show the most relevant content, even if page experience is sub-par. Treat them as supporting good content rather than a substitute for it.

What replaced First Input Delay in Core Web Vitals?

Interaction to Next Paint (INP) replaced First Input Delay (FID) as a Core Web Vital on March 12, 2024. FID measured only the delay before the first interaction was handled, while INP considers responsiveness across interactions during a visit, which makes it a stricter and more complete measure of how responsive a page feels.

Why is my PageSpeed Insights score different from Search Console?

PageSpeed Insights shows both field data from real Chrome users and a lab test from Lighthouse, which simulates a single page load. Search Console reports field data grouped across similar URLs. Lab scores vary with test conditions and are best for diagnosis, while field data reflects what real visitors experienced.

How long does it take for Core Web Vitals improvements to show?

Field data reflects real visits over time, so improvements appear gradually rather than immediately after deployment. When you start validation for an issue in Search Console's Core Web Vitals report, Google tracks it over a 28-day period to confirm the fix. Low-traffic pages may not have enough data to show individually.

What most often causes poor Core Web Vitals?

Common causes include slow server response and uncached pages, oversized or late-loading hero images, render-blocking CSS and JavaScript, heavy third-party scripts such as tags and chat widgets, large page builders, and images, ads or banners that load without reserved space and push content around.

Do Core Web Vitals affect sales and conversions?

Published case studies suggest they can. Vodafone's A/B test found a 31% LCP improvement led to 8% more sales, and a Google-commissioned Deloitte study linked small speed gains to higher retail and travel conversions. Results vary by site, so measure your own impact, ideally with a controlled test.

Have something ambitious in mind?

Tell us where you are and where you want to be. We'll come back with honest thinking on how to get there.