Performance10 min readPublished: 15 Mar 2025Updated: 9 Nov 2026

Core Web Vitals for WordPress: The 2026 Guide

A plain guide to Core Web Vitals for WordPress: what LCP, INP and CLS mean, the current thresholds, how to measure them, and the exact fixes for each one.

G7Cloud Engineering
Platform team
Share:
Three abstract performance gauges resting in the green, on a soft blue gradient.
  • Core Web Vitals are three scores, measured on real visitors, that Google uses in ranking: LCP, INP and CLS.
  • The targets are LCP under 2.5 seconds, INP under 200 milliseconds and CLS under 0.1.
  • INP replaced FID as the responsiveness score in March 2024, and it is stricter about slow interactions.
  • CLS measures how much the page jumps. Images without a width and height, late fonts and banners are the usual WordPress causes.
  • Google ranks you on data from real visitors, not on the lab score from a single test.

What are Core Web Vitals, and do they affect WordPress SEO?

Core Web Vitals are three scores Google uses to judge how a page feels to real visitors: LCP for loading, INP for responsiveness and CLS for visual stability. They have been a Google ranking signal since June 2021. A WordPress site that meets all three on real traffic has an edge over one that fails them.

The key words are real visitors. Google grades your site on data from actual Chrome users over the previous 28 days, not on a test you run once. So the goal is a page that stays fast and steady on cheap phones, slow networks and older browsers, not a single green score on your own laptop.

A tie-breaker, not a magic wand

Strong content still wins. Between two similar pages, the faster and more stable one gets the edge.

Speed also costs or earns money directly. Slow pages lose visitors before they read a word, especially on mobile. For the business case, read how slow websites kill conversions.

What are the Core Web Vitals thresholds?

The current thresholds are LCP under 2.5 seconds, INP under 200 milliseconds and CLS under 0.1. To pass, 75% of your real visits must hit each target. A quarter of visits can be slower and you still pass, but one score in the red fails the whole page.

MetricGoodNeeds improvementPoorUnit
LCP (loading)2.5 or less2.5 to 4.0over 4.0seconds
INP (responsiveness)200 or less200 to 500over 500milliseconds
CLS (visual stability)0.1 or less0.1 to 0.25over 0.25score (no unit)

The three Core Web Vitals and their bands, measured across 75% of real visits. Source: Google's web.dev documentation.

One red score fails the page

Google does not average the three. A page with a fast LCP and INP but a CLS of 0.3 still fails. Fix the worst score first, not the easiest.

These figures follow Google's documentation on web.dev. Google reviews them roughly once a year, so check the source before treating any number as permanent.

What is LCP and how do I fix it on WordPress?

LCP (Largest Contentful Paint) is how long the biggest visible element takes to appear: usually a hero image, a large heading or a banner. The target is 2.5 seconds or less. On WordPress it depends on three things, in order: how fast the server responds, whether the hero image is delayed, and how big it is.

Start with the server. Time to First Byte (TTFB) is the gap between the browser asking for the page and the first byte arriving. If the server takes over a second to send anything, nothing on the front end wins that back. On busy shared hosting, the same page can answer in 300 milliseconds at 6am and 2 seconds at lunchtime, and no caching plugin fixes that swing.

Once the server is quick, these are the WordPress fixes for LCP:

  1. 1Preload the hero image, so the browser fetches it early instead of finding it late in the HTML.
  2. 2Set fetchpriority="high" on the hero image, and never lazy-load it: that delays the one image you need first.
  3. 3Serve the hero as WebP or AVIF at the size it is shown, not a 4000-pixel original shrunk by the browser.
  4. 4Inline the small amount of CSS the top of the page needs, and load the rest of the CSS and JavaScript without blocking the first paint.
  5. 5Cache full pages, so most visitors get ready-made HTML and skip PHP and the database.
Pro Tip

Measure before you change anything. If TTFB alone is over a second, that is a hosting problem, not a theme problem. The curl timing variables split one request into DNS, connection, TLS and server time.

What is INP, and how is it different from FID?

INP (Interaction to Next Paint) measures how quickly the page responds when someone taps, clicks or types. The target is under 200 milliseconds. It replaced FID (First Input Delay) in March 2024 and is much stricter. FID only timed the wait before the first interaction. INP times the full response to every interaction in the visit.

FID (retired)INP (since March 2024)
What it timedThe wait before the first interaction was handledThe full time from interaction to the next frame on screen
Which interactionsOnly the firstEvery one, with the slowest counted
Good threshold100 milliseconds or less200 milliseconds or less

Why sites that passed FID can fail INP: INP watches the whole visit.

Heavy JavaScript is the usual cause of a poor INP. While a script runs a long task, the browser is busy and cannot respond to the tap the visitor just made. WordPress sites with many plugins often load large scripts that all compete for that time. The fixes:

  1. 1Cut third-party scripts. Chat widgets, heat maps, extra analytics tags and ad scripts are the most common cause. Remove what you do not need and load the rest late.
  2. 2Break up long tasks. A script that runs for more than 50 milliseconds blocks interaction, so split heavy work into smaller pieces.
  3. 3Judge plugins by what they load on the front end. One form or slider plugin can add hundreds of kilobytes of JavaScript to every page.
  4. 4Put off work that is not needed straight away until the browser is idle.

