Core Web Vitals in Plain Language: LCP, INP and CLS Explained

Introduction

• Many site owners complain that their website is "slow" without knowing exactly what that means, and receive reports full of acronyms like LCP, INP and CLS that nobody explains.
• Core Web Vitals are a set of metrics that try to measure the real visitor experience: when do they see the content? Does the site respond when they tap? Do elements jump around while they read?
• This article explains each metric in plain language, which thresholds Google considers good, how to test your site, and what to fix first.

What are Core Web Vitals?

They are three metrics published by Google to measure page experience quality. They count as one signal among many, and they do not replace content quality or how well a page matches what the visitor is looking for.

Notes:

• These are the thresholds Google currently publishes, and metrics may evolve. Always check the current documentation.
• INP replaced the older FID metric. It is broader because it considers responsiveness across the whole visit.
• A page is usually assessed on most real user visits (not a single visit), with mobile and desktop reported separately.

Each metric in detail

LCP: how fast the main content appears

• The largest element is usually the hero image, a big heading or a video.
• Common causes of slowness: a huge uncompressed image, a slow server response, heavy fonts, CSS and JavaScript files that block rendering, or the main image loading late.
• What improves it: compressing images and using modern formats, setting their dimensions, not lazy-loading the first-screen image, faster hosting, and reducing what blocks rendering.

INP: responsiveness when someone interacts

• Poor INP shows when you tap a button or menu and nothing happens for a moment.
• Common causes: a lot of heavy JavaScript, plugins, tracking tools and chat widgets running in the background, and long tasks that block the page.
• What improves it: cutting unnecessary scripts, deferring third-party tools, breaking up long tasks, and removing what adds no value.

CLS: visual stability

• An annoying example: you go to tap a button, an ad appears suddenly and pushes it down, and you tap something else.
• Common causes: images, ads and videos without reserved dimensions, fonts that change text shape when they load, and banners or notices inserted above the content after load.
• What improves it: setting width and height for images and ad slots, reserving space for late elements, and handling font loading carefully.

How to test your site

Use Google's free tools, and know the difference between two kinds of data:

• Field data is closest to what Google uses to assess a page, but it needs enough visits. A small site may lack sufficient field data for a given page.
• Lab data helps find causes and test fixes, but may differ from your visitors' experience.
• Test mobile first. Most visitors browse on it, and performance there is harder.

A prioritised fix list

1. Compress images and resize them to fit where they display, using modern formats like WebP or AVIF where supported.
2. Set width and height on every image and video to avoid jumping (CLS).
3. Do not lazy-load the first-screen image; defer only what sits below.
4. Review plugins and scripts: remove tracking tools, chat widgets and plugins you do not use.
5. Use good hosting and caching, since server response time directly affects LCP.
6. Reduce fonts: a limited number of weights, with fallback text shown while loading.
7. Re-measure after each change so you know what actually helped.

What matters and what does not

• A perfect 100 in a testing tool is not the goal. The goal is a fast, stable experience for real visitors within the good thresholds.
• A slow site with excellent content may still show up, and a fast site with weak content gains nothing from speed. Speed supports content; it does not replace it.
• Speed affects conversion directly: a visitor who waits too long leaves before contacting you.

Common mistakes

• Relying on a single test and judging by it. Results vary from run to run.
• Ignoring mobile and checking only on desktop.
• Uploading camera-size images and shrinking them with CSS only.
• Adding tools (tracking, chat, pixels) without reviewing their effect on speed.
• Chasing the score at the expense of content and clear design.
• Fixing without measuring afterwards, so you never know whether anything improved.

What does Xposio do?

1. We measure the site using field and lab data together, with a focus on mobile.
2. We identify the cause of each weak metric (image, script, server, font) instead of giving generic advice.
3. We order fixes by impact and effort, starting with the easiest and most effective.
4. We build new sites with optimised images, reserved dimensions and limited scripts from the start.
5. We re-measure after implementation and show you what actually changed.
6. We are clear that improving Core Web Vitals improves experience and supports visibility, but does not guarantee a particular ranking.

Internal link: Learn about the Technical SEO service at /en/services/technical-seo and the Website Design & Development service at /en/services/website-design-development.

Also: order a Digital Snapshot report.

Related reading

• Mobile-first design
• SEO guide 2026
• Practical website speed

Conclusion

• Core Web Vitals are three metrics: LCP for loading, INP for responsiveness and CLS for stability.
• The published good thresholds are LCP up to 2.5 seconds, INP up to 200 milliseconds and CLS up to 0.1.
• Read field data first, use lab data to diagnose, and start with mobile.
• Most fixes are compressed images with set dimensions, fewer scripts and good hosting.
• They are one signal among many: relevant content comes first, then a fast experience, and no ranking is guaranteed.