Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Speed & performance · Guide

How to Pass Core Web Vitals on a WordPress Site

Short answer

To pass Core Web Vitals on a WordPress site, get all three metrics to good at the 75th percentile of real visits: Largest Contentful Paint (LCP) of 2.5 seconds or less, Interaction to Next Paint (INP) of 200 milliseconds or less and Cumulative Layout Shift (CLS) of 0.1 or less. Measure first in PageSpeed Insights, fix the failing metric, then wait for the 28-day field data to catch up.

Key takeaways

  • A page passes only when LCP, INP and CLS are all good at the 75th percentile of real visits, on mobile and desktop separately.
  • Good means LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less, as of November 2026.
  • PageSpeed Insights field data covers the previous 28 days of real Chrome visits, so a fix takes up to 28 days to show there.
  • WordPress 6.3 adds fetchpriority=“high” to the first large image, and you must not lazy-load that image.
  • One page cache at a time is the rule: two caching plugins or a cache plus edge HTML caching that fight each other will slow the site, not speed it.

What are Core Web Vitals and what counts as passing?

A WordPress page passes Core Web Vitals when LCP is 2.5 seconds or less, INP is 200 milliseconds or less and CLS is 0.1 or less at the 75th percentile of real visits.

Core Web Vitals are three metrics that measure real-world user experience for loading, interactivity and visual stability.

Google Search Central says it highly recommends that site owners achieve good Core Web Vitals for success with Search (Understanding Core Web Vitals and Google search results). LCP measures loading, INP measures responsiveness and CLS measures visual stability.

Google judges each metric at the 75th percentile of page loads, separately for mobile and desktop, according to web.dev. That means at least 3 out of 4 real visits must meet the target on each device type.

MetricWhat it measuresGoodNeeds improvementPoor
LCPWhen the main content appears2.5 seconds or less2.5 to 4 secondsOver 4 seconds
INPHow fast the page reacts to taps and clicks200 milliseconds or less200 to 500 millisecondsOver 500 milliseconds
CLSHow much the layout moves while loading0.1 or less0.1 to 0.25Over 0.25

The bands in the table come from the PageSpeed Insights documentation, which lists the same thresholds for each metric. A page passes only when all three are good, so one red metric fails the whole assessment even if the other two are green.

How do you measure Core Web Vitals on a WordPress site?

Open PageSpeed Insights, enter a page URL and read the field data at the top before you look at the lab score below it.

PageSpeed Insights reports on the user experience of a page on both mobile and desktop, and it provides both lab and field data about a page, according to the PageSpeed Insights documentation. Field data comes from the Chrome User Experience Report (CrUX) and covers the previous 28-day collection period.

Run the test this way:

  1. Go to PageSpeed Insights and paste the full URL of one real page, not just the home page.
  2. Read the Mobile report first, then switch to Desktop, because mobile conditions are harder.
  3. Note which of LCP, INP or CLS fails in the field data, and write down the 75th percentile value for each.
  4. Scroll to the lab diagnostics below and note the named cause, such as a large image or a long task.

Google Search Central also points site owners to the Core Web Vitals report in Search Console, which groups pages by status and metric (Understanding Core Web Vitals and Google search results). Use Search Console to find which templates fail, then use PageSpeed Insights to diagnose one page from each failing template.

A low-traffic or new page may have no field data at all. The PageSpeed Insights documentation says a page needs enough real-user samples to appear in CrUX, and the tool falls back to origin-level data for the whole site when page-level data is missing.

Speed affects more than these three numbers, and does page speed affect SEO explains how Google treats page experience in ranking. Google says Core Web Vitals are used by its ranking systems, and also that good scores do not guarantee a top ranking.

What do you need before you start fixing them?

You need a backup, a list of your slowest pages, admin access to your site and a note of the current scores before you change anything.

Start with these items:

  • A full backup you can restore, made before any plugin or theme change.
  • PageSpeed Insights results for your home page and your 3 to 5 most visited pages or posts.
  • Access to WordPress admin, your caching plugin settings and, if you use one, your CDN dashboard.
  • A note of your WordPress version and your theme, so you can check whether a fix applies to your setup.

Fix one metric at a time and re-test after each change. Changing the cache, the images and the JavaScript all at once makes it hard to tell which change helped and which one broke something.

Your server sets the floor for every other fix. If the server is slow to answer, no image change will fix LCP, so check your host and PHP setup against WordPress hosting requirements before you spend hours on images.

How do you fix a slow LCP on WordPress?

Fix a slow LCP by making the main image smaller and loading it first, then cutting the time the server takes to answer.

The LCP element is usually the hero image or the main headline. PageSpeed Insights names the LCP element in its diagnostics, so find it there before you change anything, and follow the web.dev guide to optimizing LCP for the order of fixes.

