---
title: "Core Web Vitals Explained: LCP, INP and CLS in 2026"
description: "Core Web Vitals explained for 2026: learn how LCP, INP and CLS shape page experience and improve website performance."
image: https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Nov-15-2026-03-08-20-3607-PM.jpeg
---

[![BlazingCDN](https://blog.blazingcdn.com/hubfs/Logo/blog-logo-w.png)](https://blog.blazingcdn.com?hsLang=en-us)

[📘 Learn ▾](https://blog.blazingcdn.com/cdn-learn?hsLang=en-us)

[CDN Fundamentals](https://blog.blazingcdn.com/cdn-fundamentals?hsLang=en-us) [By Content Type](https://blog.blazingcdn.com/by-content-type?hsLang=en-us) [Advanced Concepts](https://blog.blazingcdn.com/advanced-concepts?hsLang=en-us) [📖 Glossary](https://blog.blazingcdn.com/glossary?hsLang=en-us)

[🎬 Video & Streaming ▾](https://blog.blazingcdn.com/video-streaming-cdn?hsLang=en-us)

[🔴 Live Streaming](https://blog.blazingcdn.com/live-streaming?hsLang=en-us) [📺 VOD & OTT](https://blog.blazingcdn.com/vod-ott?hsLang=en-us) [🎞️ Encoding & Players](https://blog.blazingcdn.com/encoding-players?hsLang=en-us) [🎧 Audio & Podcasts](https://blog.blazingcdn.com/audio-podcasts?hsLang=en-us) [💰 Bandwidth & Costs](https://blog.blazingcdn.com/bandwidth-costs?hsLang=en-us)

[🏗️ Infrastructure ▾](https://blog.blazingcdn.com/cdn-infrastructure?hsLang=en-us)

[🗄️ Storage & Origin](https://blog.blazingcdn.com/storage-origin?hsLang=en-us) [📦 Large File Delivery](https://blog.blazingcdn.com/large-file-delivery?hsLang=en-us) [💸 Cloud Costs & Egress](https://blog.blazingcdn.com/cloud-costs-egress?hsLang=en-us) [🌐 Networking & ISP](https://blog.blazingcdn.com/networking-isp?hsLang=en-us) [⚙️ DevOps & Cloud Infra](https://blog.blazingcdn.com/devops-cloud-infra?hsLang=en-us) [⚡ Web Performance](https://blog.blazingcdn.com/web-performance?hsLang=en-us)

[🏭 Industries ▾](https://blog.blazingcdn.com/cdn-industry-insights?hsLang=en-us)

[📺 Media & Broadcasting](https://blog.blazingcdn.com/media-broadcasting?hsLang=en-us) [💾 Software & SaaS](https://blog.blazingcdn.com/software-saas?hsLang=en-us) [📣 AdTech & Advertising](https://blog.blazingcdn.com/adtech-advertising?hsLang=en-us) [🎮 Gaming & Esports](https://blog.blazingcdn.com/gaming-esports?hsLang=en-us) [📱 Mobile Apps & Developers](https://blog.blazingcdn.com/mobile-apps-developers?hsLang=en-us) [🤖 AI & Machine Learning](https://blog.blazingcdn.com/ai-machine-learning?hsLang=en-us) [🏛️ Enterprise & Corporate](https://blog.blazingcdn.com/enterprise-corporate?hsLang=en-us) [📚 E-Learning & EdTech](https://blog.blazingcdn.com/e-learning-edtech?hsLang=en-us) [🏟️ Sports & Live Events](https://blog.blazingcdn.com/sports-live-events?hsLang=en-us)

[💰 Pricing & Compare ▾](https://blog.blazingcdn.com/cdn-pricing-and-cdn-costs?hsLang=en-us)

[Provider Pricing](https://blog.blazingcdn.com/provider-pricing?hsLang=en-us) [Cost Optimization](https://blog.blazingcdn.com/cost-optimization?hsLang=en-us) [Decision Support](https://blog.blazingcdn.com/decision-support?hsLang=en-us) [⚡ Compare](https://blog.blazingcdn.com/cdn-comparison?hsLang=en-us) [Provider Comparisons](https://blog.blazingcdn.com/provider-comparisons?hsLang=en-us) [Strategy Comparisons](https://blog.blazingcdn.com/strategy-comparisons?hsLang=en-us) [📊 Benchmarks](https://blog.blazingcdn.com/cdn-ratings-and-benchmarks?hsLang=en-us)

[🔒 Security ▾](https://blog.blazingcdn.com/cdn-security?hsLang=en-us)

[Attack Protection](https://blog.blazingcdn.com/attack-protection?hsLang=en-us) [Encryption & Access](https://blog.blazingcdn.com/encryption-access?hsLang=en-us) [Video & DRM Security](https://blog.blazingcdn.com/video-drm-security?hsLang=en-us)

[🛠️ Tools](https://blog.blazingcdn.com/cdn-tools?hsLang=en-us)

[Get Started](https://blazingcdn.com/sign-up-contact-form/)

[Web Performance](https://blog.blazingcdn.com/en-us/tag/web-performance) [Infrastructure](https://blog.blazingcdn.com/en-us/tag/infrastructure)

# Core Web Vitals Explained: LCP, INP and CLS in 2026

 Vadym Borovskyi  Nov 15, 2026, 4:10:27 PM

![\<span id="hs\_cos\_wrapper\_name" class="hs\_cos\_wrapper hs\_cos\_wrapper\_meta\_field hs\_cos\_wrapper\_type\_text" style="" data-hs-cos-general-type="meta\_field" data-hs-cos-type="text" \>Core Web Vitals Explained: LCP, INP and CLS in 2026\</span\>](https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Nov-15-2026-03-08-20-3607-PM.jpeg)

Core web vitals are three field metrics Google uses to score real-user page experience: Largest Contentful Paint (LCP) for loading, Interaction to Next Paint (INP) for responsiveness, and Cumulative Layout Shift (CLS) for visual stability. A page passes when, at the 75th percentile of real Chrome visits, LCP is 2.5 seconds or less, INP is 200 milliseconds or less and CLS is 0.1 or less. This playbook takes about two hours: pull field data, instrument real-user monitoring, find the worst subpart of each metric and ship the fixes that move it. Expect up to 28 days before the public field data fully reflects the change.

As of November 2026, Google's Core Web Vitals are LCP, INP and CLS, with "good" thresholds of 2.5 seconds, 200 milliseconds and 0.1, each evaluated at the 75th percentile of page loads in Chrome User Experience Report (CrUX) field data. INP replaced First Input Delay as the responsiveness metric in March 2024.

## **What LCP, INP and CLS measure in Core Web Vitals**

LCP measures when the largest image or text block in the viewport finishes rendering. INP measures the slowest typical delay between a click, tap or key press and the next frame painted, across the whole visit. CLS sums unexpected layout shifts inside the worst session window: shifts grouped while each comes within 1 second of the previous one, with the window capped at 5 seconds.

All three metrics are assessed separately for mobile and desktop, and a page or origin passes only when all three are good at the 75th percentile. One quarter of your visits can be bad and you still pass. That is why fixing your own fast laptop run proves nothing.

| Metric | Good | Poor | Lab proxy | Subparts to debug |
| --- | --- | --- | --- | --- |
| LCP | 2.5 s or less | over 4 s | Lighthouse LCP | TTFB, resource load delay, resource load duration, element render delay |
| INP | 200 ms or less | over 500 ms | Total Blocking Time | input delay, processing duration, presentation delay |
| CLS | 0.1 or less | over 0.25 | Lighthouse CLS (load only) | shifting element, shift source, timing relative to input |

INP has no direct lab equivalent, so a page can score well in Lighthouse and still fail in the field.

## **Prerequisites before you start**

- Access to Google Search Console for the property, or the origin URL to query in PageSpeed Insights.
- A way to ship a small JavaScript bundle to production and collect beacons (any analytics endpoint or a log pipeline).
- Chrome with DevTools, using the Performance panel and its live metrics view.
- Control over response headers at your origin or CDN, and over the HTML templates for your top page types.

## **How to test Core Web Vitals and fix them: the steps**

1. **Read field data per template, mobile first.** Open the Core Web Vitals report in Search Console, which groups URLs by similar pages, then check representative URLs in PageSpeed Insights under the field section. Why: CrUX is a 28-day rolling window at the 75th percentile, and it is what Google uses for page experience. Lab scores are for debugging only.
2. **Instrument real-user monitoring with attribution.** Add the open-source web-vitals library in its attribution build and register its LCP, INP and CLS callbacks, sending the value, the rating, the page template and the attribution object to your endpoint. Why: attribution tells you the LCP element and its four subparts, the INP interaction target and its phases, and the element behind the largest shift. Without it you are guessing.
3. **Find the LCP element and give it priority.** Remove the **loading** attribute set to lazy from any image that can become the LCP element, and set its **fetchpriority** attribute to high. If the image is a CSS background or is injected by JavaScript, move it into the HTML as a normal image element so the preload scanner discovers it. Why: resource load delay is often the largest avoidable LCP subpart.
4. **Shrink the LCP resource.** Serve the hero at the rendered width using the **srcset** and **sizes** attributes, in AVIF or WebP. If your LCP image is a desktop-sized original sent to phones, BlazingCDN's on-the-fly [**image processing for LCP-sized hero images**](https://blazingcdn.com/image-processing/) (crop, resize, resizefit, resizefill) is included at no extra charge and returns the variant from the edge. Why: load duration scales almost linearly with bytes on constrained mobile links.
5. **Cut TTFB with cacheable HTML.** For fingerprinted assets, set **Cache-Control** to a **max-age** of 31536000 seconds (one year) with **immutable**. For HTML that can tolerate brief staleness, set **s-maxage** to 60 seconds and **stale-while-revalidate** to 300 seconds so the edge answers while it refreshes. Where your stack supports it, send a **103 Early Hints** response with preload or preconnect link headers for critical CSS and fonts. Why: Google's optimization guidance gives TTFB roughly 40% of the LCP budget, and a cache miss to a distant origin can consume all of it.
6. **Break up long tasks for INP.** In the Performance panel, record a slow interaction and find tasks over 50 ms. Split event handlers so the visual update runs first and the rest yields via the **scheduler.yield** method (with a timeout-based fallback in browsers without it). Defer non-critical third-party tags until after load or first interaction. Why: input delay and processing duration are main-thread problems, not network problems.
7. **Reserve space for everything that loads late.** Give every image and video explicit **width** and **height** attributes or a CSS **aspect-ratio**, and give ad slots, embeds and consent banners a fixed **min-height**. For web fonts, use **font-display** set to optional, or match the fallback with **size-adjust** and **ascent-override** descriptors. Animate with **transform**, never top or left. Why: CLS counts shifts not triggered by a user input within 500 ms.
8. **Keep pages eligible for the back/forward cache.** Remove unload event handlers and avoid **Cache-Control** set to no-store on pages that do not hold sensitive data. Why: a bfcache restore paints instantly, which improves LCP and CLS on every back navigation at no engineering cost beyond the cleanup.

## **A worked LCP budget for a mobile hero image**

The 2.5 second LCP threshold is a budget you split across four subparts. Google's guidance suggests roughly 40% for TTFB, under 10% for resource load delay, roughly 40% for resource load duration and under 10% for element render delay.

| LCP subpart | Share | Budget at 2,500 ms | First fix if over |
| --- | --- | --- | --- |
| Time to First Byte | about 40% | 1,000 ms | Cache HTML at the edge, stale-while-revalidate, 103 Early Hints |
| Resource load delay | under 10% | 250 ms | Image in HTML, fetchpriority high, no lazy loading |
| Resource load duration | about 40% | 1,000 ms | Right-size, AVIF or WebP, same-origin delivery |
| Element render delay | under 10% | 250 ms | Smaller render-blocking CSS, fewer blocking bundles |

Load duration and TTFB own 80% of the budget, so bytes and cache hits decide most LCP outcomes.

Now the arithmetic. Lighthouse's default mobile throttling simulates about 1.6 Mb/s of throughput with 150 ms of round-trip time. A 200 KB hero is 1.6 megabits, so its transfer alone takes about 1,000 ms and spends the entire load-duration budget before a single round trip is counted. Re-encode it to an 80 KB AVIF at the rendered width and transfer drops to about 400 ms, freeing roughly 600 ms for a slow TTFB. This is our estimate from the throttling profile, not a field measurement, but it explains why image weight is the first lever on mobile LCP.

## **Validation: which metrics to read and what good looks like**

Validate in three layers. Locally, the DevTools Performance panel shows live LCP, INP and CLS as you interact, and expected values on a throttled mobile profile are LCP under 2.5 s, CLS under 0.1 and no single interaction above 200 ms. In your RUM data, read the 75th percentile per template and device class, not the mean.

- LCP attribution: TTFB plus load delay plus load duration plus render delay should sum to the LCP value, with no subpart above its budget from the table.
- INP attribution: the interaction target and its processing duration should both be visible. Processing duration under 100 ms usually leaves room for presentation.
- CLS attribution: the largest shift target should not be an image, ad slot or font-swapped text block after the fixes.
- Response headers: check that HTML responses carry **Cache-Control** with the s-maxage you set and that your CDN's cache status header reports a hit on repeat requests.

Finally, watch the CrUX numbers in PageSpeed Insights over the following 28 days. Because the window rolls, your fix shows up gradually, roughly a quarter of the effect per week.

## **Rollback plan**

Ship each fix as a separate deploy behind a flag or a template change you can revert alone. Keep RUM running before and after, and compare the 75th percentile per template over at least 7 days of traffic. If a change regresses another metric (a preload that delays CSS, for example), revert that single change instead of the batch. Header changes at the edge are the fastest to revert: restore the previous cache rule and purge HTML.

## **Why Core Web Vitals fixes fail: symptom, cause, fix**

- **LCP got worse after adding preloads.** Cause: preloading fonts, CSS and several images makes them compete for the same bandwidth. Fix: preload only the LCP resource and one critical font, and use fetchpriority on the single LCP image.
- **Lighthouse is green, field INP is poor.** Cause: Lighthouse does not click anything, and real users hit heavy handlers on menus, filters and consent dialogs. Fix: rank interactions by RUM INP attribution and profile the top three targets.
- **CLS is good on load but poor in the field.** Cause: shifts after load from infinite scroll, late ads or lazy-loaded components without reserved space. Fix: reserve dimensions and insert new content below the viewport.
- **TTFB varies widely by country.** Cause: HTML is uncacheable, so every request crosses to a single origin region. Fix: cache anonymous HTML at the edge with short s-maxage and stale-while-revalidate, and bypass the cache only for session cookies.
- **Nothing changed in Search Console after a week.** Cause: the 28-day window plus URL grouping. Fix: trust your RUM trend and wait the full window before validating the fix in the report.

## **Tuning once the page passes, and the trade-offs**

Once all three metrics are green, tighten rather than add. Use **content-visibility** set to auto on long below-the-fold sections to cut rendering work, which helps INP on large DOMs. Consider prerendering likely next pages with the Speculation Rules API for near-instant LCP on navigation, at the cost of extra origin and CDN traffic for pages users never open.

Every fix has a price. Inlining critical CSS cuts render delay but defeats caching of that CSS across pages. Font-display set to optional removes font-swap shifts but some first-time visitors see the fallback font for the whole visit. Yielding inside handlers lowers INP but adds scheduling overhead and can reorder side effects, so test analytics and state updates after splitting tasks. Edge-cached HTML lowers TTFB but needs a purge path for content changes. More on this tuning work lives in the [**web performance articles on page experience**](https://blog.blazingcdn.com/web-performance?hsLang=en-us).

## **FAQ: Core Web Vitals in practice**

### Are Core Web Vitals a Google ranking factor in 2026?

Yes, Core Web Vitals remain part of the page experience signals Google uses in ranking. Google describes them as one factor among many, and relevance of the content still outweighs them. In practice, passing helps most when competing pages are otherwise similar, while poor scores mainly cost conversions and engagement from slower, less stable pages.

### What is a good INP score for Core Web Vitals?

A good INP score is 200 milliseconds or less at the 75th percentile of page loads, and anything above 500 milliseconds is poor. INP reports a near-worst interaction from each visit, so a single heavy menu or filter handler can fail the page even when most clicks respond quickly. Debug it with field attribution, not lab tests.

### Why does Lighthouse show a different LCP than Core Web Vitals field data?

Lighthouse runs one synthetic load on a fixed throttled profile, while Core Web Vitals field data aggregates 28 days of real Chrome visits at the 75th percentile. Real users bring different devices, networks, cache states and geographies. Use Lighthouse to reproduce and debug a problem, and use CrUX or your own real-user monitoring to judge it.

### How long does it take for Core Web Vitals fixes to show in Search Console?

Core Web Vitals fixes take up to 28 days to show fully, because CrUX field data is a rolling 28-day window. Improvements appear gradually as older page loads age out. Search Console also groups similar URLs, so a fix applied to one template may take time to move a group's status. Real-user monitoring shows the trend within days.

### Does a CDN improve Core Web Vitals scores?

A CDN mainly improves LCP, by lowering TTFB and resource load duration through edge caching, compression and nearby delivery. It does little for INP, which depends on main-thread JavaScript work, and nothing for CLS, which depends on layout. The biggest CDN gain usually comes from caching anonymous HTML, not only static assets.

## **Measure your LCP subparts this week**

Deploy the web-vitals attribution build on your three highest-traffic templates and log LCP subparts, INP targets and CLS sources for seven days. Then compute the 75th percentile of each LCP subpart per template on mobile and compare it with the 1,000 / 250 / 1,000 / 250 ms budget above. The subpart furthest over budget is your first fix. If it is TTFB or load duration, test whether your HTML and hero images are actually served from cache, using the cache status header on repeat requests from two regions.

If delivery time is the subpart you need to cut, the BlazingCDN [**performance metrics page with its public test file**](https://blazingcdn.com/performance-metrics/) lets you measure latency and throughput from your own users' networks before changing anything.

Share: [f](https://www.facebook.com/sharer/sharer.php?u=https://blog.blazingcdn.com/en-us/core-web-vitals-explained-lcp-inp-and-cls-in-2026) [in](https://www.linkedin.com/sharing/share-offsite/?url=https://blog.blazingcdn.com/en-us/core-web-vitals-explained-lcp-inp-and-cls-in-2026) [𝕏](https://twitter.com/intent/tweet?url=https://blog.blazingcdn.com/en-us/core-web-vitals-explained-lcp-inp-and-cls-in-2026&text=) [✉](mailto:?subject=%3Cspan%20id="hs_cos_wrapper_name"%20class="hs_cos_wrapper%20hs_cos_wrapper_meta_field%20hs_cos_wrapper_type_text"%20style=""%20data-hs-cos-general-type="meta_field"%20data-hs-cos-type="text"%20%3ECore%20Web%20Vitals%20Explained:%20LCP,%20INP%20and%20CLS%20in%202026%3C/span%3E&body=https://blog.blazingcdn.com/en-us/core-web-vitals-explained-lcp-inp-and-cls-in-2026)

![BlazingCDN](https://blog.blazingcdn.com/hs-fs/hubfs/Logo/blog-logo-w.png?height=24&name=blog-logo-w.png)

*Heavy traffic.*  
Light bill.

The CDN for video and large traffic

100 TB a month at list price

- BlazingCDN**$415**
- [bunny.net](https://bunny.net/pricing/) Volume**$500**
- [CDN77](https://www.cdn77.com/pricing), plan to 250 TB**$990**
- [KeyCDN](https://www.keycdn.com/pricing), NA and Europe**$2,600**
- [CloudFront](https://aws.amazon.com/cloudfront/pricing/pay-as-you-go/) pay as you go**$6,965**

Each provider's published list price for transfer, lowest first, checked November 2026. BlazingCDN publishes this blog. Up to 50 TB a month a flat plan such as CloudFront Pro ($15) can cost less.

[Calculate your cost](https://blazingcdn.com/cdn-cost-calculator/?utm_source=blog&utm_medium=sidebar&utm_campaign=blog_sidebar&utm_content=compare_calc)

## Related posts

[![What Is INP? Interaction to Next Paint Explained](https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Nov-14-2026-03-08-20-3494-PM.jpeg)](https://blog.blazingcdn.com/en-us/what-is-inp-interaction-to-next-paint-explained?hsLang=en-us)

Web Performance

### [What Is INP? Interaction to Next Paint Explained](https://blog.blazingcdn.com/en-us/what-is-inp-interaction-to-next-paint-explained?hsLang=en-us)

Interaction to Next Paint (INP) is a Core Web Vitals metric that measures how quickly a page visually responds to user ...

Nov 14, 2026, 4:10:08 PM [Read more](https://blog.blazingcdn.com/en-us/what-is-inp-interaction-to-next-paint-explained?hsLang=en-us)

[![What Is CLS? Cumulative Layout Shift Explained](https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Nov-13-2026-03-08-19-9785-PM.jpeg)](https://blog.blazingcdn.com/en-us/what-is-cls-cumulative-layout-shift-explained?hsLang=en-us)

Web Performance

### [What Is CLS? Cumulative Layout Shift Explained](https://blog.blazingcdn.com/en-us/what-is-cls-cumulative-layout-shift-explained?hsLang=en-us)

Cumulative Layout Shift (CLS) is the Core Web Vitals metric for visual stability: it scores how far visible content ...

Nov 13, 2026, 4:10:03 PM [Read more](https://blog.blazingcdn.com/en-us/what-is-cls-cumulative-layout-shift-explained?hsLang=en-us)

[![What Is LCP? Largest Contentful Paint Explained](https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Nov-12-2026-03-08-23-7830-PM.jpeg)](https://blog.blazingcdn.com/en-us/what-is-lcp-largest-contentful-paint-explained?hsLang=en-us)

Web Performance

### [What Is LCP? Largest Contentful Paint Explained](https://blog.blazingcdn.com/en-us/what-is-lcp-largest-contentful-paint-explained?hsLang=en-us)

Largest Contentful Paint (LCP) is a Core Web Vitals metric. It reports the time, measured from the start of navigation, ...

Nov 12, 2026, 4:10:36 PM [Read more](https://blog.blazingcdn.com/en-us/what-is-lcp-largest-contentful-paint-explained?hsLang=en-us)

[![Responsive Images in HTML: srcset, sizes and Image Size](https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Nov-10-2026-03-22-17-0551-PM.jpeg)](https://blog.blazingcdn.com/en-us/responsive-images-in-html-srcset-sizes-and-image-size?hsLang=en-us)

Web Performance

### [Responsive Images in HTML: srcset, sizes and Image Size](https://blog.blazingcdn.com/en-us/responsive-images-in-html-srcset-sizes-and-image-size?hsLang=en-us)

Getting html image size right takes three attributes on one img element: srcset with width descriptors, sizes that ...

Nov 10, 2026, 4:25:14 PM [Read more](https://blog.blazingcdn.com/en-us/responsive-images-in-html-srcset-sizes-and-image-size?hsLang=en-us)

[![BlazingCDN](https://blog.blazingcdn.com/hubfs/Logo/blog-logo-w.png)](https://blog.blazingcdn.com?hsLang=en-us)

[📘 Learn](https://blog.blazingcdn.com/cdn-learn?hsLang=en-us) [📊 Benchmarks](https://blog.blazingcdn.com/cdn-ratings-and-benchmarks?hsLang=en-us) [🎬 Video & Streaming](https://blog.blazingcdn.com/video-streaming-cdn?hsLang=en-us) [🏭 Industries](https://blog.blazingcdn.com/cdn-industry-insights?hsLang=en-us) [💰 Pricing & Costs](https://blog.blazingcdn.com/cdn-pricing-and-cdn-costs?hsLang=en-us) [⚡ Compare](https://blog.blazingcdn.com/cdn-comparison?hsLang=en-us) [🔒 Security](https://blog.blazingcdn.com/cdn-security?hsLang=en-us) [🛠️ Tools](https://blog.blazingcdn.com/cdn-tools?hsLang=en-us) [✍️ Publish with us](https://blog.blazingcdn.com/publish-with-us?hsLang=en-us)

in f 𝕏 ✉

 Copyright © BlazingCDN |. All rights reserved.

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://blazingcdn.com/#organization",
  "@type" : "Organization",
  "description" : "High-volume CDN for video, live streaming, OTT/IPTV, software, games, SaaS and large-file delivery.",
  "logo" : {
    "@id" : "https://blazingcdn.com/#logo",
    "@type" : "ImageObject",
    "height" : 560,
    "url" : "https://blazingcdn.com/wp-content/uploads/2024/08/logo-560-560.png",
    "width" : 560
  },
  "name" : "BlazingCDN",
  "sameAs" : [ "https://www.linkedin.com/company/blazingcdn", "https://x.com/BlazingCdn", "https://www.reddit.com/r/BlazingCDN/", "https://www.wikidata.org/wiki/Q141711074" ],
  "url" : "https://blazingcdn.com/"
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://blog.blazingcdn.com/#website",
  "@type" : "WebSite",
  "inLanguage" : "en-US",
  "name" : "BlazingCDN Blog",
  "publisher" : {
    "@id" : "https://blazingcdn.com/#organization"
  },
  "url" : "https://blog.blazingcdn.com/"
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://blog.blazingcdn.com/en-us/core-web-vitals-explained-lcp-inp-and-cls-in-2026#article",
  "@type" : "BlogPosting",
  "author" : {
    "@id" : "https://blog.blazingcdn.com/en-us/author/blazingcdn#person",
    "@type" : "Person",
    "description" : "Vadym Borovskyi is Chief Product and Marketing Officer at BlazingCDN, where he has led product strategy and growth since 2021. He has more than 11 years of experience in IT product management and B2B marketing. On this blog he writes about CDN pricing and egress costs, video and software delivery, cache configuration, and how teams evaluate and switch CDN providers. He is based in Warsaw, Poland.",
    "image" : "https://143144902.fs1.hubspotusercontent-eu1.net/hubfs/143144902/vadym-borovskyi.jpg",
    "jobTitle" : "Chief Product and Marketing Officer",
    "knowsAbout" : [ "Content Delivery Networks (CDN)", "CDN pricing", "Video streaming delivery", "Software and game distribution", "Cache optimization", "Product Management", "B2B Marketing", "Digital Marketing", "Pay Per Click Marketing (PPC)", "Google Ads", "Search Engine Marketing (SEM)", "Marketing Strategy", "Artificial Intelligence (AI)", "Cloud Management", "SaaS Development", "IT Consulting", "Computer Networking", "Project Management", "Startups" ],
    "name" : "Vadym Borovskyi",
    "sameAs" : [ "https://www.linkedin.com/in/axelt/" ],
    "url" : "https://blog.blazingcdn.com/en-us/author/blazingcdn",
    "worksFor" : {
      "@id" : "https://blazingcdn.com/#organization"
    }
  },
  "dateModified" : "2026-11-15T15:10:28Z",
  "datePublished" : "2026-11-15T15:10:27Z",
  "description" : "Core Web Vitals explained for 2026: learn how LCP, INP and CLS shape page experience and improve website performance.",
  "headline" : "Core Web Vitals Explained: LCP, INP and CLS in 2026",
  "image" : "https://143144902.fs1.hubspotusercontent-eu1.net/hubfs/143144902/Gemini-Blog/image-Nov-15-2026-03-08-20-3607-PM.jpeg",
  "inLanguage" : "en-us",
  "isPartOf" : {
    "@id" : "https://blog.blazingcdn.com/#website"
  },
  "mainEntityOfPage" : {
    "@id" : "https://blog.blazingcdn.com/en-us/core-web-vitals-explained-lcp-inp-and-cls-in-2026",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@id" : "https://blazingcdn.com/#organization"
  },
  "wordCount" : 2386
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://blog.blazingcdn.com/en-us/core-web-vitals-explained-lcp-inp-and-cls-in-2026#breadcrumb",
  "@type" : "BreadcrumbList",
  "itemListElement" : [ {
    "@type" : "ListItem",
    "item" : "https://blog.blazingcdn.com/en-us",
    "name" : "Blog",
    "position" : 1
  }, {
    "@type" : "ListItem",
    "item" : "https://blog.blazingcdn.com/en-us/core-web-vitals-explained-lcp-inp-and-cls-in-2026",
    "name" : "Core Web Vitals Explained: LCP, INP and CLS in 2026",
    "position" : 2
  } ]
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://blog.blazingcdn.com/en-us/core-web-vitals-explained-lcp-inp-and-cls-in-2026#faq",
  "@type" : "FAQPage",
  "mainEntity" : [ {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Yes, Core Web Vitals remain part of the page experience signals Google uses in ranking. Google describes them as one factor among many, and relevance of the content still outweighs them. In practice, passing helps most when competing pages are otherwise similar, while poor scores mainly cost conversions and engagement from slower, less stable pages."
    },
    "name" : "Are Core Web Vitals a Google ranking factor in 2026?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "A good INP score is 200 milliseconds or less at the 75th percentile of page loads, and anything above 500 milliseconds is poor. INP reports a near-worst interaction from each visit, so a single heavy menu or filter handler can fail the page even when most clicks respond quickly. Debug it with field attribution, not lab tests."
    },
    "name" : "What is a good INP score for Core Web Vitals?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Lighthouse runs one synthetic load on a fixed throttled profile, while Core Web Vitals field data aggregates 28 days of real Chrome visits at the 75th percentile. Real users bring different devices, networks, cache states and geographies. Use Lighthouse to reproduce and debug a problem, and use CrUX or your own real-user monitoring to judge it."
    },
    "name" : "Why does Lighthouse show a different LCP than Core Web Vitals field data?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Core Web Vitals fixes take up to 28 days to show fully, because CrUX field data is a rolling 28-day window. Improvements appear gradually as older page loads age out. Search Console also groups similar URLs, so a fix applied to one template may take time to move a group's status. Real-user monitoring shows the trend within days."
    },
    "name" : "How long does it take for Core Web Vitals fixes to show in Search Console?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "A CDN mainly improves LCP, by lowering TTFB and resource load duration through edge caching, compression and nearby delivery. It does little for INP, which depends on main-thread JavaScript work, and nothing for CLS, which depends on layout. The biggest CDN gain usually comes from caching anonymous HTML, not only static assets."
    },
    "name" : "Does a CDN improve Core Web Vitals scores?"
  } ]
}
```