Core Web Vitals for WordPress: Optimization Guide (2026)

Where WordPress loses on Core Web Vitals, the server first and then the LCP image, and which plugin settings to switch on and leave off.

Arjen Karel
Updated · 12 min read
Share

Core Web Vitals on WordPress in short

On phones, WordPress sites fail Core Web Vitals mostly on LCP, and most of that LCP is the wait for the server: according to the State of Web Vitals, 32.1% of WordPress sites have a good time to first byte, against 59.2% of all sites. Start with a page cache, then the LCP image, then switch off the plugin settings that hold scripts and CSS back.

How do WordPress sites score on Core Web Vitals?

According to the State of Web Vitals, 62.6% of WordPress sites pass all three Core Web Vitals on phones, against 69.7% of all sites. WordPress sites do better than average on INP and CLS and worse on LCP and the server's response time:

On phones WordPress All sites
Pass all three 62.6% 69.7%
Good LCP 69.7% 81.9%
Good INP 96.7% 91.8%
Good CLS 90.5% 88.9%
Good TTFB 32.1% 59.2%

On 82.7% of WordPress sites with an image LCP, the time to first byte is the largest of the four LCP parts on phones (on all sites 67.6%), and the download of the image is the largest on 1.4%. Converting images to WebP rarely fixes a WordPress LCP: the browser can't request the image before the server has sent the HTML. On Shopify, where the server is Shopify's, 95.7% of stores have a good TTFB; the Shopify guide covers what goes wrong there. Every WordPress metric: WordPress in the State of Web Vitals.

Core Web Vitals Assessment failed on WordPress: where do you start?

PageSpeed Insights shows "Core Web Vitals Assessment: Failed" when the real Chrome visitors of that page, or of the whole site, had an LCP, INP or CLS worse than "good" at the 75th percentile over the last 28 days. Open the mobile tab and look at which metric is orange or red: on WordPress it is usually LCP, and the first fix is a page cache, because everything on the page waits for the server. The Lighthouse score under it, even a 95, comes from one simulated page load; the assessment from your visitors' field data.

A WordPress audit often finds two or three settings behind the failure: the hero image is lazy loaded, the page cache skips the pages that matter, or the fonts come from three places at once. To improve Core Web Vitals on WordPress, work in this order:

  1. A page cache, at the CDN, the host or a plugin, checked while logged out.
  2. The LCP image in the HTML, out of lazy loading.
  3. On a page builder: no entrance animation and no slider in the first section.
  4. For slow taps: the plugin scripts each page loads.
  5. For layout shifts: images, ads, bars and CSS that arrives late.
  6. The optimization plugin's settings: which ones to leave off.

How to pass the Core Web Vitals has the same order for any site.

How do you speed up the server response on WordPress and WooCommerce?

A page cache sends a stored copy of the page instead of building it with PHP and database queries for every visitor, which shortens the time to first byte (TTFB) and with it First Contentful Paint (FCP) and LCP. Put the cache as close to the visitor as you can: the HTML cached at your CDN first, then the page cache at your host, then a cache plugin. Then check that logged-out visitors from your ads and newsletters get the cached copy.

A CDN that caches only images and stylesheets passes every page request on to your server. Cloudflare caches HTML only with a Cache Rule you set up yourself, or with APO, its ready-made add-on for WordPress: Configure Cloudflare for the Core Web Vitals has the settings. Many managed hosts run a page cache on the server, such as Varnish or nginx. On a host without a page cache, use a cache plugin: WP Rocket, LiteSpeed Cache on a LiteSpeed server, or the Fast cache of WP Core Web Vitals, which sends the cached page before WordPress and your other plugins load.

Some visitors skip every cache: logged-in users, a visitor with something in the cart, a URL with a query string the cache doesn't know, and every visitor when a plugin sets a cookie on each response. WP Rocket ignores gclid, fbclid and the utm_ parameters by default, LiteSpeed Cache does it with Drop Query String, and a CDN needs its own rule. WooCommerce cart, checkout and account pages and logged-in pages always come from WordPress itself: an object cache such as Redis, often a switch at your host, makes those faster.

For a developer: the cache header on the HTML response says who answered (HIT, MISS or BYPASS, and DYNAMIC on Cloudflare when it passes the page on). Read it logged out, then again with a new ?gclid= value. Find and fix a slow TTFB goes through those headers.

Which WordPress hosting is best for Core Web Vitals?

Hosting affects page speed and Core Web Vitals performance through one number, the time to first byte (TTFB), and the fastest hosts serve your pages from a cache. A fast WordPress host includes a page cache on the server and an object cache for logged-in and shop pages, lets a CDN keep your HTML at its edge, and runs a current PHP version. A cached page on a cheap host is faster than an uncached page on an expensive one.

Test what you have before you move. Load a page in a private window and read the TTFB in the Network panel of Chrome DevTools or in PageSpeed Insights. Then look at real visitors: this site's CrUX History report shows the TTFB of any domain per week over 25 weeks, free: compare your site with sites on the host you are looking at.