Follow these steps in order:

  1. Open the failing page in PageSpeed Insights and find the named LCP element in the diagnostics.
  2. Resize the hero image to the largest size your theme shows, then compress it before you upload it.
  3. Upload WebP where your host supports it. WordPress has accepted WebP uploads since version 5.8, and AVIF uploads since version 6.5.
  4. Check the hero image in the page source and remove loading="lazy" from it if a plugin or theme added it.
  5. Turn on page caching so the server answers faster, and clear the cache after each change so you test the new version.

WordPress 6.3 added automatic help for this step. The WordPress developer reference for wp_maybe_add_fetchpriority_high_attr() shows the function was introduced in version 6.3.0, and it adds fetchpriority="high" to the first large image on the page.

That automatic help only works for images WordPress can see. If your theme loads the hero as a CSS background image or through a slider, WordPress cannot mark it, so change the hero to a normal image element or set the priority in the theme.

The image must also be large enough to qualify. The same developer reference notes a minimum size threshold of 50,000 square pixels for an image to be eligible as the high-priority image, and the WordPress core team reported that this change typically improves LCP by 5 to 10 percent.

For plugin-specific settings, how to configure WP Rocket for Core Web Vitals walks through the cache and file settings in that plugin. Use one caching plugin only, and do not run a second one beside it.

How do you stop layout shift (CLS) on WordPress?

Stop layout shift by giving every image, video, embed and banner a fixed size or reserved space before it loads.

CLS adds up every unexpected move of visible content while the page loads. A good CLS is 0.1 or less, and anything over 0.25 is poor, according to the PageSpeed Insights documentation.

Work through these causes:

  • Images and videos without width and height, which push text down when they arrive.
  • Ads, banners and cookie notices that appear at the top of the page after the content has loaded.
  • Web fonts that load late and change the height of paragraphs.
  • Content injected above existing content, such as a banner added by a plugin after the page first draws.

Set width and height on images and videos in your content and theme, and reserve a fixed-height space for any banner, ad slot or notice that loads late. If a plugin injects a banner with no reserved space, give it a fixed height in the theme or move it below the main content.

WordPress has added native lazy loading to images since version 5.5, and it skips the first 3 content images by default so the top of the page stays stable. Do not add a second lazy-loading plugin on top of that, because two systems can fight and shift the layout.

Check the fix in the lab report first. CLS in the lab only captures shifts during load, so a page can look clean in a single lab run and still shift for real visitors, which is why the 28-day field data is the final check.

How do you fix a slow INP on WordPress?

Fix a slow INP by cutting the JavaScript that runs when a visitor taps, clicks or types, starting with scripts you do not need.

INP measures responsiveness across the whole visit, not just the first click. A good INP is 200 milliseconds or less, and anything over 500 milliseconds is poor, according to Google Search Central.

INP replaced First Input Delay (FID) as the responsiveness metric on 12 March 2024. Older audit reports that mention FID are out of date, and what is INP explains the metric in more detail.

Follow the web.dev guide to optimizing INP and work through these steps:

  1. List every plugin that adds JavaScript to the front of the site, and remove the ones you do not use.
  2. Remove or delay chat widgets, social feeds and tracking pixels that run on every page but serve few visitors.
  3. Defer or delay non-essential JavaScript in your caching plugin, and exclude scripts that break when delayed.
  4. Keep forms and menus light, and avoid page-builder sections that load heavy scripts on pages that do not need them.

INP is a field-only metric, so the lab score cannot show it directly. The PageSpeed Insights documentation lists Total Blocking Time among its lab metrics but not INP, so use Total Blocking Time in the lab as a clue and INP in the field data as the verdict.

Heavy page-builder pages are a common cause on WordPress. If one template is slow to respond, how to speed up Elementor covers the settings that cut the scripts that builder loads.

How does page caching help Core Web Vitals?

Page caching helps by serving a saved HTML copy of a page instead of building it from PHP and the database on every visit.

Caching plugins store posts and pages as static files, which the WordPress optimization documentation says can improve performance several hundred times over for fairly static pages. That faster server answer cuts LCP, because the browser cannot draw the main content until the HTML arrives.

Set caching up this way:

  1. Turn on page caching in one plugin or in your host cache, not both at once.
  2. Exclude logged-in users, the cart, checkout and account pages from the cache.
  3. Clear the cache after you publish or change a page, then re-test the page logged out.
  4. Check the response headers for a cache HIT on a logged-out visit before you trust the result.

Edge caching can add a second layer. With Cloudflare Automatic Platform Optimization, Cloudflare serves your entire site from its edge network, including HTML, and it bypasses the cache for logged-in users, according to the Cloudflare APO documentation.

Cloudflare also says that when you use its WordPress plugin, it updates cached content within 30 seconds of a change. That short delay matters when you re-test, because a stale cached page will show the old scores.

If you use Cloudflare, Cloudflare cache rules for WordPress covers the cache settings for the site. Do not stack a page rule that caches everything on top of APO, because the two systems can serve stale pages.

How long does it take for a fix to show in field data?

