Core Web Vitals: Is your store losing sales before the page even loads?
A visitor clicks on your ad, lands on your store… and waits. One second, two seconds, three. Before your product even appears, they're gone, probably to a competitor. This isn't a hypothetical scenario: more than half of mobile visitors abandon a page that takes more than three seconds to load.
To measure this reality, Google created the Core Web Vitals: three simple indicators that score the real experience of your visitors. And they directly influence both your visibility on Google and your conversion rate. Here's what every e-commerce owner should know.
What are Core Web Vitals?
Core Web Vitals are three metrics that Google uses to evaluate the experience a page delivers to real users, not robots or simulations. A page is considered "good" when at least 75% of its visitors get a good experience, measured separately on mobile and desktop.
| Metric | What it measures | Good score |
|---|---|---|
| LCP (Largest Contentful Paint) | Loading speed: when the main element (often your product image) becomes visible | ≤ 2.5 s |
| INP (Interaction to Next Paint) | Responsiveness: how fast the page reacts when someone clicks or taps | ≤ 200 ms |
| CLS (Cumulative Layout Shift) | Visual stability: whether elements move around unexpectedly | ≤ 0.1 |
In plain terms, for an online store:
- LCP = how quickly the shopper sees your product.
- INP = how smoothly the "Add to cart" button, filters and menus respond.
- CLS = whether the button they were about to click suddenly jumps because a banner appeared.
Why it matters for your business
Your visibility on Google
Core Web Vitals are part of the signals Google uses to rank pages. Between two stores offering similar products with similar content quality, the faster one wins. And because Google evaluates mobile and desktop separately, and most e-commerce traffic comes from mobile devices, your mobile score is the one that really counts.
Your revenue
This is where the numbers get convincing. Companies that improved their Core Web Vitals have measured real business impact:
- Vodafone: +8% in sales after improving loading speed by 31%
- Cdiscount: +6% in revenue during Black Friday after improving all three metrics
- AliExpress: 15% fewer bounces after drastically improving visual stability
- Redbus: mobile conversion rate nearly doubled after fixing layout shifts and speeding up interactions
Performance is not a technical luxury; it's a sales lever.
What you risk with poor scores
Concretely, bad scores translate into very real frustrations for your customers:
- A customer taps "Add to cart", nothing happens for half a second, they tap again… and end up with two items in the cart (or just leave).
- They're about to tap a product, a promotional banner loads and pushes everything down, so they tap the wrong thing.
- On mobile, your category page takes five seconds to display anything. Half of your visitors never see your catalog.
How do you know where you stand?
Good news: measuring is free and takes five minutes.
- PageSpeed Insights (pagespeed.web.dev): enter a product page URL and get your scores instantly, based on real user data.
- Google Search Console: its Core Web Vitals report shows which groups of pages (home, categories, products) pass or fail, for mobile and desktop.
- Real User Monitoring: for deeper tracking, tools like the
web-vitalslibrary or Cloudflare tell you exactly which interactions are slow, on which pages.
One important rule: trust field data (real visitors) over lab tests. A perfect score in a test tool means nothing if your actual customers, on mid-range phones, are waiting four seconds.
How to improve: three levels of action
Level 1: Editorial: what you put on your pages
No developer needed, and often the quickest wins:
- Compress your images and use modern formats (WebP, AVIF). A product photo doesn't need to weigh 3 MB.
- Size your images to their display dimensions and avoid 4000-pixel-wide photos displayed at 400 pixels.
- Limit heavy banners, pop-ups and autoplay videos, especially at the top of the page.
- Always define image dimensions so the page doesn't jump while loading.
Level 2: Development: how your store is built
- The main product image should load first, with high priority and never lazy-loaded.
- Third-party scripts (chat, reviews, retargeting pixels, A/B testing) are the classic culprits: audit them, remove the ones you don't need, and load the rest after the essentials.
- Heavy interactions (filters, carousels, cart) should give instant visual feedback, even while the server responds.
- A regular clean-up of your tag manager prevents invisible slowdowns from accumulating over time.
Level 3: Infrastructure: where your store lives
- A CDN serves your pages from servers close to your visitors, reducing response time.
- Caching (including modern techniques like the back/forward cache and page prerendering) can make navigation feel instant.
- Your hosting and platform architecture set the ceiling: a slow server response penalizes every single page.
Frequently asked questions
What are Core Web Vitals and why should I care as a store owner?
Core Web Vitals are three metrics Google uses to score the real experience of your visitors: LCP (loading speed), INP (responsiveness) and CLS (visual stability). They matter because they influence both your visibility on Google and your conversion rate.
How do I know if my store's Core Web Vitals are good?
Use PageSpeed Insights (pagespeed.web.dev) for instant scores from real user data, or the Core Web Vitals report in Google Search Console to see which page groups pass or fail on mobile and desktop. A page is "good" when at least 75% of visitors get a good experience.
Can improving Core Web Vitals really increase my sales?
Yes. Vodafone saw +8% in sales after a 31% faster load, Cdiscount gained +6% revenue during Black Friday, AliExpress cut bounces by 15%, and Redbus nearly doubled its mobile conversion rate.
What are the most common causes of a slow store?
Heavy uncompressed images, oversized banners, pop-ups and autoplay videos, plus third-party scripts like chat, reviews, retargeting pixels and A/B tests. A slow server response also penalizes every page.
Do I need a developer to improve my Core Web Vitals?
Not always. Editorial fixes (compressing images, sizing them correctly, limiting heavy banners) need no developer and are often the quickest wins. Development and infrastructure changes do require technical work.
Should I trust lab tests or real user data?
Trust field data from real visitors over lab tests. A perfect score in a test tool means nothing if your actual customers, on mid-range phones, are waiting four seconds.
How often should I check my Core Web Vitals?
Treat performance as an ongoing discipline, not a one-time project: measure first, fix what matters most, and keep monitoring. A regular clean-up of your tag manager prevents invisible slowdowns from accumulating.
What do LCP, INP and CLS mean in practice for my store?
LCP is how quickly the shopper sees your product, INP is how smoothly the "Add to cart" button, filters and menus respond, and CLS is whether a button jumps because a banner appeared.
The bottom line
Core Web Vitals boil down to three questions your customers unconsciously ask: Does it load fast? Does it respond when I click? Does it stay put? If the answer to any of these is no, you're paying for traffic that leaves before buying.
The good news is that the most impactful fixes are well known and often simple. The key is to measure first, fix what matters most, and treat performance as an ongoing discipline, not a one-time project.
At Saphes, performance is built into every store we ship from day one. Curious about your own scores? Test a page. It takes less time than reading this article.