A faster host fixes the server part of LCP and nothing else. A lazy loaded hero or a slider is just as slow on the new server.

How do you fix a slow LCP image on WordPress?

WordPress gives the first large image in the content fetchpriority="high" (since version 6.3) and leaves the first images out of lazy loading. A slow LCP image on WordPress comes from what overrides that: a lazy load plugin, a theme or page builder that sets the hero as a CSS background, or a slider. According to the State of Web Vitals, the LCP element is a CSS background image on 42.5% of WordPress sites, against 28.9% of all sites, and the LCP image is lazy loaded on 14.5%.

Each optimization plugin keeps the first images out of its lazy loading: Exclude Leading Images in Perfmatters, Viewport Images in LiteSpeed Cache, and in WP Rocket Optimize Critical Images, which is always on. WP Core Web Vitals learns from your visitors which image is the LCP element on each page and screen size, and loads that one first with high priority. A hero that the theme or builder sets as a background has to become a normal image, and so does the first slide of a slider.

For a developer, a hero in a theme template: with these two attributes WordPress adds the width, height and srcset and leaves out the lazy loading:

<?php
echo wp_get_attachment_image( $hero_id, 'full', false, array(
    'fetchpriority' => 'high',
    'loading'       => false,
) );
?>

The fix fails when a lazy load plugin moves the image URL into data-src, or when a logo at double size takes the high priority WordPress gives the first large image. A preload is for an image the HTML can't name, such as a background that has to stay, and it needs fetchpriority="high" too. LCP request discovery has the details.

Only then the file: the size the screen needs, in WebP or AVIF, which an image plugin such as Imagify or ShortPixel makes from the media library. Optimize the LCP image goes through the file itself.

Can an Elementor site pass Core Web Vitals?

Yes: an Elementor page passes Core Web Vitals when its first screen has the hero as an image in the HTML, and no entrance animation and no slider.

Elementor adds a hero as a Container background by default, and I see it almost every day. The browser finds a background image only after it has read the stylesheet, and by default every phone gets the desktop file. An Image widget with object-fit: cover puts the photo in the HTML with a srcset: faster Elementor hero images shows the steps.

Then set Advanced > Motion Effects > Entrance Animation to None on the first section. The animation holds the downloaded photo back until its fade ends, and LCP waits with it. On a test page built like an estate agent's WordPress site, with Elementor and a slider, fixing one LCP part at a time took LCP on a throttled phone from 6.70 to 2.18 seconds. Converting the photo to WebP shortened its download by 2.5 seconds, and 1.9 seconds of that moved into element render delay, the wait between download and paint. LCP breakdown has each step.

Chrome DevTools Performance panel with the LCP breakdown insight open: the four parts as bands under the timeline, the photo's request in the Network track ending at the start of Element render delay 1,920 ms, and a fadeIn animation in the Animations track running to the LCP marker

The estate agent test page in Chrome DevTools, after the WebP step.

Does a lightweight or custom theme help?

A custom theme or a light theme such as Astra improves Core Web Vitals performance through what it loads on every page: less CSS and JavaScript than a multipurpose theme that loads the styles of every layout it offers. Whether a page passes depends more on its first screen than on its theme: Astra can pass Core Web Vitals, and so can a heavier theme whose first screen is built well.

How do you fix INP on WordPress?

According to the State of Web Vitals, 96.7% of WordPress sites have a good INP on phones, against 91.8% of all sites. A slow tap on WordPress usually comes from a heavy plugin script, a theme or WooCommerce script on a filter or the cart, or a setting that holds scripts back until the first tap.

Perfmatters' Script Manager and Asset CleanUp unload a plugin's scripts and styles on the pages that don't use it, such as a form plugin on your product pages. The number of plugins matters less than what each one loads on each page. Never unload wp-polyfill: WordPress then drops every script that needs it, the cart and checkout included. Find the plugin that loads it and load that plugin only where it is used. Swap an analytics plugin that adds its own script, such as MonsterInsights, for one that adds only Google's tag, such as Site Kit by Google.

Delay JavaScript execution in WP Rocket, Delay JavaScript in Perfmatters and Load JS Deferred set to Delayed in LiteSpeed Cache hold the scripts back until the first tap or scroll. That wins a Lighthouse score, because Lighthouse never taps. A real visitor taps the menu and waits while the browser downloads and runs all of it, and INP reports the slowest tap of the visit. Leave those settings off. WP Core Web Vitals defers scripts in their original order and loads analytics and chat widgets after the page has loaded, without waiting for a tap.

For what is still slow after that, ask a developer for a trace of the slow tap: find and fix INP issues shows how to record one.

How do you fix CLS on WordPress?

