Core Web Vitals: What Every Agency Needs to Know in 2026 Complete Agency Guide

Core Web Vitals have transformed how agencies must approach website delivery. Since their integration into the Google algorithm in 2021 and the major 2024 update, these three performance metrics are no longer a technical footnote: they directly condition the organic search rankings of every page you deliver to clients.

In 2026, according to Chrome User Experience Report (CrUX) data, around 45% of sites in European Google SERPs pass the "Good" thresholds across all three metrics. For a digital agency, this is both a constraint and an opportunity: well-optimised sites have a measurable competitive advantage.

This guide explains what Core Web Vitals are, why they concretely matter for your clients' rankings, and how to optimise them effectively on every project.

What are Core Web Vitals?

Core Web Vitals are three metrics defined by Google to measure the real user experience of a web page. They form part of a broader set called "Page Experience", which also includes HTTPS security, the absence of intrusive interstitials and mobile optimisation.

What distinguishes Core Web Vitals from classic performance metrics is their origin: these are field data metrics, collected from millions of real Chrome users. They are not lab simulations. Google knows exactly how fast your site loads for your visitors, on their real devices and real connections.

The most significant update came in March 2024: INP (Interaction to Next Paint) replaced FID (First Input Delay) as the official responsiveness metric. This transition matters for agencies: INP measures all interactions throughout a session, not just the first one, which tightens requirements on JavaScript-heavy pages.

The three metrics explained

LCP: Largest Contentful Paint

LCP measures the time needed to display the largest element visible on screen. In practice, that is the hero image, main text block or banner video.

The LCP element is often an unoptimised hero image, a web font that blocks rendering, or a slow-responding server. On the vast majority of sites, LCP is the first problem to surface.

INP: Interaction to Next Paint

INP (which replaced FID in March 2024) measures the latency of all user interactions with the page: clicks, keyboard presses, mobile taps. It retains the 75th percentile value of session interactions.

INP is particularly critical on sites with heavy JavaScript: complex frameworks, WordPress plugins that add event listeners, third-party chat or tracking scripts. A page that "loads fast" but responds slowly to clicks will get a poor INP score.

CLS: Cumulative Layout Shift

CLS measures the visual stability of a page: does content jump visually during or after loading? A high CLS means elements move unexpectedly, shifting text the user was reading or moving a button just as they were about to click it.

The most frequent causes: images without defined dimensions, web fonts that replace displayed text (FOUT/FOIT), or advertisements and embeds that load dynamically and push content down.

Core Web Vitals and SEO: what the data says

The integration of CWV into the Google algorithm is not incidental. Several studies published between 2024 and 2026 document the correlation between CWV scores and SERP positioning.

It is important to add nuance: Core Web Vitals are not the only ranking factor, far from it. Content relevance, backlinks and domain authority remain dominant. But with equivalent content and authority, a site that passes CWV thresholds gains an advantage over one that fails them. And in competitive markets like digital in French-speaking Belgium, that advantage can make the difference.

The ground-level reality is more nuanced still: Google can rank excellent content even if the site fails CWV. What it will not do is give you the benefit of the doubt between two pages of comparable value. Performance becomes a tiebreaker.

Typical problems on agency-built sites

After analysing dozens of sites delivered by agencies of all sizes, certain problems recur systematically.

Uncompressed hero images without modern formats

Loading dozens of WordPress plugins

Web fonts without a fallback strategy

Third-party scripts loaded synchronously

Missing dimensions on images

These problems are particularly common on projects delivered quickly, without a formalised performance checklist. The article on technical SEO foundations you are neglecting covers other common blind spots.

How to measure your Core Web Vitals

Measuring CWV correctly means distinguishing two types of data, which are complementary but different in their use.

A practical point often overlooked: field data is only available if the URL has enough traffic. For a low-traffic site, Search Console will show 'no data'. In that case, lab scores (Lighthouse) remain the only available reference point, and you work from there.

Segmenting mobile and desktop

CWV scores often differ significantly between mobile and desktop. Google uses both, but mobile tends to be more penalised because 4G connections in Belgium and French-speaking Switzerland remain variable by zone, and low-end devices are more widespread than agencies often assume among B2C target audiences.

