The real cost of a slow website: What Core Web Vitals actually protect

How much is a slow website actually costing you?

Most websites nowadays solely rely on custom themes anyone can buy on theme forest or similar online shops to save time on development and money along with it, all in the quest to go live as soon as possible to make the business a reality. The problem is though that those bought themes are so heavy and slow it can actually have an impact on conversions.

Studies show that slow websites cost online retailers alone an estimated $2.6 billion in lost every year. And that is not a projection, it’s an aggregation of measured conversion losses, abandoned sessions, and suppressed organic traffic across thousands of retail properties. Most site owners miss that because it hides under the radar within multiple reports such as bounce rate, checkout abandonment data, and organic traffic declines that look unrelated.

This article will cover a single question most owners and performance guides skip: what is this costing me and the company, before asking what do I fix?

So what are Core Web Vitals?

In short, Core Web Vitals are Google’s metrics which show you loading speed, interactivity, and visual stability. These are not an abstract developer’s checklist.

It is a measurement layer both Google and users rely on to determine whether you want to stay on a website or leave. A Deloitte Digital study across 37 brands and more than 30 million sessions found that 0,1 second improvement in mobile load speed raised retail conversion rates by 8,4% and average order value by 9,2%. And those are real numbers which are reproducible.

What Core Web Vitals measure (and why Google made them official)?

Core Web Vitals or CWV in short, uses three metrics to help Google assess the real-world experience of loading, interaction, and navigation on the page:

1. Largest Contentful Paint (LCP) – measures loading performance e.g. how long it takes the largest visible content element to render
2. Interaction to Next Paint (INP) – measures the latency between a user’s input and the page’s visual response
3. Cumulative Layout Shift (CLS) – measures how visually stable the website is and does it move unexpectedly during and after load

Google’s thresholds are:

LCP	INP	CLS
Under 2.5 seconds	Under 200 milliseconds	Under 0,1

Common CWV misconceptions

The important thing to keep in mind is that what you measure on PageSpeed Insights and Lighthouse audits do not determine how CWV affects your rankings.

Google’s ranking systems use actual field data from real users visiting your actual pages using Chrome browser. Those field data aggregate into something called Chrome User Experience Report or CrUX in short. To put it simply, a perfect 100 in lab results means nothing if real users have completely different experience using very slow internet connections with 4 second LCP.

Have in mind that Google has committed to updating CWV metrics no more than once per year, with advance notice – meaning that businesses can plan and budget for those necessary changes so that a website can operate as optimally as possible.

The penalty gate: why “passing” CWV matters more than you think?

Most common framing of Core Web Vitals is that it is a “ranking boost” so, just to optimize for additional incremental SEO gains which could not have been more wrong. It is backwards. More accurate framing Is that: failing CWV imposes rank penalty, passing it removes the penalty, and exceeding the above-mentioned thresholds provides no additional benefits what’s o’ ever.

From the practical point of view, take a web page ranking with a set of keywords and backlink profiles etc. but with poor CWV. And then imagine another page with that exact same setup but the only difference is that it has a better CWV setup.

That another page will almost certainly win the tiebreaker against your page and rank better than you. And that not only affects that very page you are trying to rank, but it also affects the entire page as well. So, a domain with widespread LCP or INP failures doesn’t just lose individual rankings, it concedes grounds to competitors on every contested keyword where technical performance is the deciding factor.

LCP: the cost of a slow first impression

So, thinking about perceived loading speed, the first thing coming to our minds is the very first rendered element. That is usually a hero image, product photo, or above the fold text block. The main thing to remember is that the users do not experience milliseconds but whether a page feels sluggish or crisp and instant.

It is Google’s best single metric for that perception. So, the classification is as follows:

• Good – LCP is under 2,5 seconds
• Needs Improvement – LCP is between 2,5 – 4 seconds
• Poor – LCP is above 4 seconds

What does it mean in the real world? The conversion gap between those bands is not marginal. Google and Blue Triangle data show that product pages with a 2 second LCP see 40% – 50% higher conversion rates than pages loading at 4-5 seconds. Let’s say you own an ecommerce website generating approximately $10 million annually… that gap would be $4-5 million in revenue that is structurally unavailable due to the LCP being in a Poor band.

Vodafone Italy is a good example for this. Their 31% improvement in LCP produced an 8% increase in sales – that’s the actual revenue… not the conversion rate. So, moving from 4,2 seconds to 2,4 seconds puts you in a different category than moving from 2,4 to 2,1.

INP: the hidden cost of an unresponsive page

Before, there was First Input Delay (FID) measuring only the delay before the browser began processing user’s very first interaction. That later got replaced with much stricter Interaction to Next Paint (INP) as an official Core Web Vital. What INP does is it measures the latency of every interaction throughout a session – every tap, click, scroll, trigger, form input, form submission, etc. and it reports the worst performing one. This makes it more representative signal of how a given website or web application really behaves under use.

The results? Sites that have been confidently “passing” CWV for years may have been failing since March 2024 without realizing it. Pass rates on affected sites dropped from roughly 97% under FID to approximately 65% under INP.

