B2B buyers research quietly and judge quickly. A slow, janky site erodes trust before a sales conversation begins. Core Web Vitals give you a shared, user‑centred way to measure and improve that experience, without chasing a vanity score.

The thresholds (at the 75th percentile)

  • LCP (Largest Contentful Paint): ≤ 2.5 s
  • INP (Interaction to Next Paint): ≤ 200 ms
  • CLS (Cumulative Layout Shift): ≤ 0.1

Why this matters for B2B

For B2B, the win isn’t e‑commerce conversion rate, it’s credibility and lead quality. A fast, stable site signals competence (especially if you sell technology), keeps researchers engaged across multiple pages, and improves the experience for the mobile and lower‑bandwidth visitors that desktop‑centric teams often forget. Performance is also one of many factors search engines consider for ranking, though it’s not a silver bullet.

The three metrics, in plain language

Largest Contentful Paint (LCP)

How long until the largest visible element (often a hero image or headline) renders. Slow LCP usually comes from slow server responses, render‑blocking resources, or large unoptimised images.

Interaction to Next Paint (INP)

How responsive the page feels across all interactions. High INP usually means too much JavaScript blocking the main thread. INP replaced First Input Delay as a Core Web Vital in 2024.

Cumulative Layout Shift (CLS)

How much the layout jumps as the page loads. Common causes: images without dimensions, injected banners, and late‑loading fonts or ads.

Lab data vs field data: don’t confuse them

Tools like Lighthouse give lab data: a single simulated run, useful for debugging. Core Web Vitals are officially assessed on field data, real users over time (for example, via the Chrome User Experience Report). A great Lighthouse score does not guarantee good field performance, so be honest about which you’re reporting.

A realistic improvement plan

  1. Measure first. Look at field data for your top landing pages, then use Lighthouse to find causes.
  2. Fix LCP: optimise and correctly size the hero image, prioritise it (don’t lazy‑load it), reduce render‑blocking CSS/JS, and improve server response time.
  3. Fix CLS: set width and height (or aspect‑ratio) on images and embeds, reserve space for dynamic content, and use font-display to avoid layout jumps.
  4. Fix INP: ship less JavaScript, break up long tasks, defer non‑critical scripts, and avoid heavy third‑party tags.
  5. Protect it: add a performance budget so regressions are caught before launch.

Our take: most B2B sites get the biggest win from three things: a properly optimised LCP image, fewer third‑party scripts, and reserving space to kill layout shift. You rarely need a full rebuild.

Sources

  1. Google web.dev, “Core Web Vitals.” web.dev/articles/vitals
  2. Google web.dev, “Interaction to Next Paint (INP).” web.dev/articles/inp
  3. Google web.dev, “Optimize LCP / CLS.” web.dev/articles/optimize-lcp
  4. Chrome UX Report (field data). developer.chrome.com/docs/crux

Editorial note. Written by the Qaisi team and reviewed by our engineering practice for technical accuracy. Thresholds reflect Google’s published guidance at the time of writing. A named reviewer will be shown here once our editorial policy is published.

Share: LinkedIn X / Twitter Email

Want a faster, more credible site?

We build performance in from the start and can tune an existing site against Core Web Vitals.

Explore web development