Key takeaways
- Core Web Vitals are measured from real users at the 75th percentile: LCP ≤ 2.5 s, INP ≤ 200 ms, CLS ≤ 0.1.
- Always start with field data (Search Console, PageSpeed Insights “real users”), then use lab tools to diagnose.
- On WordPress, the biggest wins are usually: a lighter theme, an optimised hero image, fewer plugins and third-party scripts, and full-page caching.
- Fix layout shifts by reserving space for images, ads, embeds and web fonts.
Speed is not just a technical vanity metric. Slow pages lose readers, reduce conversions and give search engines a weaker page experience signal. Google’s Core Web Vitals condense user-perceived performance into three metrics. This playbook explains each metric and the WordPress-specific fixes that work — the same checklist we apply to every site we build and maintain.
1. The three metrics in plain language
| Metric | What it measures | Good | Poor |
|---|---|---|---|
| LCP – Largest Contentful Paint | How quickly the main content (usually the hero image or headline) appears | ≤ 2.5 s | > 4.0 s |
| INP – Interaction to Next Paint | How quickly the page responds visually after clicks, taps and key presses | ≤ 200 ms | > 500 ms |
| CLS – Cumulative Layout Shift | How much content unexpectedly jumps around while loading | ≤ 0.1 | > 0.25 |
Each metric is evaluated at the 75th percentile of page loads, separately for mobile and desktop. INP replaced First Input Delay (FID) in March 2024 and is stricter, because it considers every interaction during a visit.
2. Measure correctly: field data first
- Search Console → Core Web Vitals report: groups of URLs with similar issues, based on real Chrome users.
- PageSpeed Insights: the top section (“Discover what your real users are experiencing”) shows field data; the lower section is a lab test for diagnosis.
- Chrome DevTools → Performance panel: record interactions locally to find long tasks and layout shifts.
- Real-user monitoring: the open-source
web-vitalsJavaScript library can send metrics to your analytics for page-level detail.
If a page lacks enough Chrome traffic, PageSpeed Insights shows origin-level data or none at all. Test representative templates (homepage, article, product, category) instead of every URL.
3. Fixing LCP on WordPress
3.1 Identify the LCP element
PageSpeed Insights and DevTools tell you which element is the LCP. On content sites it is usually the featured image or the article title.
3.2 Make the LCP image fast
- Serve properly sized images using WordPress’ responsive
srcset, and avoid uploading 5,000-pixel photos for 800-pixel slots. - Use modern formats (WebP or AVIF). Recent WordPress versions support both in the media library, depending on the server’s image library.
- Never lazy-load the LCP image. Add
fetchpriority="high"to it. WordPress applies this automatically in many cases, but custom themes and page builders often override it. - Preload a hero image that is set as a CSS background, or better, render it as an
<img>.
3.3 Reduce server response time (TTFB)
- Use full-page caching (server-level or a caching plugin) so most visitors receive static HTML.
- Add a persistent object cache such as Redis for dynamic pages and WooCommerce.
- Choose hosting with modern PHP versions and enough CPU; cheap shared hosting is a common LCP bottleneck.
- Use a CDN to serve assets close to your visitors.
3.4 Remove render-blocking resources
Every stylesheet and synchronous script in the <head> delays rendering. Self-host fonts, combine or inline critical CSS, defer non-critical JavaScript and remove CSS from plugins that are not used on a given page.
4. Fixing INP on WordPress
INP problems come from JavaScript keeping the main thread busy, so the browser cannot respond quickly to input.
- Audit third-party scripts: chat widgets, A/B testing, heatmaps, social embeds and multiple analytics tags are frequent culprits. Remove what you do not use; load the rest after consent or on interaction.
- Limit page builders and heavy sliders that ship large JavaScript bundles to every page.
- Break up long tasks in custom code; yield to the main thread and debounce expensive event handlers like scroll and resize.
- Avoid layout thrashing: batch DOM reads and writes.
- Reduce DOM size: deeply nested builder markup makes every style recalculation slower.
Our own theme for this website uses vanilla JavaScript without jQuery, defers all scripts and loads one small slider library locally — a deliberate choice to keep interactions fast.
5. Fixing CLS on WordPress
- Always include
widthandheightattributes (or CSSaspect-ratio) on images and video embeds — WordPress adds them for media library images. - Reserve fixed space for ad slots, cookie banners and newsletter bars instead of pushing content down.
- Use
font-display: swapwith well-matched fallback fonts, or preload your main web fonts. - Do not insert content above existing content after load, except in response to user interaction.
- Animate with
transformandopacity, not with properties that change layout.
6. A WordPress performance stack that works
| Layer | Recommendation |
|---|---|
| Hosting | Current PHP version, HTTP/2 or HTTP/3, server-level caching, enough CPU and RAM |
| Theme | Lightweight, block or classic theme without bundled page-builder bloat |
| Caching | Full-page cache + object cache + browser caching headers |
| Media | Responsive images, WebP/AVIF, lazy loading below the fold only |
| Fonts | Self-hosted WOFF2, limited weights, preloaded primary font |
| Scripts | Deferred, minimal third parties, consent-gated tracking |
| CDN | Static assets (and optionally HTML) served from edge locations |
7. A repeatable optimisation workflow
- Pick the template with the most traffic and the worst field data.
- Run a lab test, note the LCP element, long tasks and layout shifts.
- Fix one category at a time (images, then render-blocking, then scripts).
- Deploy, verify in the lab, then wait for field data to update (Search Console uses a 28-day window).
- Click “Validate fix” in Search Console once improvements show.
8. Do not forget the business view
Performance work competes with other priorities. Tie improvements to outcomes you care about — bounce rate on landing pages, checkout completion, ad viewability — so the effort is justified and sustained. And remember: Core Web Vitals are one of many signals. A fast page with unhelpful content will not outrank a slightly slower page that answers the question better.
Conclusion
Most WordPress sites can pass Core Web Vitals without exotic tricks: a lean theme, optimised images, fewer scripts, good caching and solid hosting. Our maintenance plan includes a monthly speed review, and our technical SEO audit pinpoints exactly what slows your site down. Pair this with the security steps in our WordPress hardening checklist.