Core Web Vitals for Ecommerce: Which Ones Actually Move Conversion

For ecommerce, the Core Web Vitals that move conversion are the ones measured on real shoppers, on your money pages, on mobile. LCP decides whether product pages feel fast, INP decides whether add to cart and filters feel responsive, and CLS decides whether shoppers tap the right thing. Passing Google's thresholds is the floor, not the goal.

Core Web Vitals get treated as an SEO checkbox: pass the assessment, move on. For an online store that framing misses the point. Each metric describes something a shopper feels, and the gap between passing and performing well shows up in conversion long before it shows up in rankings.

Noibu is AI for ecommerce operations, the always-on optimization system that keeps online stores running at their best. A team of supervised AI agents finds what's broken, slow, or leaking revenue, does the work, and hands results back for human approval.

What are Core Web Vitals?

Core Web Vitals are three metrics Google uses to measure page experience: Largest Contentful Paint (LCP) for loading, Interaction to Next Paint (INP) for responsiveness, and Cumulative Layout Shift (CLS) for visual stability. Google rates a page as good when LCP is 2.5 seconds or less, INP is 200 milliseconds or less, and CLS is 0.1 or less, measured at the 75th percentile of real visits.

Do Core Web Vitals affect ecommerce conversion?

Yes, though the relationship is directional rather than a fixed formula. Slower, less stable pages lose shoppers, and the effect is strongest on mobile, where most ecommerce traffic now lands. Mobile accounted for 73.1% of ecommerce traffic during Holiday 2025, according to the Noibu Holiday 2025 Ecommerce Benchmark Report.

The size of the effect depends on the store, the page, and the shopper. As a planning benchmark, Noibu's 2025 BFCM Peak Season Playbook estimates that a 100ms increase in mobile load time is associated with roughly an 8 to 10% lower conversion rate. Treat that as a starting assumption to test against your own data, not a universal coefficient.

Those top-decile numbers are well inside Google's thresholds. That is the practical point: passing the assessment means a page is not failing, while the stores that convert best treat Google's limits as a floor.

Which Core Web Vital matters most for ecommerce?

The vital that matters most is the one failing on your highest-revenue template. In practice each metric tends to hurt a different part of the journey, which is why a single sitewide score hides the problem.

CLS deserves more attention than it gets. At Totally Bamboo, where one person runs all of direct-to-consumer, a CLS score that had been in the red since 2024 went from 0.53 to 0.02 with Noibu's agents running on the store. For more on how slow pages show up in revenue, see how to find slow pages hurting your ecommerce conversion.

How do you measure Core Web Vitals for an online store?

Measure Core Web Vitals on real users, split by page template and device, and tie each template to its revenue. Lab tools such as Lighthouse and PageSpeed Insights are useful for diagnosing a known slow page, but they test one simulated visit and often disagree with what shoppers experience.

1. Collect real-user data. Use real-user monitoring that captures LCP, INP, and CLS from actual sessions, including every browser and device mix your shoppers use.
2. Group by template. Report home, collection, product, cart, and checkout separately. A fast homepage can mask a slow product template that carries most of the revenue.
3. Split by device. Look at mobile and desktop separately; mobile almost always performs worse and carries more traffic.
4. Attach revenue. Pair each template with its sessions, conversion rate, and revenue, so you can see where speed is most likely costing orders.
5. Compare against your own best pages. Your fastest product pages are the most realistic target for the rest of the template.

How do you prioritize Core Web Vitals work?

Prioritize by revenue exposure: the sessions that hit the slow experience multiplied by the value of the page. That usually puts product page LCP and add-to-cart INP on mobile at the top of the list, ahead of homepage scores that leadership tends to look at first.

Noibu's Performance Agent works from real-user Core Web Vitals tied to sessions and revenue. It finds the templates and resources slowing shoppers down, drafts the change, and measures the result after a person approves it, so the before and after is a query rather than a meeting. Teams can run it from the Noibu console or from Claude through the Noibu plugin for Claude.

What usually causes poor Core Web Vitals on ecommerce sites?

The usual causes are third-party scripts, oversized images, and late-loading content. Review widgets, chat, personalization, A/B testing snippets, and tag managers add JavaScript that competes with the shopper's taps, which hurts INP. Uncompressed hero and gallery images hurt LCP. Banners, fonts, and widgets that load after the page renders cause CLS.

On Shopify, theme apps are a frequent source because each install can add scripts to every page. For platform-specific steps, see how to speed up your Shopify store.

Frequently asked questions

Related topics

• Noibu's Performance Agent
• How to find slow pages hurting your ecommerce conversion
• How to speed up your Shopify store
• How to do an ecommerce site audit
• Rage clicks: what they are and how to find them

See your real-user Core Web Vitals by page: run a free website audit →