What Core Web Vitals are
Core Web Vitals are Google's three metrics for real-world 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 least 75% of real visits meet the "good" threshold for all three.
| Metric | Measures | Good | Poor |
|---|---|---|---|
| LCP — Largest Contentful Paint | When the main content appears | ≤ 2.5 s | > 4.0 s |
| INP — Interaction to Next Paint | How fast the page responds to input | ≤ 200 ms | > 500 ms |
| CLS — Cumulative Layout Shift | How much the layout jumps | ≤ 0.1 | > 0.25 |
INP replaced First Input Delay (FID) as a Core Web Vital on 12 March 2024. INP is stricter: it looks at the latency of interactions across the whole visit, not just the first one.
Why B2B websites should care
It is tempting to treat speed as an e-commerce problem. B2B buyers don't check out in a cart, so a few hundred milliseconds can't matter — or so the argument goes. The research says otherwise.
+8.4%
increase in retail conversions from a 0.1-second improvement in mobile site speed; travel conversions rose 10.1%.
The same study found lead-generation sites also benefited from faster pages, with more visitors moving deeper into the funnel. A B2B buyer comparing three suppliers on a phone between site visits behaves much like any other mobile user: if the page drags, they open the next tab.
Page experience is also a ranking consideration in Google Search. It will not outrank relevance, but between two equally useful pages, the faster and more stable one has the edge.
Fixing LCP: make the main content arrive first
On corporate sites, the LCP element is almost always the hero — a full-width photo, a background video, or a large headline. The usual culprits are oversized images, render-blocking CSS and JavaScript, and slow server response.
- Serve hero images in AVIF or WebP at the size actually displayed, with responsive srcset.
- Never lazy-load the LCP image; give it fetchpriority="high" instead.
- Replace autoplay hero videos with a poster image, or load the video after first paint.
- Use static generation or edge caching so time to first byte stays low.
- Preload the one or two font files used above the fold.
<!-- LCP hero: eager, prioritized, right-sized -->
<img src="/hero-1600.avif"
srcset="/hero-800.avif 800w, /hero-1600.avif 1600w"
sizes="100vw" width="1600" height="900"
fetchpriority="high" alt="Offshore platform at dawn">Fixing INP: keep the main thread free
INP suffers when JavaScript blocks the browser from responding to a tap or click. On B2B sites the biggest offenders are rarely your own code; they are tag managers, chat widgets, heatmap tools, and marketing pixels that pile up over years.

- 1.Audit every third-party script and remove the ones nobody uses.
- 2.Load chat and analytics tools after user interaction or idle time.
- 3.Break long tasks into smaller chunks and avoid heavy work in click handlers.
- 4.Prefer CSS for animations and avoid scroll-jacking libraries.
- 5.Ship less JavaScript — static HTML with small islands of interactivity beats a full client-side app for most marketing pages.
“Every script on a corporate site was added for a good reason. Few were ever removed for a better one.”
Fixing CLS: stop the page from jumping
Layout shift makes a site feel unfinished. It happens when content appears without reserved space — images without dimensions, late cookie banners, web fonts swapping in, or embeds that resize after load.
- Set width and height (or aspect-ratio) on every image, video, and iframe.
- Reserve space for banners and announcement bars, or overlay them instead of pushing content.
- Use font-display: optional or matched fallback metrics to limit font-swap shifts.
- Never insert content above existing content unless the user asked for it.
Measure, fix, and keep it fixed
| Tool | Data type | Use it for |
|---|---|---|
| PageSpeed Insights | Field + lab | Quick pass/fail per URL |
| Search Console — Core Web Vitals report | Field | Site-wide groups of failing URLs |
| Chrome DevTools Performance panel | Lab | Finding long tasks and LCP bottlenecks |
| web-vitals JavaScript library | Field (your own) | Sending real-user metrics to analytics |
Performance regresses quietly. A new campaign pixel, a heavier hero, a fresh plugin — each feels harmless. Put a performance budget into your release process and recheck field data monthly. When we rebuild sites at Finetune, we treat Core Web Vitals as acceptance criteria, not as a post-launch optimization.
Frequently asked questions
- What are the Core Web Vitals thresholds?
- A page has good Core Web Vitals when Largest Contentful Paint is 2.5 seconds or less, Interaction to Next Paint is 200 milliseconds or less, and Cumulative Layout Shift is 0.1 or less, measured at the 75th percentile of real page visits.
- What replaced First Input Delay?
- Interaction to Next Paint (INP) replaced First Input Delay as a Core Web Vital on 12 March 2024. INP measures the responsiveness of all interactions during a visit rather than only the delay before the first one.
- Do Core Web Vitals affect Google rankings?
- Core Web Vitals are part of the page experience signals Google Search uses. Relevance and content quality matter more, but when pages are otherwise similar, better page experience can help. Faster pages also convert better regardless of ranking.
- What usually slows down B2B websites?
- The most common causes are oversized hero images or autoplay videos, too many third-party scripts such as tag managers and chat widgets, render-blocking fonts and CSS, and heavy client-side JavaScript frameworks used for mostly static marketing pages.





