Core Web Vitals for Ecommerce: Speed That Moves Revenue

Core Web Vitals are the three metrics Google measures on real visitors: Largest Contentful Paint for loading, Interaction to Next Paint for responsiveness, and Cumulative Layout Shift for visual stability. The passing thresholds are the speed levels at which measured stores sold more: LCP within 2.5 seconds, INP at 200 milliseconds or less, CLS at 0.1 or less. Vodafone recorded 8 per cent more sales from a single LCP improvement, and Rakuten 24 lifted revenue per visitor by more than half. For an ecommerce store, these are revenue thresholds, not a technical score.

Most store owners judge speed by loading their own homepage on the office wi-fi. Your customers are on a three-year-old phone on a shopping-centre 4G connection, and that is the experience Google measures. The gap between those two experiences is where carts get abandoned. It is measurable, fixable and directly tied to what the store earns.

What are the Core Web Vitals thresholds an ecommerce store needs to hit?

There are three thresholds, and all of them are assessed on real-user data. Google’s guidance is that LCP should occur within 2.5 seconds of when the page first starts loading, that pages should have an INP of 200 milliseconds or less, and that pages should maintain a CLS of 0.1 or less (web.dev). A store passes when it meets all three for most of its real visitors, not on a single lucky test run.

On a product page those abstractions become concrete. LCP is usually the product image: the moment the thing being sold becomes visible. INP is the delay between tapping add-to-cart and the interface responding. CLS is the page shuffling as banners and review widgets load in, which is how a customer aims at the checkout button and hits a promo tile instead.

How much revenue does hitting the thresholds actually move?

The strongest evidence comes from A/B tests on live stores, where speed is the only variable. Vodafone ran one on a landing page and found that a 31% improvement in LCP led to 8% more sales (web.dev). Rakuten 24’s investment in Core Web Vitals increased revenue per visitor by 53.37% and conversion rate by 33.13% (web.dev).

“Thanks to the collaboration with Google and the introduction of LCP as the main KPI for page performance, it was possible to significantly improve the customer experience of our e-commerce.”

Davide Grossi, Head of Digital Marketing, Vodafone (web.dev)

Treat those numbers as evidence of the mechanism, not a promise of your result. They are controlled tests on stores that started slow; a store that already loads quickly will gain less. The direction, though, is consistent across every published test we have seen: when the page gets faster, more of the same visitors buy.

Which metric should a store fix first?

LCP first. It carries the clearest revenue evidence and is usually the cheapest metric to improve. Most ecommerce LCP problems come down to oversized images, heavy theme code or render-blocking scripts from installed apps. CLS comes second, because layout shift causes misclicks at the exact moment a customer is trying to buy. INP matters most on app-heavy themes where every tap fights the scripts already running.

The fixes are unglamorous. Serve product images in modern formats, sized to the container they sit in. Never lazy-load the hero image. It is the LCP element, and deferring it is self-sabotage. Audit installed apps quarterly: every widget you added in a promo three years ago still loads its script on every page today. Reserve fixed space for banners and review widgets so nothing jumps while a customer reads. This is the same speed budget we hold our own website builds to, because retrofitting speed always costs more than building with it.

Should you trust lab scores or field data?

Field data decides and lab data diagnoses. Core Web Vitals compliance is assessed on what real visitors experienced, judged at the 75th percentile of page loads, segmented across mobile and desktop devices (web.dev). A lab tool simulates one visit on one device. Use it to find causes, never to declare victory. A green lab score on your laptop proves nothing about the phone your customer is holding.

Practically, that means two places to look: the Core Web Vitals report in Google Search Console, which shows how real visitors experienced your pages, and the field-data section at the top of a PageSpeed Insights report. Check the templates where the money lands: product and collection pages. That is where paid and search traffic typically arrives, and a fast homepage hides a slow product page.

When is more speed work not worth paying for?

Once all three metrics are green for most real visitors, further speed spending buys little. Past the thresholds the returns diminish: the next hundred milliseconds costs more to remove and moves less revenue. At that point the constraint has moved elsewhere: the offer, the product photography, a shipping cost that surprises people at checkout. If speed is not your store’s problem, that is what we would tell you.

The sequence for an owner is short. Pull the field data, fix LCP on the templates that take the revenue, strip the app bloat, reserve space for everything that loads late, then re-measure a month later. After that, the levers worth pulling look more like what a high-converting site needs beyond raw speed: clarity, proof and a reason to act now. This is also where our ecommerce build work starts: measure first, then spend where the measurement points.

Speed bonds with everything else the store already pays for. Ads land on pages that convert better, emails click through to pages that hold attention, and the same traffic produces more orders. Those gains compound. If you want your store measured honestly against these thresholds, start a conversation or see how we scope the work.

Frequently asked questions

What is a good Core Web Vitals score for an ecommerce site?

A store passes Core Web Vitals when its real visitors experience Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint at 200 milliseconds or less, and Cumulative Layout Shift at 0.1 or less. The assessment uses field data from actual visits, judged at the 75th percentile, so most of your customers, not a single test run, must get the fast experience.

Do Core Web Vitals actually affect ecommerce conversion rates?

Yes, and the evidence is A/B-tested rather than anecdotal. Vodafone found a 31 per cent improvement in Largest Contentful Paint produced 8 per cent more sales, and Rakuten 24’s Core Web Vitals work lifted revenue per visitor by 53.37 per cent and conversion rate by 33.13 per cent. Faster pages convert more of the same visitors; the size of the lift depends on how slow the store was to begin with.

How do I check my store’s Core Web Vitals?

Use the Core Web Vitals report in Google Search Console for the store-wide picture, and the field-data section of a PageSpeed Insights report for a single URL. Both show real-visitor data rather than a simulated test. Check product and collection page templates rather than only the homepage, because that is where search and paid traffic typically lands, and where a slow page costs actual orders.

Do I need a full rebuild to pass Core Web Vitals?

Usually not. Most failing stores get to green by compressing and correctly sizing images, removing or deferring unused app scripts, keeping the hero image out of lazy-loading, and reserving layout space for late-loading widgets. A rebuild is only the answer when the theme itself is the bottleneck: heavy, old and resistant to surgery. Measure first; the field data tells you which situation you are in.