Skip to main content

Core Web Vitals

Search Console says your pages need improvement. Now what?

We translate Core Web Vitals reports into specific fixes for loading, responsiveness and layout stability, working from real-user data so improvements show up where Google measures them.

LCP in good rangeFaster pages

Business impact

What Core Web Vitals tell you about your visitors

Core Web Vitals measure three things visitors notice: how quickly the main content appears, how quickly the page reacts to a tap, and whether things jump around while loading.

Frustration you cannot see in analytics

A button that does nothing for half a second or a layout shift that causes a mis-tap rarely shows up in reports, but it erodes trust and completion rates.

Part of Google's page experience signals

Core Web Vitals contribute to how Google evaluates page experience. Passing them will not guarantee rankings, but failing them is a weakness competitors may not have.

Mobile is where most sites fail

Mid-range phones on mobile networks expose problems that a fast office desktop hides. Field data reflects those real devices.

Common issues

Problems we regularly solve

Slow Largest Contentful Paint (LCP)

Hero images that are lazy-loaded, discovered late, served too large or delayed by slow server response push LCP beyond the 2.5 second threshold.

Poor Interaction to Next Paint (INP)

Long JavaScript tasks from page builders, sliders, consent managers and tag managers block the main thread, so taps and clicks feel sluggish.

Cumulative Layout Shift (CLS)

Images and embeds without dimensions, late-loading web fonts, cookie banners and injected promotional bars push content down as the page loads.

Lab and field data disagree

Lighthouse shows green while Search Console reports failures, because lab tests use a single simulated device and cannot measure real interactions.

Whole URL groups failing together

Search Console groups similar URLs, so one problematic template, such as product or category pages, can flag thousands of URLs at once.

Fixes that never seem to register

Field data is a rolling 28-day window, so improvements appear gradually and teams often abandon work before the data catches up.

What's covered

What's included in Core Web Vitals optimisation

Google's "good" thresholds are assessed at the 75th percentile of page loads: LCP at or below 2.5 seconds, INP at or below 200 milliseconds and CLS at or below 0.1. Our work targets each metric directly.

Field data analysis

Review of the Core Web Vitals report in Search Console and CrUX data through PageSpeed Insights to identify which templates and devices are failing.

LCP improvements

Preloading or prioritising the LCP image, serving it in WebP or AVIF at the right size, removing lazy loading above the fold and reducing server response time.

INP improvements

Breaking up long tasks, deferring or removing non-essential scripts, reducing DOM size and auditing third-party tags that run on interaction.

CLS improvements

Setting width and height on media, reserving space for ads and embeds, adjusting font loading and fixing banners that insert above existing content.

Real-user measurement

Optional collection of Core Web Vitals from your own visitors using the web-vitals library, so you see results by page without waiting on CrUX.

Validation in Search Console

Starting validation once fixes are live and tracking the affected URL groups until they move into the good range.

Maintenance activities

What we do, and how often

Exact frequencies depend on your plan and platform. This is a typical schedule.

On onboarding

  • Export and review of Search Console Core Web Vitals issues
  • Mapping failing URL groups to site templates
  • Lab profiling of representative pages in Chrome DevTools

On demand

  • Template-level fixes for LCP, INP and CLS
  • Third-party script audit with recommendations to keep, defer or remove
  • Search Console validation requests after release

Monthly

  • Field data trend review per template
  • Check for regressions after plugin, theme or app updates
  • Core Web Vitals status in the monthly report

Our methodology

How we work

  1. 1

    Read the field data first

    We start from CrUX and Search Console to see what real visitors experience, then decide which metric and template to tackle first.

  2. 2

    Reproduce in the lab

    Using throttled mobile profiles and performance traces, we reproduce the problem and identify the specific element, script or resource responsible.

  3. 3

    Fix at template level

    Changes are made in the theme, templates or configuration so they apply to every page of that type, then tested on staging.

  4. 4

    Release and validate

    After release we confirm the lab improvement and start Search Console validation for the affected issue groups.

  5. 5

    Watch the 28-day window

    We track field data over the following weeks and report when the 75th percentile moves into the good range, or what is still holding it back.

Business benefits

What you gain

Work focused on what Google measures

By prioritising field data, effort goes into the metrics and pages that appear in your Search Console reports.

Template-level fixes

Fixing the template rather than individual pages means improvements apply across whole sections of the site.

Better everyday usability

Stable layouts and responsive interactions make the site easier to use, whether or not a visitor arrived from search.

Clear progress reporting

You see which URL groups have passed, which are improving and what remains, rather than a single fluctuating score.

Technologies supported

  • Google Search Console
  • PageSpeed Insights
  • Chrome UX Report (CrUX)
  • Lighthouse
  • Chrome DevTools Performance panel
  • web-vitals JavaScript library
  • WebPageTest
  • Google Tag Manager
  • WebP and AVIF
  • Resource hints (preload, preconnect)

Running something not listed? Ask us – we'll tell you honestly if it's a fit.

Who it's for

Who needs Core Web Vitals optimisation?

Marketing teams

Teams that have seen Core Web Vitals warnings in Search Console and need someone to turn them into fixes.

E-commerce managers

Stores where product and category templates fail on mobile because of image galleries, reviews and app scripts.

Publishers and content sites

Sites with ads, embeds and long-form pages where layout shift and responsiveness are common problems.

Industry guidance: E-commerce · Education · Professional Services

FAQs

Core Web Vitals Optimisation: common questions

What are the Core Web Vitals thresholds?
Google classes a page as good when, at the 75th percentile of visits, 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. Our Core Web Vitals guide explains each one.
Why does PageSpeed Insights show good lab results but failing field data?
Lab tests simulate one device on one connection and cannot measure real interactions, so INP in particular often only shows up in field data. We use lab tools to diagnose but judge success on field data.
How long before Search Console shows the improvement?
Field data is based on a rolling 28-day window of real visits, so improvements usually appear gradually over several weeks after release. Low-traffic pages may not have enough data to report at all.
Our site does not have enough traffic for CrUX data. Can you still help?
Yes. We can rely on lab testing and, if useful, add lightweight real-user measurement with the web-vitals library so you collect your own field data.
Do we have to remove our marketing tags to pass INP?
Not necessarily. We audit each tag, measure its cost and recommend options such as delaying it until after interaction, loading it on fewer pages or replacing it. Decisions about removing tools remain yours.

Turn Core Web Vitals warnings into a fix list

Request a technical audit and we will map your failing URL groups to the templates and scripts responsible.