INP is really hard to trace too because it never shows up in load-time dashboards. It, most commonly manifests as checkout button which does not work or lags significantly, a form that feels broken etc. These kinds of experiences users usually abandon and attribute the problem to the brand itself, not the browser.

CLS: when layout shifts quietly destroy conversions

Think of the case where a user goes to the website and then wants to tap into a link but fails to do so because it suddenly went down the screen because an image loaded above it. That is what CLS measures. How much visible content moves unexpectedly after the initial render.

CLS classification is as follows:

• Good – CLS is under 0,1
• Poor – CLS is above 0,25

The CLS issue is most prominent on ad supporting websites, but it is also relevant beyond ad supporting websites.

Rakuten 24 for example, did the A/B test where the optimized landing page saw CLS improve by 92.72% compared to the unoptimized version, alongside FID improving 7.95%, FCP improving 8.45%, and TTFB improving 18.03%.

The net result of all that effort was that their business saw a 53.37% increase in revenue per visitor, a 33.13% increase in conversion rate, a 15.20% increase in average order value, a 9.99% increase in average time spent, and a 35.12% reduction in exit rate.

Bear in mind that its betterment of the CLS led to the betterment of other CWV parameters as well so their business success cannot be attributed to the CLS alone as earlier mentioned Vodafone case can be with their LCP improvements.

Although CLS alone cannot be attributed to improving business results, it can be attributed to improving other important CWV metrics which can improve business performance.

CLS failures are also disproportionately damaging on mobile, where smaller viewports amplify shifts and smaller tap targets mean a misplaced element is more likely to cause the wrong touch. It depends on real asset loading sequences, network timing, and third-party scripts behaving as they do for actual users, which is the main reason the field data exist in the first place and why CLS almost never appears in developer test environments.

The mobile gap: Where does most of the revenue risk concentrate?

The majority of sites are actively penalized on mobile — the environment where most consumer search and ecommerce sessions now occur. Only 42% of mobile origins pass all three Core Web Vitals, compared to 63% of desktop origins.

Deloitte Digital’s research shows that when mobile load time increases people don’t just gradually leave, they hit a cliff and drop hard. At a load time of 1 – 3 seconds, bounce rate rises 32%, at 4 or more seconds, 63% of visitors leave before the page is useful and at 6 seconds two in three people leave and are gone.

It is always mobile first no matter what

For Google’s ranking systems, mobile CrUX data is what matters for mobile search results. A site that passes CWV on desktop but fails on mobile is still penalized. So, the desktop performance is irrelevant to how the page ranks for user’s phones.

Mapping the full cost: bounce rate, conversions, and organic traffic together

The costs of slow performance don’t stack linearly — they multiply. Three distinct mechanisms are operating simultaneously:

• direct conversion loss from slow or unstable pages,
• bounce rate escalation that reduces session depth and revenue per visit, and
• organic ranking suppression that reduces total traffic volume entering the funnel

Each degrades a different part of the revenue equation, and they compound. A site with poor CWV doesn’t just convert worse, it gets less traffic, converts a smaller share of that traffic, and extracts less value from each session.

Rakuten 24 did not just fix on CWV metric, called it a day and then saw business improvements. They went on optimizing all three metrics together which produced the multiplier effect which this entire article is all about.

Look at it this way: you get fewer visitors from ranking suppression, multiplied by a lower conversion rate from slow LCP and sluggish INP, multiplied by smaller average orders from poor mobile experience, which compounds into a revenue gap that dwarfs any individual metric’s contribution.

How to diagnose where your site is failing right now

The start of any CWV audit is in Google Search Console’s Core Web Vitals report which uses directly the field data from CrUX report we mentioned earlier in this article. This report is segmented by Good, Needs Improvement and Poor statuses separately for both mobile and desktop.

That is the only data source the reflects how Google’s ranking systems are currently evaluating your pages.

Using PageSpeed Insights is also possible but be careful to use it for informational purposes only… it does not aggregate all the URLs in one report. It can only do one URL at a time which can be misleading.

Also bear in mind that if your site passed all three Core Web Vitals before March 12, 2024, re-audit now because the FID to INP transition means your previous green status may not reflect current reality.

Building the internal case for core Web vitals improvement

Securing budget for performance optimization requires translating technical findings into commercial exposure.

The framework is straightforward:

1. Identify your current CWV status from GSC field data
2. Estimate the organic traffic volume at risk from ranking suppression on Poor-status URLs
3. Apply the conversion-rate lift estimates
4. Compare the projected revenue recovery against the cost of optimization.

The data points needed to populate that model are all in this article.

Core Web Vitals ultimately measure one thing: whether your site respects a visitor’s time. A page that loads slowly, jumps around, or lags on input loses people — quietly, with no exit survey to explain why.

Google didn’t invent this dynamic; it just gave it a scorecard. The business case for fixing Core Web Vitals is the same business case as not losing customers to friction that was fixable all along.

Need a hand closing that gap?

Vincta Solutions can audit your Core Web Vitals and run the optimization — get in touch and we’ll tell you exactly where the leak is.

FAQ