When auditing a site, always check both segments. A site that passes on desktop but fails on mobile has a real SEO problem, even if the desktop experience seems acceptable.

Concrete optimisations per metric

Optimising LCP

LCP depends primarily on four factors: server speed, resource blocking time, LCP image size and format, and loading priority.

High-impact immediate actions:

• Convert hero images to WebP or AVIF (30 to 70% weight reduction)
• Add fetchpriority="high" and loading="eager" on the identified LCP image
• Use <link rel="preload"> in the <head> to preload the hero image
• Optimise TTFB (Time to First Byte): quality hosting with low latency, CDN, server cache

On Next.js or static sites, LCP is easier to control because the server responds near-instantly and images can be served from a CDN from generation. On WordPress, TTFB optimisation requires quality hosting (no low-end shared hosting) and a robust cache plugin like WP Rocket or Perfmatters.

Optimising INP

INP is the hardest metric to optimise on sites with heavy JavaScript. It measures the browser's ability to process an interaction without blocking the main thread.

Priority actions:

• Defer or delay non-critical third-party scripts (analytics, chat, pixels) with defer or async
• Reduce JavaScript bundle sizes (tree shaking, route-based code splitting)
• Avoid heavy event handlers on frequently clicked elements
• On React/Next.js: avoid unnecessary re-renders, use useMemo and useCallback judiciously

A high INP is often caused by third-party scripts loaded synchronously. A simple audit: open Chrome DevTools, enable "Block third-party scripts" in the Network panel and measure INP. If the score improves dramatically, you have found the cause.

Optimising CLS

CLS is often the simplest metric to fix once the causes are identified.

Solutions by cause type:

• Images without dimensions: always specify width and height in HTML, or use CSS aspect-ratio
• Web fonts: use font-display: swap and preload critical fonts with <link rel="preload">
• Iframes and embeds: wrap in a container with aspect-ratio or calculated padding-bottom
• Cookie banners and pop-ins: use position: fixed to prevent them from shifting content

Guaranteeing scores for your clients

The real added value of an agency or development partner is not measured only at initial delivery. It is also measured by how long performance holds over time.

If you work with a white-label development partner, performance must be built into the service contract, not added as an option. A serious partner maintains LCP, INP and CLS scores within "Good" thresholds from initial delivery and can document their results. Our article on before/after Lighthouse scores for rebuilt agency sites gives concrete examples of what this looks like in practice.

For SEO agencies in particular, guaranteeing technical performance is inseparable from client results. Proposing a technical rebuild to a client stagnating despite good content is often the most profitable conversation of the year. We have detailed how SEO agencies use web development outsourcing to offer this type of service without in-house technical skills.

A word on contractual guarantees

Some agencies are beginning to include performance commitments in their client contracts: "Lighthouse score > 90" or "LCP < 2.5 seconds measured at launch". This is an excellent differentiating practice, but it assumes your delivery process is genuinely calibrated to achieve it. If you outsource development, make sure your white-label partner can guarantee these thresholds and provide proof at delivery.

Frequently asked questions

Are Core Web Vitals really a Google ranking factor?

What is the difference between field data and lab data?

My site scores 90+ on Lighthouse but fails Core Web Vitals in Search Console. Why?

How long does it take to see the ranking impact of a CWV optimisation?

Do Core Web Vitals apply to all pages or only the homepage?

Is WordPress harder to optimise for Core Web Vitals than a static site?

Conclusion

Core Web Vitals are not a passing trend. In 2026, they are an integral part of the technical baseline for any professional website. For agencies, understanding these metrics is no longer optional: it is a fundamental skill that distinguishes quality deliveries from sites that stagnate in the SERPs.

The good news is that the bulk of optimisations are systematisable. With a rigorous delivery checklist and the right technical stack, it is possible to guarantee "Good" scores across all three metrics for the vast majority of projects. If you want to know how to structure this process without in-house technical skills, see our checklist of criteria for choosing a development partner or discover our white-label approach.