Core Web Vitals on WordPress: How to Pass in 2026
Practical fixes for LCP, INP and CLS on WordPress and Elementor sites.
Read articleIn this guide
Key takeaways
- Measure first with real-user data, then fix the slowest templates.
- Hosting and caching give the biggest improvements for most sites.
- Optimised images and fewer plugins and scripts do most of the rest.
- Change one thing at a time and keep a backup before every change.
Why speed matters
A slow website costs you twice: visitors leave before they enquire, and Google's page experience signals, including Core Web Vitals, favour pages that load quickly and respond smoothly. The good news is that most of the work to speed up WordPress follows the same proven steps.
This guide gives you the order to work in. For a deeper look at the three Core Web Vitals metrics, read our guide to Core Web Vitals on WordPress.
Step 1: Measure before you change anything
- PageSpeed Insights shows real-user data (when your site has enough traffic) plus a lab test with specific suggestions.
- Google Search Console groups your pages into good, needs improvement and poor for Core Web Vitals.
- Test your key templates: home page, a service page, a blog post and, for shops, a product and category page.
| Metric | What it measures | "Good" threshold |
|---|---|---|
| LCP | How quickly the main content appears | 2.5 seconds or less |
| INP | How quickly the page responds to taps and clicks | 200 milliseconds or less |
| CLS | How much the layout jumps while loading | 0.1 or less |
Step 2: Fix hosting and caching
- Use good hosting: cheap shared hosting is the most common cause of slow WordPress sites. Managed or well-specified hosting with server-level caching makes a dramatic difference.
- Run a current PHP version supported by WordPress and your plugins. Newer versions are faster and more secure.
- Turn on page caching, so most visitors get a ready-made page instead of WordPress building it each time.
- Add object caching (such as Redis) for busy or dynamic sites, including WooCommerce stores.
- Use a CDN to serve images and files from servers closer to your visitors.
Check your server response time. If the first byte takes over half a second to arrive, fix hosting and caching before anything else. No amount of image compression makes up for a slow server.
Step 3: Optimise images
- Resize images to the size they're actually displayed, and never upload huge camera originals.
- Use modern formats such as WebP or AVIF.
- Don't lazy-load the main image at the top of the page; WordPress lazy-loads images further down automatically.
- Set width and height on images so the layout doesn't jump as they load.
- Avoid sliders at the top of the page; a single, well-optimised image loads faster.
Step 4: Cut plugins, scripts and bloat
- Audit your plugins: remove anything you don't use, and replace heavy plugins with lighter alternatives.
- Limit third-party scripts: chat widgets, trackers, embedded videos and social feeds often slow pages more than WordPress itself.
- Defer non-essential JavaScript, so the page becomes usable before everything has loaded.
- Load scripts only where needed, for example a form plugin only on pages with a form.
- Use a lightweight theme, and be careful with page builders that add a lot of extra code.
Back up before every change. Minifying, combining and deferring scripts can break menus, forms or checkouts. Test on a staging copy where possible, and check key pages after each change.
Step 5: Fonts and database
- Use fewer font families and weights, and consider hosting fonts locally.
- Preload the main font used above the fold, with sensible fallbacks.
- Clean the database: old revisions, spam comments and expired data from removed plugins.
Want us to speed it up?Get a free audit with your speed issues and a prioritised list of fixes.
Get my free audit Quick checklist
- Measure key templates in PageSpeed Insights and Search Console.
- Upgrade hosting if server response is slow.
- Update PHP and turn on page caching and a CDN.
- Resize and convert images; keep the main image eager-loaded.
- Remove unused plugins and heavy third-party scripts.
- Defer non-essential JavaScript and test thoroughly.
- Simplify fonts and clean the database.
- Re-measure, then monitor monthly.
Speed is also part of technical SEO. Our technical SEO guide covers the other checks that help Google crawl and rank your site. And because outdated plugins slow sites down and create security risks, see our WordPress security checklist too.
WordPress speed FAQs
Which caching plugin should I use?
It depends on your host. Many managed hosts include server caching, and adding another caching plugin can conflict with it. Check what your host provides first.
Is Elementor slow?
Page builders add extra code, but a carefully built Elementor site on good hosting can still pass Core Web Vitals. The way the site is built matters more than the tool.
Will a faster site improve my rankings?
Speed is one of many ranking signals, so it rarely transforms rankings on its own. It does reliably improve user experience and conversions, which is reason enough.
How fast should my website load?
Aim for the main content to appear within 2.5 seconds for real users, and for the page to respond quickly when people tap or click.
The bottom line
To speed up WordPress, measure first, then work in order: hosting and caching, images, plugins and scripts, fonts and database. Change one thing at a time, back up first and re-test. A fast site keeps more visitors, wins more enquiries and gives your SEO a solid foundation.