PERFORMANCE

EN — 2026

LCP, INP and CLS: how to genuinely improve Core Web Vitals

Fixing one metric while breaking another is not a real performance gain.

← Back to all notes

PERFORMANCE

LCP, INP and CLS: how to genuinely improve Core Web Vitals

06 October 20268 min readWYN Studio

Core Web Vitals measure three different user experiences: how fast the main content appears, how the page responds to interaction, and whether the page jumps while loading. Fixing one while breaking another is not a real performance gain.

LCP: when does the main content arrive?

LCP is usually the hero image, large heading or main content block. Reducing server response time, delivering critical CSS early, sizing the large image correctly and cutting unnecessary third-party requests are the first checkpoints.

INP: what happens after the click?

INP tries to understand how fast the interface responds after the user clicks, taps or uses the keyboard. Long JavaScript tasks, large DOM updates and animations that occupy the main thread are felt here.

CLS: why does the page jump?

Images without reserved dimensions, late-arriving banners and fonts that change metrics shift the layout. Giving image and ad areas their size from the start reduces the shifts that happen before the user even reads.

Lab and real-user data

Lighthouse gives fast feedback during development; real-user data shows different devices, networks and usage patterns. Reading both together avoids the mistake of generalising a good result from a powerful computer.

Source / further readingWYN working approachThis article does not copy the original content of the source; it is WYN’s practical interpretation. For current headlines, check the publication date and the source page separately.