CWV FOR WORDPRESS

Three metrics, measured at the 75th percentile of real visitors: LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1. Google reads these from field data in the Chrome User Experience Report, not from your Lighthouse run, so a green lab score is necessary but not sufficient.

Key takeaway: WordPress can pass Core Web Vitals, but its defaults fight you: heavy themes, plugin sprawl, and unoptimised media. Fix media and caching first, cut plugins second, and verify with field data, not lab scores.

• Heavy themes and page builders. Multipurpose themes and builders like Elementor and Divi ship large CSS and JavaScript bundles, much of it unused on any given page.
• Plugin sprawl. Every active plugin can add its own scripts and styles site-wide, even on pages that never use it.
• Unoptimised media. The media library serves whatever was uploaded. Large hero images with no WebP and no sizing are the most common LCP killer.
• No caching by default. A stock WordPress install renders PHP on every request. Without page caching, time to first byte suffers under load.

In order of impact: add page caching and a CDN; optimise and correctly size images (WebP, lazy-load below the fold); reduce the theme and plugin JavaScript you ship; and host on infrastructure that keeps time to first byte low. A good [managed or VPS host](/blog/best-vps-for-wordpress-2026/) does more for TTFB than any plugin. If your build is heavy enough that none of this is enough, that is the signal to consider [headless WordPress with Astro](/blog/headless-wordpress-astro-setup/), which removes the front-end weight entirely.

For the hands-on service version of this, see my [WordPress speed optimization](/wordpress-speed-optimization/) page; for the platform-agnostic list, the [Core Web Vitals checklist](/guides/cwv-checklist/).

• Installing three caching plugins. They conflict. Pick one page-cache plugin (or a host with caching built in) and stop.
• Optimising images by hand, once. New uploads undo it. Use a plugin or pipeline that converts to WebP and sizes on upload, every time.
• Chasing a 100 in Lighthouse. It is a lab toy. The Search Console report and field data are what rank you.
• Adding a performance plugin without removing the cause. A minifier on top of a bloated builder is a plaster, not a fix. Cut the bloat first.

Install nothing that only reports lab scores. Use the PageSpeed Insights field section and the Search Console Core Web Vitals report, both of which read real-user data. After a fix, field data takes about 28 days to fully reflect the change, so do not panic when the score does not move the next morning. Track the trend over weeks, not the number on any single day, and only call a fix done once the field data confirms it.