Core Web Vitals Meaning: LCP, INP & CLS Explained 2026

Key Takeaways

• Core Web Vitals are three Google-defined metrics that measure the real-world experience of loading, interacting with, and visually using your website.
• The three metrics are LCP (Largest Contentful Paint), INP (Interaction to Next Paint) and CLS (Cumulative Layout Shift).
• The "good" thresholds: LCP of 2.5 seconds or less, INP of 200 milliseconds or less, CLS of 0.1 or less, measured at the 75th percentile of page loads.
• Just over half of mobile sites fail at least one metric. In the HTTP Archive's 2025 Web Almanac, 48% of mobile websites had good Core Web Vitals, so passing is a real competitive edge.
• You can test your site for free using Google PageSpeed Insights and Google Search Console.

What Are Core Web Vitals? (The Short Answer)

Core Web Vitals are three performance metrics defined by Google that measure the loading speed, interactivity, and visual stability of a web page based on real user data. Google says its ranking systems use Core Web Vitals, as one part of overall page experience.

If you have heard the term but never understood what Core Web Vitals actually mean for a business owner, this guide is for you. We build our sites with these metrics in mind, and slow or jumpy pages are one thing worth ruling out when a site is slipping in search.

The Three Core Web Vitals Metrics

Each metric measures a distinct dimension of how a real user experiences your page:

1. LCP — how fast your main content loads
2. INP — how quickly your site responds when someone interacts with it
3. CLS — how stable your page layout is while it loads

Each has a defined "good," "needs improvement," and "poor" threshold — Google publishes the official Core Web Vitals thresholds on web.dev. Hitting "good" on all three is the goal: a page counts as passing when it meets the recommended targets at the 75th percentile of page loads for all three. Google also says good scores in these tools do not guarantee a top ranking.

LCP: Largest Contentful Paint

What it measures

LCP measures how long it takes for the largest visible element on the page — typically a hero image, a large heading, or a video poster — to fully render in the viewport. In plain terms: how quickly does the page look loaded to the person viewing it?

The thresholds

• Good: 2.5 seconds or less
• Needs improvement: over 2.5 and up to 4.0 seconds
• Poor: over 4.0 seconds

Why it matters

LCP is the metric users feel most directly. If someone clicks your link in Google and stares at a blank or partially-loaded page for three seconds, they are likely gone before they read a word. Google's 2017 research with SOASTA, reported in the Milliseconds Make Millions study, found that as page load time goes from one second to three seconds, the probability of bounce increases by 32%. In our own speed test of 556 UK trade websites on a simulated phone, the typical site took 6.7 seconds to show its main content, and 72% of the 489 we could speed-test (350) were over 4 seconds.

Common causes of poor LCP

• Large, unoptimised images (a JPEG that could be a WebP at a fraction of the size)
• Render-blocking JavaScript or CSS files loaded in the head
• Slow server response times or shared hosting under load
• Hero images that are not preloaded or prioritised
• Heavy third-party scripts running before your content

How we address it

Our brochure sites are built on Next.js, whose image component serves WebP by default and lazy-loads images by default. We also mark the hero image to load first. Fade-in animations on a hero image or heading can delay the moment it counts as painted, so as a rule of ours we keep them off the hero.

INP: Interaction to Next Paint

What it measures

INP replaced the old First Input Delay (FID) metric on 12 March 2024. Where FID only measured the delay before the browser started processing a click or tap, INP measures the full response time — from the moment you interact with something to when the browser paints the visual response.

It captures how the page responds throughout the entire user session, not just the first click, and takes the worst interaction as its representative score (with some outliers excluded).

The thresholds

• Good: 200 milliseconds or less
• Needs improvement: over 200 and up to 500 milliseconds
• Poor: over 500 milliseconds

Why it matters

A site that loads quickly but then feels sluggish when you click a menu, submit a form, or open a dropdown creates a poor impression — even if the page technically loaded fast. INP is Google's way of capturing that sluggishness.

Common causes of poor INP

• Long JavaScript tasks blocking the browser's main thread
• Heavy event listeners on interactive elements
• Bloated third-party scripts (chat widgets, analytics, advertising tags) running at interaction time
• React or other framework components with expensive re-renders
• Excessive DOM size making updates slow

