Core Web Vitals for e-commerce: the speed fixes that matter most
What LCP, INP and CLS measure, the thresholds to aim for, and the practical fixes for images, apps, fonts and scripts that speed up a store on mobile.

- Aim for LCP of 2.5 seconds or less, INP of 200 ms or less and CLS of 0.1 or less
- Heavy images, too many apps and unreserved space cause most store speed problems
- Test on a mid-range phone and a slow connection, not only your laptop
Speed is part of the shopping experience and part of how search engines judge pages. Google's Core Web Vitals give three measures to aim for.
The three metrics
| Metric | Measures | Good |
|---|---|---|
| LCP (Largest Contentful Paint) | How fast the main content appears | 2.5 seconds or less |
| INP (Interaction to Next Paint) | How quickly the page responds to taps and clicks | 200 milliseconds or less |
| CLS (Cumulative Layout Shift) | How much the layout jumps around while loading | 0.1 or less |
These are measured for real visitors, at the 75th percentile, and are reported in Search Console and PageSpeed Insights.
Fix LCP: get the main image up fast
- Resize and compress images. Do not serve a 4,000-pixel photo to a phone. Use modern formats such as WebP where possible (photography guide).
- Do not lazy-load the main hero or product image, because it must appear immediately. Lazy-load images below the fold.
- Preload the key image or give it high priority.
- Use a CDN and caching, so that files arrive from nearby servers.
Fix INP: keep the page responsive
- Remove apps and scripts you do not use. Each one adds JavaScript that competes for the phone's processor.
- Delay non-essential scripts such as chat widgets and trackers until after the page is usable.
- Avoid heavy animations and big sliders.
Fix CLS: stop things jumping
- Set width and height on images and videos so space is reserved.
- Reserve space for banners and ads.
- Load fonts carefully so that text does not jump when the font arrives.
- Do not inject content above what the user is reading.
Third-party apps: the usual culprit
Review each one: reviews widgets, pop-ups, chat, trackers, upsell tools. Measure the page with and without them. Keep what earns its keep. Many stores speed up noticeably by removing three or four unused apps (hidden costs).
How to measure
- PageSpeed Insights shows lab and real-user data for a URL.
- Search Console's Core Web Vitals report shows groups of URLs that need work.
- A real mid-range Android phone on mobile data shows what many customers experience.
Test your home page, a collection page, a product page and the checkout.
Platform matters
A platform with lightweight themes, built-in image optimisation and few required apps starts faster. Ask about this when you choose (framework).
A one-week speed plan
| Day | Task |
|---|---|
| 1 | Run PageSpeed Insights on home, collection, product and checkout pages and note the worst metric on each |
| 2 | Resize and compress the largest images, and make sure the main image is not lazy-loaded |
| 3 | List every app and script, then remove or delay the ones you cannot justify |
| 4 | Add width and height to images and reserve space for banners |
| 5 | Retest on a mid-range phone with mobile data and compare with day one |
What to do next
Run PageSpeed Insights on your top product page. Fix the single largest problem it names, usually an oversized image or a heavy script, then test again.
Frequently asked questions
Do Core Web Vitals affect rankings?
They are one of many signals, and relevance matters more. They also affect conversion directly, because slow pages lose shoppers.
Why is my score good on my laptop and bad in the report?
Reports reflect real visitors on varied phones and networks. Test on a mid-range phone with mobile data.
How often should I check?
Check monthly, and also after any new app, theme change or large campaign page goes live, because those are the moments when a fast store most often becomes slow without anyone noticing.