JavaScript decides your INP

The most common cause of a failing INP on WordPress is a pile of third-party tags loaded on every page. Cutting them is usually quicker and cheaper than any optimisation plugin. See why performance should not depend on plugins.

What is CLS and what causes layout shift on WordPress?

CLS (Cumulative Layout Shift) measures how much the page jumps around as it loads. The target is a score of 0.1 or less. A shift happens when content moves after the visitor can see it: you go to tap a link, an image loads above it, and the page lurches down. It is the score most often ignored on WordPress, and the easiest to break by accident.

The usual WordPress causes:

  1. 1Images without width and height attributes. The browser cannot reserve space, so text moves when the image arrives. Always set both.
  2. 2Ad and embed slots with no space reserved. A late ad, map or video pushes everything below it down. Give each slot a fixed height.
  3. 3Late web fonts. When a custom font swaps in, lines re-wrap. Preload your main fonts and choose a font-display setting that avoids a jarring swap.
  4. 4Cookie banners added above the content. Show them as an overlay, or reserve their space in advance.
Pro Tip

CLS is the cheapest score to fix, because most causes are in the page markup, not the server. Set a width and height on every image, reserve space for anything that loads late, and preload your main font.

How do I measure Core Web Vitals on my WordPress site?

Use two kinds of data. Lab data comes from a single test in controlled conditions, and is useful for finding problems. Field data is what real visitors experienced, and it is what Google ranks you on. Four tools cover both.

ToolData typeBest for
PageSpeed InsightsField and labChecking one page: real-visitor scores plus lab detail
Chrome UX Report (CrUX)FieldThe real-visitor data Google uses to grade you
Search Console Core Web Vitals reportFieldEvery URL on your site, grouped by pass or fail
Chrome DevToolsLabReproducing one slow interaction to fix it

Lab data helps you find problems; field data decides your ranking.

Start with PageSpeed Insights. Enter a URL and it shows your real 28-day scores at the top and lab detail below. If it says there is not enough real-visitor data, you only have the lab score, which is not your ranking grade. Watch Search Console's Core Web Vitals report over time: it groups pages that share a problem, so you can fix a whole template at once.

Green in the lab is not green in the field

A perfect score on your laptop and fibre connection says little about a visitor on an old phone and mobile data. Trust the field data in PageSpeed Insights and Search Console over any single lab run.

Why does hosting set the limit on your Core Web Vitals?

Every Core Web Vital starts with the server. LCP cannot beat your Time to First Byte, and no plugin wins back time the server has already spent. On shared hosting, your response time depends on what every other site on the machine is doing, so your scores wobble even when your page never changes.

On G7Cloud WordPress hosting, each site runs in its own container with its own database, so another customer's busy lunchtime does not slow your pages. The dashboard shows each site's CPU and memory use over the last 7 days, so when a score drops you can see whether the site was short of resources at the time.

If you run a shop, the same thinking applies to WooCommerce speed optimisation, where the cart and checkout cannot be cached and hit PHP and the database on every request.

Frequently asked questions

What is a good Core Web Vitals score for WordPress?

You pass when all three scores hit their targets for 75% of real visits: LCP under 2.5 seconds, INP under 200 milliseconds and CLS under 0.1. One score in the red fails the whole page, so fix the worst one first.

Did INP replace FID for WordPress sites?

Yes. INP (Interaction to Next Paint) replaced FID (First Input Delay) in March 2024. INP is stricter: it times the full response to every interaction in a visit, not only the wait before the first one, so some sites that passed FID now fail INP.

Why is my Core Web Vitals score good in PageSpeed Insights but poor in Search Console?

PageSpeed Insights often shows a lab score from a fast test machine. Search Console reports field data from real visitors on real phones and networks. Google ranks you on field data, so trust Search Console and the Chrome UX Report over a single lab run.

Can a caching plugin fix Core Web Vitals on WordPress?

Caching helps LCP by serving ready-made HTML, but it cannot fix a slow server underneath. It also does nothing for INP, which is a JavaScript problem, or CLS, which is a markup problem. If Time to First Byte is over a second, the fix is faster hosting where your site is not sharing resources, not another plugin.

How often does Google update Core Web Vitals data?

Google grades your site on a rolling 28 days of real Chrome visits, updated about daily. A fix only shows its full effect once enough visitors have seen the improved page, so expect two to four weeks.

Put this into practice on G7Cloud

Every site runs in its own dedicated container behind ScaleShield, with daily backups that are restore-tested every night. Start on the free plan, no card needed.

About G7Cloud Engineering

Platform team

Articles written by the engineers who build and run G7Cloud: UK managed hosting and the AI Website Builder. We write about what we operate every day: containers, backups, databases, and the small-business websites that run on them.

More about G7Cloud →