How to improve it

The primary lever is reducing main thread work. This means code-splitting your JavaScript so only what is needed on a given page is loaded, deferring non-critical scripts, and auditing third-party tags. If you are running multiple marketing scripts — analytics, heatmaps, chat widgets — each one adds to the cost of every user interaction.

CLS: Cumulative Layout Shift

What it measures

CLS measures visual instability — how much your page layout shifts unexpectedly while it is loading. You have experienced this: you start reading an article, an ad loads above the text, and everything jumps down a few hundred pixels. That jump is a layout shift, and CLS reports the largest burst of layout shifts during the page's life.

The thresholds

• Good: 0.1 or less
• Needs improvement: over 0.1 and up to 0.25
• Poor: over 0.25

Why it matters

High CLS is genuinely irritating and can cause real problems — users clicking the wrong button because the layout jumped just as they tapped. It signals a poorly built page.

Common causes of poor CLS

• Images or video with no declared dimensions (width and height attributes)
• Ads, embeds, or iframes that load in and push content down
• Web fonts that load late and cause a font swap that reflows text
• Dynamically injected content (banners, cookie notices, chat widgets) that appear after initial load
• Animations that shift layout rather than transforming in place

How to fix it

Always declare explicit width and height on images and video elements. Use aspect-ratio CSS where needed. Preload critical web fonts and choose your font-display setting carefully: font-display optional avoids a re-layout, because the web font is only used if it has loaded in time. Ensure any injected content — including cookie consent banners — has reserved space, or slides in from outside the viewport rather than pushing content down.

How to Test Your Core Web Vitals

You do not need technical expertise to check your scores. Here are the main tools:

Google PageSpeed Insights

Visit pagespeed.web.dev and enter your URL. You will get both lab data (simulated in controlled conditions) and field data (real-user measurements from the Chrome User Experience Report, where available). Lab data is good for debugging; field data shows what real visitors experienced. CrUX field data comes from Chrome users who have opted in, over a 28-day sliding window.

Google Search Console

If your site is verified in Search Console, the Core Web Vitals report shows how your pages perform based on real-world usage data, split by mobile and desktop, with the URLs that have Poor or Needs improvement issues. It is the best view of your site's field data at scale. See the Search Console Core Web Vitals report help.

GTmetrix

GTmetrix provides a detailed waterfall chart of every resource loading on your page, making it useful for diagnosing specific bottlenecks — a particular image, a slow API call, or a render-blocking script.

Chrome DevTools

For developers, Chrome's Performance panel and Lighthouse audit (built into DevTools) allow granular diagnosis directly in the browser.

Why Core Web Vitals Matter for SEO

Google's documentation says its core ranking systems look to reward content that provides a good page experience, and that Core Web Vitals are used by its ranking systems. It also says Google Search always seeks to show the most relevant content, even if the page experience is sub-par, but that for many queries there is lots of helpful content available, so a great page experience can contribute to success in Search.

Google also recommends good Core Web Vitals for a great user experience generally, and its own guidance warns that chasing a perfect score purely for SEO may not be the best use of your time.

The mobile picture is worth knowing: in the 2025 Web Almanac, 48% of mobile websites had good Core Web Vitals, so just over half did not. That means many of your competitors are likely failing, and if you pass, you have a real edge.

What the Research Says About Speed and Revenue

Google does not publish how much weight Core Web Vitals carry in ranking, so be wary of any claim of a precise effect. The clearer evidence is about visitors and sales.

Google commissioned a study from Deloitte and 55, Milliseconds Make Millions (2020), covering 37 European and US brands. For retail, it found that a 0.1 second improvement in each of four mobile speed metrics went with an 8.4% increase in conversions and a 9.2% increase in average order value. Those metrics were load-time measures such as First Meaningful Paint and server latency, not the Core Web Vitals themselves. It also found a correlation across large brands, not a promise for a small site.

What Actually Moves the Needle

If you are a business owner without a developer on hand, here is where to focus energy:

If your site is more than three years old and has never been audited for performance, a professional website audit will give you a prioritised list of exactly what is hurting your scores and how to fix it.

