Skip to content
Cloutions
Cloutions

Core Web Vitals: what they measure and how to improve them

5 min read

Core Web Vitals: what they measure and how to improve them

You open PageSpeed Insights, type in your website address and a few acronyms appear in red: LCP, INP, CLS. Is it serious? Does it affect your position on Google? Where do you start? The Core Web Vitals are three metrics Google uses to measure the real experience of people visiting your site: how long it takes to see the main content, how long the page takes to react when they tap something and whether elements move around while it loads.

Understanding them helps you set priorities, because not every recommendation the tools give you has the same impact, and some take a lot of work for very little result.

What the Core Web Vitals measure: LCP, INP and CLS

These are the thresholds Google publishes on web.dev:

MetricWhat it measuresGoodPoor
LCP (Largest Contentful Paint)How long it takes for the main element of the page to appear, usually a large image or a block of text.Up to 2.5 secondsOver 4 seconds
INP (Interaction to Next Paint)How long the page takes to respond on screen when the user clicks, taps or types.Up to 200 millisecondsOver 500 milliseconds
CLS (Cumulative Layout Shift)How much the elements of the page shift unexpectedly while it loads.Up to 0.1Over 0.25

Between "good" and "poor" lies the "needs improvement" band. To assess a page, Google looks at the 75th percentile of real visits: in other words, at whether at least three out of every four visits have a good experience. INP replaced the old FID, which only measured the first interaction; INP takes all of them into account.

Lab data and real-world data: they are not the same

PageSpeed Insights shows two blocks of information that are best not confused:

  • Real user data (the top section): comes from real visits made with Chrome over the last few weeks. This is what Google takes into account. If your site gets few visits, this block may not appear.
  • Lab diagnostics (the score from 0 to 100): a simulation on a mid-range mobile phone with a limited connection. It is useful for finding problems, but it is not what Google uses for ranking.

Google Search Console also has the Core Web Vitals report, which groups the URLs on your site that have similar problems. It is the best way to see which types of pages are failing, for example all the product pages or all the blog posts.

Do the Core Web Vitals affect rankings?

Yes, but with caveats. The Google Search Central documentation explains that its ranking systems take them into account, although the relevance of the content still carries more weight. A very fast site with weak content will not overtake a slower one that answers what the user is looking for better. When two results are evenly matched, the experience can tip the balance.

Where it always shows is in the business: a site that is slow to load, or that jumps around just as you are about to press a button, makes people leave or click the wrong thing.

How to improve LCP

  • A server that responds quickly. If the server is slow to reply, everything else arrives late. Good hosting and well-configured caching are the foundation.
  • An optimised main image. The large header photo is often the LCP element. Serve it in a modern format such as WebP or AVIF, at the right size for each screen and without lazy loading: lazy loading is useful for images further down, not for the first one.
  • Loading priority. Telling the browser that the image is a priority, with preload or the fetchpriority attribute, helps it arrive sooner.
  • Fewer blocking resources. Stylesheets and scripts loaded before the content delay everything. Remove the ones you do not need and defer those that are not required at the start.
  • Lightweight web fonts. Few font variants, loaded efficiently.

How to improve INP

INP gets worse when the browser is busy running JavaScript and cannot attend to the user. These are the most common causes:

  • Third-party scripts: chats, advertising pixels, maps, review widgets or tools that record sessions. Check which ones you really use and load the rest only when needed.
  • Heavy plugins and modules: visual builders, sliders and effects that add a lot of code for very little result.
  • Long tasks: functions that block the browser for too long. The technical fix is to split them into smaller parts or move them out of the moment of interaction.
  • Pages with too many elements: huge listings or very complex menus make every change on screen more expensive.

A practical way to find the culprit is to disable the third-party scripts one by one, on a test copy of the site, and compare the results. Often the problem is a tool installed a long time ago that nobody uses any more.

How to improve CLS

  • Always specify the width and height of images and videos, so the browser reserves their space before loading them.
  • Reserve space for ads, banners and elements that appear late, such as a promotions bar or the cookie notice.
  • Do not insert content above what the user is already reading.
  • Control how fonts load so the change of typeface does not shift the text.

The cookie notice deserves a separate mention: if it appears by pushing the content down instead of overlaying it, it can ruin the CLS of every page on the site at once.

Where to start if your site fails the Core Web Vitals

  1. Open the Search Console report and find out which groups of pages are failing and on which metric, starting with mobile.
  2. Pick a representative page from each group and analyse it in PageSpeed Insights.
  3. Fix first what depends on the template and not on a single page: a change to the product page template improves all the product pages at once.
  4. After each change, wait for real data to build up before treating the problem as solved, and use the option to validate the fix in Search Console.

If you want to go a step further, in our article on the new performance standards in web development we talk about how to build a fast website from the start.

Often Core Web Vitals problems come from how the site is built, not from a one-off setting. At Cloutions we tackle them from both SEO and web design and development at once. If your site is failing, tell us what PageSpeed is flagging and we will see where to start.

Frequently asked questions

Do I need to score 100 on PageSpeed Insights?

No. The score from 0 to 100 is a lab diagnostic; what Google takes into account is the real user data for the Core Web Vitals. It is better to pass all three metrics than to chase a perfect score.

Why does PageSpeed Insights give me different results every time?

Lab tests depend on server load, the network and the moment they are run, so they vary between runs. To make decisions, look at the real user data and the trend, not at a single test.

How long does Google take to reflect Core Web Vitals improvements?

Real-world data is calculated over several weeks of visits, so improvements show up gradually. In the meantime, you can follow progress in the Search Console report.

More articles

Our office

Where are we

Av. Bon Pastor 15 · 08380 Malgrat de Mar (Barcelona)

Get directionsGoogle Maps map