A fix can show in lab results at once, but field data takes up to 28 days to fully reflect it because it covers the previous 28 days.

Field data in PageSpeed Insights is powered by the Chrome User Experience Report and covers the previous 28-day collection period, according to the PageSpeed Insights documentation. The data is updated daily, while the BigQuery version of the same dataset is updated monthly.

That rolling window means each day replaces about one day of old visits with new ones. A fix made today will move the 75th percentile gradually, and only after 28 days will the window hold nothing but visits from after the fix.

Do not re-test field data every day and expect a jump. Re-run the lab test after each change to check that the fix worked, then check the field data once a week and look for a steady trend.

How do you check that your fixes worked?

Re-run PageSpeed Insights on the same URLs, compare the lab diagnostics with the earlier run and watch the field data over the next 28 days.

Use this check after each round of fixes:

  1. Re-run PageSpeed Insights on the home page and each page you fixed, on Mobile first.
  2. Confirm the lab diagnostics no longer name the problem you fixed, such as the same large image.
  3. Confirm the Lighthouse Performance score is 90 or above, which the PageSpeed Insights documentation calls good, with 50 to 89 needing improvement and below 50 poor.
  4. Record the field values each week in a note, and compare the 75th percentile for LCP, INP and CLS with the numbers from before the fix.

A Lighthouse score of 90 or above is good, but the documentation also warns that good lab data does not necessarily mean real-user experiences will also be good. The field verdict is the one that counts for the Core Web Vitals assessment.

Also check the Search Console Core Web Vitals report after a few weeks. It groups pages by status, so you can see whether a whole template moved from poor to good or whether only the pages you tested by hand improved.

The lab test itself uses a simulated mid-tier device, a Moto G4, on a mobile network for mobile, according to the PageSpeed Insights documentation. Run the same test more than once, because network and hardware load can move the lab score between runs.

What mistakes should you avoid?

Avoid chasing the lab score, lazy-loading the hero image and running two caches at once.

  • Chasing the 0 to 100 lab score instead of the three field metrics, when only the field metrics decide whether the page passes.
  • Lazy-loading the hero image, which delays the LCP element and hurts the metric you are trying to fix.
  • Running two caching plugins, or a caching plugin plus edge HTML caching that you did not set up to work together.
  • Changing the cache, the images and the JavaScript in one go, so you cannot tell which change helped.
  • Judging a fix by field data the next morning, when the 28-day window still holds mostly old visits.
  • Ignoring mobile, when mobile is the harder test and the one most visitors use.
  • Adding a new chat widget, pop-up or tracking tag after you fixed INP, without re-testing the pages it loads on.

Frequently asked questions

How long does it take to pass Core Web Vitals on WordPress?

Lab results can improve on the day you fix the problem, but field data covers the previous 28 days, so it can take up to 28 days for the full window to reflect the fix. Most sites see the 75th percentile move gradually over 2 to 4 weeks. If the lab diagnostics still name the same problem, the fix did not work, and waiting will not help.

Do I need a plugin to pass Core Web Vitals?

No single plugin passes Core Web Vitals for you. You need page caching, correctly sized images, a hero image that is not lazy-loaded and JavaScript you have trimmed. A caching plugin helps with the server and script parts, and WordPress core already handles lazy loading and fetch priority for content images since version 6.3.

Why does my site pass on desktop but fail on mobile?

Google judges mobile and desktop separately at the 75th percentile, and mobile tests use a simulated mid-tier phone on a mobile network, which is slower than a desktop on a wired connection. Mobile pages also show the same large images and scripts on a smaller screen with less processing power. Fix the mobile report first, because it is the harder test.

Can I pass Core Web Vitals with a page builder?

Yes, but page builders add JavaScript and CSS that can hurt INP and LCP, so you need to trim what they load. Remove unused widgets and sections, defer non-essential scripts, keep the hero image as a normal image element and re-test the templates you use most. If one template stays slow, simplify that template before you change the whole site.

What should I fix first if all three metrics fail?

Fix the metric that is furthest from its target first, and start with the pages that get the most visits. In practice that often means the LCP image and the server answer, then layout shift from images without sizes, then the JavaScript behind a slow INP. Fix one metric, re-test the lab report, then move to the next.

Does passing Core Web Vitals guarantee a top ranking?

No. Google says Core Web Vitals are used by its ranking systems, and also that good scores do not guarantee a top ranking. Relevance and content quality still decide most of the result. Passing Core Web Vitals removes a disadvantage and gives visitors a faster, steadier page, but it does not replace good content.

Sources

  1. Web Vitals web.dev
  2. Understanding Core Web Vitals and Google search results Google Search Central
  3. About PageSpeed Insights Google for Developers
  4. Optimize Largest Contentful Paint web.dev
  5. Optimize Interaction to Next Paint web.dev
  6. wp_maybe_add_fetchpriority_high_attr() WordPress Developer Resources
  7. About Automatic Platform Optimization Cloudflare Docs

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test