Core Web Vitals in 2026: how to make your website load in under 2 seconds

A slow website loses visits before anyone sees its content, and Google also ranks it lower. Core Web Vitals are the metrics Google uses to measure the real experience of your users. This article explains them without jargon and gives the right order to improve them.

What Core Web Vitals are

Core Web Vitals are a set of metrics Google uses to measure the user experience of a page: how long it takes to show content, how quickly it responds to interaction, and whether elements move while loading. They are an official part of the ranking factors.

What matters is that they don't measure speed in a lab, but the real experience of your visitors on their own devices and connections. That's why they're so relevant: they reflect what the user actually feels.

The three metrics you need to know

LCP — Largest Contentful Paint

Measures how long it takes for the main element of the page to load (usually the large image or headline at the top). It's the 'perceived speed' metric. Target: under 2.5 seconds.

INP — Interaction to Next Paint

Measures how long the page takes to respond when the user interacts (a click, a tap). It replaced the old FID in 2024. Reflects whether the website 'feels smooth'. Target: under 200 milliseconds.

CLS — Cumulative Layout Shift

Measures how much elements move while the page loads. It's what causes you to try to tap a button and it shifts position. Target: under 0.1.

Why they matter for SEO and for conversion

Core Web Vitals work on two fronts at the same time. On one hand they are a ranking factor: all else being equal, Google prefers the faster website. On the other, they directly affect conversion.

The business impact is measurable: every second of load delay reduces conversion. A website that passes Core Web Vitals retains more visits, generates more contacts and ranks better. It's one of the few improvements that helps both SEO and conversion at the same time.

How to measure your website correctly

There are two types of data and it's important not to confuse them:

• Field data: the real experience of users (CrUX report). This is what Google uses for ranking. You can see it in Search Console, in the Core Web Vitals report.
• Lab data: a controlled simulation. This is what PageSpeed Insights or Lighthouse provides. Useful for diagnosing, but not exactly what Google measures.

1. Look at the Core Web Vitals report in Google Search Console to see the real status by URL groups.
2. Run key pages through PageSpeed Insights (mobile and desktop) to identify causes.
3. Always prioritise mobile: it's where most traffic is and where speed fails most.

Improvements in order of impact

Not all optimisations deliver equally. This is the order by effort-to-result ratio for a typical website:

1. Optimise images: convert to WebP, size correctly and use lazy loading. Usually the biggest LCP improvement.
2. Activate cache and a CDN to serve content closer to the user.
3. Reserve space for images and ads (define width and height) to eliminate CLS jumps.
4. Reduce and defer non-essential JavaScript, which is the main cause of poor INP.
5. Load web fonts in an optimised way so text appears sooner.
6. Remove third-party plugins and scripts that don't contribute to conversion.

Web speed checklist

• ✓All images in WebP and sized to their actual display size
• ✓Lazy loading on images outside the initial viewport
• ✓Browser cache and CDN active
• ✓Width and height defined on images and containers to avoid layout shifts
• ✓Third-party JavaScript reviewed and deferred where possible
• ✓Web fonts optimised with appropriate font-display
• ✓LCP under 2.5s on mobile
• ✓INP under 200ms
• ✓CLS under 0.1
• ✓Core Web Vitals report in Search Console showing green

Speed isn't a one-time project: every change to the website can affect it. It's worth reviewing regularly, especially after adding plugins, scripts or new sections.