If you are already with us on WebsiteCare, the Growth plan includes performance audits and the Premium plan includes ongoing performance optimisation. You can also read more about what goes into keeping a site running well in our website maintenance guide and our full website hosting and maintenance guide.

For businesses considering a new build or a site overhaul, our web design service is built around performance from the ground up — we build with speed, security and performance in mind.

What to Ask Your Web Developer

If you have read this guide and suspect your site has a Core Web Vitals problem, here are the specific questions to ask your developer or agency:

1. "What are our current Core Web Vitals scores on mobile?" — Not desktop. Mobile is what Google primarily uses for rankings.
2. "What is our LCP element and can it be optimised?" — This identifies the single biggest bottleneck in your page load.
3. "How many third-party scripts are running on our site?" — Every analytics tool, chat widget, and tracking pixel adds to INP delay.
4. "Are our images served in WebP/AVIF format with correct dimensions?" — This is the most common CLS and LCP fix.
5. "Is the site using a CDN?" — A Content Delivery Network serves your site from servers closer to your visitors. One of the cheapest performance wins available.
6. "When was our last performance audit?" — If the answer is "never" or "more than 6 months ago," that is your starting point.

If you do not have a developer relationship, our free mini website audit includes a mobile and speed snapshot, and our WebsiteCare Growth and Premium plans include performance audits and ongoing optimisation.

Frequently Asked Questions

Do Core Web Vitals directly affect my Google rankings?

Google says its ranking systems use Core Web Vitals, but there is no single page experience signal, and good scores do not guarantee a top ranking. Google also says it always seeks to show the most relevant content, even if the page experience is sub-par, while for queries with lots of helpful content a great page experience can contribute to success. Google has not published how much weight Core Web Vitals carry, and slow or unstable pages can still frustrate visitors whatever the ranking effect.

What is the difference between lab data and field data?

Lab data is generated by running automated tests under controlled conditions (simulated device, simulated network, no caching). Field data — also called real user monitoring — is collected from actual Chrome users visiting your site in real conditions. Field data comes from the Chrome UX Report, and it is what the Search Console Core Web Vitals report is built on. Lab data is more useful for diagnosing specific issues because you can reproduce it consistently.

INP replaced FID — does that mean my old scores are still valid?

Not directly. INP became an official Core Web Vitals metric on 12 March 2024, replacing First Input Delay. Your historical FID scores cannot be compared like-for-like with INP, as they measure different things. INP is a more demanding and more representative metric — some sites that had good FID scores find their INP scores need attention. Run a fresh audit against the current metrics.

My site passes on desktop but fails on mobile. Which matters more?

Both matter, but mobile performance is particularly significant. Google uses mobile-first indexing, meaning it crawls and evaluates your site primarily as a mobile user would experience it. Mobile field data is also often worse than desktop because of network conditions and device constraints. If you are only passing on desktop, treat the mobile failures as the priority.

How long does it take to fix Core Web Vitals?

As a rough guide of ours, not a guarantee, many small business sites can have most LCP and CLS issues fixed inside 1-2 weeks of focused work — image optimisation, removing render-blocking scripts, adding explicit dimensions. INP problems often take longer because they usually require auditing and reducing third-party JavaScript, which can mean trade-offs with marketing or tracking tools the business relies on. We scope this as part of a website audit.

Ready to Fix Your Core Web Vitals?

If your site is struggling with performance — or you have never checked your scores — now is the right time to find out where you stand.

Our free mini website audit gives you a high-level homepage review with a mobile and speed snapshot, and our full £149 audit (see pricing) gives detailed analysis across five review areas and a prioritised list of improvements.

Already have a site? Our WebsiteCare plans cover hosting, security and maintenance, and the Growth and Premium plans add performance audits and ongoing optimisation.

Related Reading

• Page Speed Optimisation: A Practical Guide for Business Websites
• How Website Speed Affects E-commerce Conversion Rates
• Web Design Trends 2026: What Actually Matters for Small Businesses
• Sustainable Web Design: How to Reduce Your Website's Carbon Footprint
• SEO for Small Businesses in the UK: Where to Start