Lyneon

Core Web Vitals for online shops: LCP, CLS and INP explained

Search Console reports “poor” or “needs improvement” for Core Web Vitals and you are not sure what to make of it? Here is what the three metrics mean, how to measure them and what usually holds shops back.

Updated · 5 min read

In short

  • Core Web Vitals are three metrics: LCP (loading of the main content, up to 2.5 s), CLS (page jumping, up to 0.1) and INP (response to clicks, up to 200 ms).
  • What counts is data from real visitors (CrUX, Search Console), not the lab score. The 75th percentile of visits is assessed.
  • In shops the usual causes are a heavy main image, third parties (ads, chat, tracking) and elements that load late and push the content.

Why bother

According to Google, Core Web Vitals measure user experience and are part of how a site is assessed in search. The practical effect matters more: a slow or jumping shop puts customers off exactly when they want to buy. On mobile it shows most.

Do not overestimate the link to rankings. A good score alone will not put you first; relevance of content still matters more. But poor values can be the deciding difference between two similar shops.

The three metrics and their thresholds

  • LCP (Largest Contentful Paint): how long until the largest element on the screen appears, usually the main image or the headline. Good: 2.5 seconds or less.
  • CLS (Cumulative Layout Shift): how much the content moves while loading. Good: 0.1 or less. The typical experience is clicking the wrong button because the page shifted.
  • INP (Interaction to Next Paint): how quickly the page responds to a click, tap or key press. Good: 200 milliseconds or less. INP replaced the earlier FID metric.

A page is rated good only when all three metrics meet the threshold at the 75th percentile of visits, separately for mobile and desktop. That means three quarters of real visits must be fast.

Field data and lab data

Field data comes from real Chrome users and is collected by the Chrome User Experience Report (CrUX). It reflects your visitors, their phones and connections. Lab data comes from a simulated test, for example in Lighthouse. It is good for finding causes and verifying changes, but it differs from reality.

A practical rule: field data decides whether you have a problem. Use the lab test to find out why. INP cannot be measured in the lab because nobody clicks in the test; Lighthouse shows Total Blocking Time as a substitute.

How to measure your shop

  1. PageSpeed Insights

    At pagespeed.web.dev enter the address of the home page, a category and a product. At the top you see field data for the last 28 days, below it the lab test. Switch between mobile and desktop. If field data is not available, the page does not have enough visits.

  2. Search Console overview

    In Google Search Console open the Core Web Vitals section. It shows how many URLs are good, need improvement or are poor, separately for mobile and desktop. URLs are grouped by similar pages, so fixing one template often fixes the whole group.

  3. Find the worst page type

    In a shop the problem is usually on one template, most often the product page or the category listing. Start where there are most visits.

  4. Find the cause in the lab test

    In the Diagnostics section of PageSpeed Insights or in Lighthouse you see the LCP element, the elements causing shifts and the scripts that block the main thread. After a fix, expect field data to improve only after a few weeks, as the measured visits turn over.

What slows shops down most often

The most common causes of slow loading of the main content (LCP):

  • The main image (banner, product photo) is too large, in an old format, or loads late (lazy loading on the first image).
  • Slow server response or no caching.
  • A slider that loads its scripts first and only then the first slide.
  • Fonts that block text from showing.

CLS and INP in practice

Page jumping (CLS) is caused by images without set dimensions, banners and cookie banners inserted above the content, ad or chat windows, and fonts that change text size on load. The fixes: image dimensions, reserved space for elements that load later, and a banner that overlays the content instead of pushing it down.

Slow response (INP) is caused by heavy JavaScript: many tags in the tag manager, third-party scripts, complex filters and product displays. It helps to limit the number of plugins, defer non-essential scripts and remove outdated tracking code.

What you can do yourself and when to call an expert

You can measure the state, shrink images, remove unused plugins and code, and cancel unnecessary tracking scripts yourself. Template changes, font loading, deferring scripts and server response are already technical work. For WooCommerce see WooCommerce speed. We measure the state, fix the biggest causes and send measurements before and after: from €200 excl. VAT, see shop speed.

Frequently asked questions

Why do values in PageSpeed Insights differ from Search Console?

PageSpeed Insights shows a lab test of one URL and field data for the last 28 days. Search Console groups URLs and shows values from real visitors. Field data decides.

What if no field data is available?

The page or site does not have enough Chrome visits for Google to publish it. Use the lab test as a guide and watch for when field data appears.

How long until a fix shows in Search Console?

The report works with data over a longer period, so improvement shows gradually, usually within a few weeks.

Order a free audit

Enter the shop address and your e-mail. We send the report in two working days. We use your details only to answer this request.

  • No access and nothing to install
  • The report is yours even if you order nothing
  • A person answers, not a bot
Add details(optional)

We use your details only to answer this request. Privacy policy