Core Web Vitals: A Complete Guide to Website Performance

Core web vitals are three metrics Google uses to score how fast, responsive, and stable a page feels to a real visitor: Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift. Pass all three, and you clear Google’s page experience bar. Fail one, and you risk losing positions to a faster competitor.

This guide covers what each metric measures, how to test core web vitals with lab and field data, and a step-by-step plan to fix the common problems on UK and Irish business sites. It also looks at one factor most guides skip: how server location affects load times for visitors in Britain and Ireland.

What Are Core Web Vitals?

Core web vitals are a subset of Google’s page experience signals, focused on loading speed, interactivity, and visual stability. Google built them into its ranking systems in 2021 and has kept them as a measurable input ever since. The metrics use real-world data from the Chrome User Experience Report, so they reflect what your actual visitors experience on their own devices and connections, not a score from a single test run.

They sit alongside Google’s helpful content system rather than replacing it. A fast page with thin content will not rank, and strong content on a slow page will struggle against a faster rival. For most SME sites we audit through our search engine optimisation services, Core Web Vitals act as a tie-breaker: the deciding factor when two pages are otherwise close.

Why Google Measures Loading, Interactivity, and Stability

Each metric maps to a moment of frustration. Loading covers the wait before the main content appears. Interactivity covers the lag after you tap or click. Stability covers content jumping around as the page settles. Google picked these three because they predict whether someone stays or bounces.

The Shift From FID to INP

Until March 2024, the interactivity metric was First Input Delay (FID), which only measured the delay on a visitor’s first interaction. Google retired FID and replaced it with Interaction to Next Paint (INP), which measures responsiveness across the whole visit. Any guide still listing FID as a current metric is out of date, and so is any audit built around it.

The Three Metrics Explained

The table below gives the thresholds Google uses. Anything in the “good” column passes; “poor” puts the page at risk.

Largest Contentful Paint: Solving the Hero Image Problem

LCP measures how long the largest visible element takes to render, usually a hero image, video, or large text block. The target is 2.5 seconds or faster. The most common culprit on business sites is an uncompressed hero image loaded at full resolution. Serve images in WebP or AVIF, set explicit dimensions, and preload the hero asset so the browser fetches it early. Slow server response time, covered further down, is the other frequent cause.

Interaction to Next Paint: The Responsiveness Test

INP measures how quickly the page responds when someone clicks, taps, or presses a key across the entire visit. The target is 200 milliseconds or less. Heavy JavaScript is the usual cause of a poor score because long tasks block the main thread and delay the browser’s response. Splitting code into smaller chunks and deferring non-essential scripts both help. For sites that lean on plugins, our WordPress theme guidance explains how theme bloat quietly inflates this metric.

Cumulative Layout Shift: Stopping The Jump

CLS measures how much the layout moves unexpectedly as the page loads. The target is 0.1 or lower. UK retailers see this most with cookie banners and Buy Now Pay Later widgets that load late and push content down. Reserve space for any element that loads after the initial render: set width and height on images, give ad slots a fixed container, and use font-display: swap So the text does not reflow when a custom font arrives.

The UK infrastructure factor: hosting, latency, and TTFB

Time to First Byte (TTFB) is the wait before your server sends the first byte of the page, and it feeds directly into LCP. US-centric guides rarely mention it, but for a Belfast or Dublin business, it can be the difference between passing and failing. A site hosted on a US server adds physical distance, and every added millisecond of latency degrades the loading score for local visitors.

The fix is to host close to your audience or to put a content delivery network in front of the site, with edge nodes in London or Dublin caching content nearer the user. We cover the trade-offs in detail in our managed hosting breakdown and our website performance analysis guide.

How To Measure Core Web Vitals

You need both lab data and field data. Lab data comes from a single controlled test and is best for debugging a change before it goes live. Field data comes from real visitors via the Chrome User Experience Report and is what Google actually uses for ranking.

Google Search Console

The core web vitals report in Search Console groups your URLs into Good, Needs Improvement, and Poor using field data. It is the first place to look because it shows the metrics Google scores you on, grouped across similar pages.

PageSpeed Insights and Lighthouse

PageSpeed Insights shows lab and field data side by side and names the specific LCP element and the scripts hurting INP. Lighthouse, built into Chrome DevTools, runs the same lab audit locally so you can test fixes before deploying. Use the DevTools performance panel to find the exact long task causing an INP delay.

Real User Monitoring

Search Console field data updates on a 28-day rolling average, so it is slow to confirm a fix. Real user monitoring tools report continuously, which is useful when you have made a change and want to see the effect across different devices and locations sooner.

How To Improve Your Scores: A Remediation Plan

Aim for the green “good” zone rather than a perfect score. Chasing 100/100 burns hours for diminishing returns once you are safely in the pass range. Work through the fixes in this order.

Image and Media Optimisation

Compress every image, convert to WebP or AVIF, and set explicit width and height. Lazy-load anything below the fold so it does not compete with the hero element. This is the single highest-impact change for most sites, and it lifts LCP directly.

Critical CSS and Render-Blocking Resources

In-line the CSS needed for above-the-fold content and defer the rest. Minify CSS and JavaScript, and load non-essential scripts asynchronously so they stop blocking the first paint. This helps both LCP and INP.

Third-Party Script Management

Analytics, heatmaps, and pixel scripts are the biggest INP killers on SME sites. Audit what is loading through your tag manager, remove anything unused, and load the rest after the page is interactive. Every third-party script you add runs on the main thread your visitors are waiting on.

“Core web vitals help gauge initial performance, but deeper engagement signals reveal if visitors truly value your page. That’s the next frontier of user-focused SEO,” says Ciaran Connolly, founder of ProfileTree.

If the technical side sits beyond your team, a structured site audit will find the specific issues before you spend money guessing. You can also start with a free SEO check to see where performance is dragging your rankings.

Final word

Core web vitals reward sites that load fast, respond quickly, and stay stable while they settle. Start with your Search Console report, fix images and third-party scripts first, and check your hosting if LCP stays stubborn. Get into the green zone and hold it there, then put the effort you saved into content that keeps visitors reading.

Frequently Asked Questions

Short answers to the questions people search most often around core web vitals. Each point refers back to the relevant section above for details.