When an eCommerce site is slow, the problem isn't just a low PageSpeed score. The problem is that the user waits, clicks and nothing happens, sees elements jumping around, loses confidence, goes back or abandons the checkout.
That is why Core Web Vitals should be read as signals of real experience, not as technical acronyms to delegate and forget. LCP, INP and CLS describe three different moments: when the page becomes visible, how well it responds to input, and how stable it stays while the user tries to use it.
For a brochure site they can be important metrics. For an eCommerce site they are even more delicate, because every bit of friction can cost orders, Ads budget and organic traffic.
Core Web Vitals: what they actually measure
Core Web Vitals are three metrics Google uses to assess central aspects of page experience:
- LCP, Largest Contentful Paint: measures how long it takes to display the main visible element on the page, for example the hero image, the product block or the main content;
- INP, Interaction to Next Paint: measures how responsive the page is when the user interacts with it, for example clicking a filter, a variant, the menu, the cart or the checkout;
- CLS, Cumulative Layout Shift: measures how much the layout moves unexpectedly while the page loads or while the user is working with it.
The official thresholds used as a reference are simple:
- Good LCP: within 2.5 seconds;
- Good INP: under 200 milliseconds;
- Good CLS: under 0.1.
But be careful: knowing the threshold isn't enough. The question for an owner is: which pages of my eCommerce site are failing, on which devices, and with what impact on sales?
eCommerce LCP: when the page seems not to start
LCP is about first impact. On a category page it may be the main image, the heading with the product listing or the block above the fold. On a product page it is often the product image or the main content. On an Ads landing page it may be the block that is supposed to convince the user to carry on.
If LCP is high, the user feels the page is slow even if other elements are technically loading. On mobile this matters enormously: someone arriving from Google, Shopping or Performance Max is not inclined to wait.
Frequent causes of high LCP on eCommerce sites:
- hero or product images that are too heavy;
- a slow server or undersized hosting;
- a theme loaded with CSS and JavaScript;
- badly loaded fonts;
- sliders above the fold;
- cookie banners and marketing scripts that slow down the start;
- categories with too many products or filters loaded immediately.
On an eCommerce site, improving LCP doesn't just mean compressing images. It means deciding what has to appear first and what can wait.
eCommerce INP: the site is visible, but it doesn't respond
INP is often the metric owners underestimate most, because the site can look loaded and still be awkward to use. You tap a filter and the page freezes. You click "add to cart" and you can't tell whether the command registered. You open the mobile menu and there is a delay. You select a variant and the price updates after a moment that feels too long.
On an eCommerce site, INP relates directly to the actions that lead to a sale:
- opening the menu and the internal search;
- category filters;
- variant selection;
- adding to the cart;
- changing quantities;
- coupons;
- checkout steps;
- choosing shipping and payment.
A page that is slow to respond creates doubt. And in the checkout, doubt is expensive: the user may click several times, assume the payment isn't working, or give up for fear of making a mistake.
eCommerce CLS: when everything moves while you are clicking
CLS measures unexpected layout shifts. It is that annoying feeling when you are about to click a product and a banner appears, an image loads and pushes the text down, a reviews box changes height, or the button moves precisely as you are tapping it.
On eCommerce sites it often happens because of:
- images without defined dimensions;
- promo banners loaded afterwards;
- intrusive cookie banners;
- fonts that change size on load;
- review, chat or payment widgets loaded late;
- prices, variants or availability that change the height of blocks;
- product cards not designed with stable dimensions.
A high CLS isn't just ugly to look at. It can produce mis-clicks, frustration and a loss of confidence, especially on a smartphone.
PageSpeed, Lighthouse and real-world data: they are not the same thing
Many people look only at the PageSpeed score and think they have the answer. Green good, red bad. In reality you need to distinguish at least two levels.
Lighthouse is a lab test: it simulates a visit under controlled conditions. It is extremely useful for diagnosing problems, but it doesn't always represent all real users.
CrUX and Search Console, on the other hand, use real-world data, when available, collected from Chrome users. This is where you can work out whether the problem really affects the site's audience, especially on mobile.
A serious eCommerce operation needs to read both:
- Lighthouse to understand what to fix;
- CrUX and Search Console to understand what real users experience;
- Analytics and order data to understand whether performance affects conversions and revenue.
The point isn't chasing a perfect number on the homepage. The point is working out whether categories, product pages, cart and checkout are fast enough to sell.
The pages to check first on an eCommerce site
A common mistake is testing only the homepage. But the homepage is often not the most important page for revenue. On an eCommerce site you have to start from the pages that receive traffic, take users to the cart or carry SEO value.
Recommended priority:
- main categories: because they capture commercial queries and SEO traffic;
- indexable filter pages: because they are often landing pages very close to purchase;
- bestseller product pages: because every slowdown affects direct sales;
- Google Ads landing pages: because every visit has a cost;
- the cart: because the user has already shown intent;
- the checkout: because here a delay can turn into a lost order;
- important brand pages: if they bring traffic and shape the catalogue.
We have already covered the subject in the post on a slow PrestaShop and its impact on SEO, Google Ads and conversions. The logic is the same: speed is not a technical line item, it is part of profitability.
Core Web Vitals and Google Ads: why the budget can burn faster
If you are paying for traffic, the page has to be ready to receive it. A campaign can be set up well, the feed can be tidy, the product can be competitive. But if the landing page is slow, unstable or unresponsive, part of the budget is lost before the user even evaluates the offer.
The problem is even more serious when the Ads report is never connected to page performance. You might think the campaign is bringing low-quality traffic, when the real problem is that the product page or the checkout doesn't hold up on mobile.
That is why an eCommerce audit has to cross-reference:
- Ads landing pages;
- Core Web Vitals by URL or template;
- mobile conversion rate;
- cart abandonment;
- checkout abandonment;
- average order value;
- margin and cost per acquisition.
Performance shouldn't be seen as "a nicer site". It should be seen as less friction between a paid click and a real order.
Core Web Vitals and SEO: being fast isn't enough, you need a clean structure
Speed helps, but on its own it doesn't rescue a disorganised catalogue. An eCommerce site can have good technical metrics and still lose opportunities if categories, filters, brands and product pages aren't well organised.
That is why Core Web Vitals should be read alongside SEO structure:
- clean URLs;
- light, crawlable categories;
- filters indexable only when useful;
- well-maintained brand pages;
- product pages with consistent content and structured data;
- a tidy sitemap;
- correct canonicals;
- optimised images.
Our custom platform exists precisely to hold these layers together: performance, architecture, SEO filters, brand pages, product pages and data for Google Ads. We have also covered this in the articles on eCommerce SEO filters and on eCommerce brand pages that sell.
What to ask your agency about Core Web Vitals
If they tell you "we've improved PageSpeed", don't stop there. Ask where, how and with which data.
- Are you looking at real CrUX/Search Console data or only Lighthouse tests?
- Are the metrics good on mobile or only on desktop?
- Which URLs are failing: homepage, categories, products, cart or checkout?
- Which template weighs most on revenue?
- Does high LCP come from images, the server, scripts or the theme?
- Does INP get worse when I use filters, the cart or the checkout?
- Is CLS caused by images, banners, fonts, widgets or unstable product cards?
- Have the Google Ads landing pages been tested individually?
- Have you measured the conversion rate before and after the work?
- Are the optimisations structural or just temporary compression?
A good audit doesn't just hand over a score. It hands over a priority: what to fix first because it genuinely affects traffic, Ads and orders.
A short practical checklist for an eCommerce owner
If you want a quick sense of where you stand, start here:
- open Search Console and check the Core Web Vitals report;
- separate mobile and desktop;
- identify the problematic URL groups;
- test a category, a product page, the cart and the checkout with PageSpeed Insights;
- check whether the images above the fold are too heavy;
- check whether the menu, filters and cart respond immediately on a smartphone;
- see whether banners, reviews, chat or cookies move page elements around;
- cross-reference the data with mobile conversion rate and abandonment;
- don't optimise the easiest page first: optimise the one that weighs most on the business.
If your site has many pages, a manual audit isn't enough. You need to think in terms of templates and URL groups: categories, brands, filters, product, cart, checkout. That is how you avoid fixing one demo page and leaving the rest of the catalogue slow.
How we handle it at BitHub
At BitHub we look at eCommerce performance within a wider picture: SEO, Ads, conversions, catalogue and technical structure. Our Green Web Audit was built precisely to bring together performance, page weight, resources, hosting, CO₂ and the data you need to see where to act.
When we work on a custom eCommerce site, the advantage is being able to work on the structure, not just apply patches. We can manage images, templates, filters, brand pages, product pages, cart, checkout and scripts with more control than in many systems weighed down by layered modules and themes.
The result shouldn't just be "100 on Lighthouse". The result should be a site that loads well, responds well, doesn't move while the user is buying, and helps Google read the pages that matter.
Useful sources
To dig deeper, you can start from the official documentation on Core Web Vitals, on the LCP, INP and CLS metrics, from the Google Search Central guide to page experience, and from the Lighthouse documentation on the performance score.
FAQs about Core Web Vitals for eCommerce
Which Core Web Vitals should an eCommerce site look at?
The three main metrics are LCP, INP and CLS. For an eCommerce site they should be read above all on mobile and on the pages that sell: categories, filters, product pages, cart, checkout and Ads landing pages.
Is a high PageSpeed score enough for SEO?
No. PageSpeed is useful, but it isn't enough. You need to look at real user data, SEO structure, indexable pages, content, structured data and above all the impact on conversions and revenue.
Why does INP matter in the checkout?
Because it measures the responsiveness of the page. If coupons, shipping, payment or buttons respond late, the user can lose confidence, click several times or abandon at the very moment closest to the order.
What causes a high CLS on an eCommerce site?
Images without dimensions, banners loaded afterwards, cookie banners, review widgets, chat, fonts and unstable product cards. Anything that moves the layout while the user is reading or clicking can increase CLS.
Is it better to optimise the homepage or product pages?
It depends on traffic and revenue. On many eCommerce sites it makes sense to start from categories, bestseller product pages, Ads landing pages, cart and checkout, because they are the pages closest to the sale.
Are Core Web Vitals and Google Ads connected?
Yes, because a slow or unresponsive landing page reduces the quality of the experience after the click. Even with well-built campaigns, a slow page can lower conversions and increase the real cost per order.