You click a link, the page starts loading, the text jumps as an image appears, and when you finally tap a button nothing happens for a moment. You have probably left websites like that, and so have your customers. Those frustrations are exactly what Core Web Vitals measure.
Core Web Vitals are Google’s metrics for real-world user experience: how quickly the main content loads, how quickly the page responds to interaction, and how stable the layout is. Good scores make visitors happier and support your search performance. This guide explains each metric in plain language and shows practical ways to fix them on a WordPress website.
What are Core Web Vitals?
According to web.dev, Google’s resource for web performance, the three Core Web Vitals and their “good” thresholds are:
- Largest Contentful Paint (LCP): measures loading. Aim for 2.5 seconds or less.
- Interaction to Next Paint (INP): measures responsiveness. Aim for 200 milliseconds or less.
- Cumulative Layout Shift (CLS): measures visual stability. Aim for 0.1 or less.
Google assesses these at the 75th percentile of real page visits, so most of your visitors need a good experience, not just those on fast devices.
Why Core Web Vitals matter
- User experience: faster, more stable pages keep visitors engaged and reduce frustration.
- Conversions: slow pages and laggy buttons cost enquiries and sales.
- Search: page experience is part of how Google evaluates pages, and healthy, fast sites are better candidates for features like AI Overviews.
How to measure your Core Web Vitals
Google Search Console
The Core Web Vitals report shows real-user data grouped by page type, split into mobile and desktop. Start here to see which groups of pages need attention.
PageSpeed Insights
Test individual pages to see both real-user data (when available) and lab diagnostics, with specific suggestions for improvement.
Chrome DevTools
For deeper investigation, the Performance panel shows what happens while a page loads and responds.
How to fix LCP (loading) on WordPress
LCP is usually your hero image, a large heading or a banner. To speed it up:
- Optimise the hero image. Resize it to the dimensions actually displayed, compress it and use a modern format such as WebP or AVIF.
- Do not lazy-load the main image. Lazy loading is great for images further down the page, but the LCP image should load immediately.
- Enable page caching. Use your host’s caching or a reputable caching plugin so pages are served quickly.
- Improve server response time. Quality hosting, a recent PHP version and a content delivery network (CDN) all help.
- Reduce render-blocking resources. Minimise and defer CSS and JavaScript that are not needed straight away.
How to fix INP (responsiveness) on WordPress
INP replaced First Input Delay as a Core Web Vital in March 2024. It looks at how quickly the page responds to clicks, taps and key presses throughout a visit. Poor INP usually means too much JavaScript.
- Audit your plugins. Remove plugins you do not use and replace heavy ones with lighter alternatives.
- Delay non-essential scripts. Chat widgets, social embeds, heatmaps and some trackers can load after the user interacts.
- Avoid bloated page-builder add-ons. Many add-on packs load scripts on every page even when not used.
- Limit third-party scripts. Each ad, pixel or widget adds work for the browser.
How to fix CLS (layout stability) on WordPress
- Set image and video dimensions. Include width and height so the browser reserves space.
- Reserve space for banners and ads. Cookie notices, promotional bars and embeds should not push content down after loading.
- Load web fonts carefully. Use font-display settings and preload key fonts to reduce text shifting.
- Avoid inserting content above existing content unless it responds to a user action.
A practical example
A typical small-business WordPress site might have a large, uncompressed hero photo, a slider plugin, a chat widget, three tracking scripts and a page builder add-on pack. Replacing the slider with a single optimised image, delaying the chat widget, removing unused add-ons and enabling caching often turns failing scores into passing ones without changing the design at all.
Keep scores healthy over time
Core Web Vitals change as you add content, plugins and features. Check them monthly as part of your website maintenance checklist, and test after every major update. Good performance also supports mobile-first design, because mobile visitors feel slow pages most.
Quick WordPress performance checklist
- Hosting uses a current PHP version and server-level caching.
- A single, well-configured caching plugin is active (not several competing ones).
- Images are resized, compressed and served in WebP or AVIF.
- Below-the-fold images and videos are lazy-loaded; the hero image is not.
- Unused plugins, themes and page-builder widgets are removed.
- Third-party scripts are limited and delayed where possible.
- Fonts are limited to the weights you actually use.
- A CDN serves static files to visitors closer to them.
How Core Web Vitals connect to your business goals
It is easy to treat performance as a purely technical score, but the real goal is business results. A page that loads fast and responds instantly lets visitors read your offer, trust your brand and contact you without friction. That is why speed should be part of every project from the start, not an afterthought. If you are planning a new site, our guide to website costs in 2026 explains why performance foundations are worth budgeting for.
When to call in a professional
Some fixes, like compressing images or removing an unused plugin, are quick wins you can do yourself. Others need technical expertise: diagnosing slow database queries, rebuilding heavy templates, replacing a bloated theme or configuring server caching and a CDN. If your scores stay poor after the basics, or if changes risk breaking your design, a developer can usually find and fix the real bottleneck much faster.
Frequently asked questions
Where can I check my Core Web Vitals?
Use the Core Web Vitals report in Google Search Console for real-user data and PageSpeed Insights to test individual pages.
Does INP replace FID?
Yes. INP replaced First Input Delay as the responsiveness metric in Core Web Vitals in March 2024.
Why do my PageSpeed scores change every time I test?
Lab tests vary with network and server conditions. Focus on trends and on the real-user data in Search Console rather than a single test result.
Need a faster WordPress website?
MinifyTech diagnoses and fixes slow WordPress sites, from image optimisation and caching to plugin clean-ups and hosting advice. Request a quote for a speed audit, or add ongoing performance checks with our maintenance plans.