Since version 5.5, WordPress adds width and height to images from the media library, so layout shifts on WordPress usually come from elsewhere: a theme or builder image without a size, an ad slot, a bar or consent banner that pushes the page down, a font swap, or CSS that an optimization plugin loads late. The goal is a CLS of 0.

  • Images: WP Rocket's Add missing image dimensions (under Media) and the Add missing width and height setting in WP Core Web Vitals both add width and height to the theme's images that lack them.
  • Ads: give the ad plugin's slot the height of the ad size that shows most often. In AdSense, Excluded areas keep auto ads out of the first screen.
  • Bars and consent banners: switch the plugin to a bottom bar, a box or a popup. Those float over the page and move nothing.
  • Late CSS: exclude the theme's stylesheet from the optimization plugin's delayed or asynchronous CSS, or switch that setting off.
  • Fonts: use fewer web font files and preload one or two, the font of your largest first-screen text first, since that text can be the LCP element. Match the fallback font with metric overrides in Additional CSS. Font display has the CSS, and how to check your LCP afterwards.

Cumulative Layout Shift (CLS) has the code for each cause.

Which WP Rocket, LiteSpeed Cache and Perfmatters settings help Core Web Vitals?

Use one caching and optimization plugin, and switch on its page cache, the setting that keeps the first images out of lazy loading, deferred JavaScript and missing image dimensions. Leave off the settings that delay JavaScript or rewrite your CSS: they win a Lighthouse score and make real visits slower. Two optimizers on one site undo or double each other's work.

  • WP Rocket. Switch on: Page cache, Load JavaScript deferred, Add missing image dimensions. Leave off: Delay JavaScript execution, Remove Unused CSS, Load CSS asynchronously.
  • LiteSpeed Cache. Switch on: Page cache, Drop Query String, Load JS Deferred: Deferred, Viewport Images and Add Missing Sizes (both need Lazy Load Images on). Leave off: Load JS Deferred: Delayed, Generate UCSS, Load CSS Asynchronously.
  • Perfmatters. Switch on: Script Manager, Exclude Leading Images, Defer JavaScript, Add Missing Image Dimensions. Leave off: Delay JavaScript, Remove Unused CSS.

Remove Unused CSS and the critical CSS behind Load CSS asynchronously build separate CSS for every page, usually inline in the HTML, so every page view downloads it again. Where that CSS misses a rule, the page jumps when the rest of the CSS arrives. Stylesheets of about 15 kB compressed each, with the tiny ones combined, load fast and stay in the browser's cache. With deferred JavaScript, an inline script that needs jQuery can break: exclude jQuery from the defer, or follow defer jQuery in WordPress.

On WordPress I kept looking for a plugin that loads a page the way I would build it by hand, and when I couldn't find one, I built it. WP Core Web Vitals keeps your CSS in a few files of 12 to 14 kB the browser caches, loads the LCP image your visitors report first, and makes no script wait for a tap. It is free, and it replaces your current optimizer.

A plugin does what a good developer can do in a few hours. A slider that builds the hero in JavaScript is still there afterwards.

How do you check Core Web Vitals on WordPress after a change?

Check a change logged out, in a private window, on the second load so the cache is warm. Logged-in users skip the page cache and most optimizations, so what you see logged in differs from what your visitors get.

Run Lighthouse again on the mobile tab of PageSpeed Insights for the pages that failed, then watch real visitors. CoreDash shows the new values per page from the next visits on; with Tag login status on in its WordPress plugin it splits TTFB and LCP into logged-in and logged-out visits, so you see who skips the cache.

Repeat the check after every theme, builder or plugin update: an update can switch a setting back, add a script to every page or put the hero back in a background. In Search Console a fix takes up to 28 days to turn green.

No setting fixes a theme that sends megabytes of CSS to every page, a WooCommerce filter that rebuilds the whole page on every tap, or a host whose cache your pages keep skipping. If the assessment still fails on mobile after the cache, the image and the plugin settings, a power hour finds which of those it is on your site.

About the author

Arjen Karel is a web performance consultant and the creator of CoreDash, a Real User Monitoring platform that tracks Core Web Vitals data across hundreds of sites. He also built the Core Web Vitals Visualizer Chrome extension. He has helped clients achieve passing Core Web Vitals scores on over 925,000 mobile URLs.

Arjen Karel

Need a faster site?

I'm Arjen, and I've been fixing slow sites for 17 years. If you're running into issues you can't fix yourself, send me your URL and let's have a chat.

Send me your URL
Arjen Karel
Arjen Karel, Web performance consultant since 2009

Why isn't our fix working?

Sometimes the CDN still serves the old HTML, or the fix went into the desktop template and mobile uses another one. Send me your URL and the problem, and I reply with a few times. I check your field data first, then we spend one hour on your site, and within a day you have my notes in writing. €350 excl. VAT.

Send me your URL

No developer to build the fix? I do the work myself, on a copy of your site.

Arjen KarelCore Web Vitals still red on mobile?Send me your URL