Largest Contentful Paint is the metric that decides whether your WordPress page feels fast or slow. In 2026 the techniques that actually move LCP look very different from what worked five years ago. This guide is the short version of wordpress lcp optimisation that works in practice.
Start with an honest baseline
Run PageSpeed Insights against your slowest page. Note the LCP number from the field data section. That is what real users experience and what Google rewards. A lab score that looks better is misleading.
If LCP is above 2.5 seconds, the dominant cost is almost always image delivery. If it is below that, focus on other metrics.
Find the LCP element
In Chrome DevTools, open the Performance panel and record a page load. The LCP marker tells you which element Google considers the largest contentful paint. Nine times out of ten it is the hero image or the featured image of the article.
Now you know what to optimise. Everything else on the page can wait.
Preload and fetchpriority
Add fetchpriority=”high” to the LCP image. This tells the browser to grab it before scripts. For images discovered late by the parser, also add a link rel=”preload” with the image URL.
WordPress themes that follow current best practices already do this. If yours does not, a filter on wp_get_attachment_image_attributes can inject the attribute on the relevant image.
Move the image closer to the visitor
Preload only helps if the file is fast to fetch. If your hero image lives in /wp-content/uploads on a single Sydney server and your visitor is in London, no preload hint will save you. Offload the media library to an object store with a global CDN and the round trip drops by half or more. Defyn Media Offload makes this a single setup wizard followed by a background migration.
Once the CDN edge is serving the image, preload combined with fetchpriority gets you within a few hundred milliseconds of theoretical best.
Modern formats, the right size
WebP and AVIF are smaller than JPEG at the same visual quality. Most WordPress media plugins generate these formats automatically. Pair that with a properly sized srcset so a phone never downloads a desktop size image.
Format and size optimisation feel small individually. Stacked together they often cut LCP by twenty to thirty percent.
Frequently asked questions
How much can wordpress lcp optimisation realistically improve?
On a previously slow site, dropping LCP from four seconds to under two and a half is realistic with the techniques above. Past that point you are fighting physics.
Do plugins like WP Rocket handle this?
Caching plugins help with TTFB and HTML delivery. They do not fix slow image delivery. You need an offload plugin for that.
Is preload always a good idea?
Only for the LCP element. Preloading too many resources hurts more than it helps because it crowds out other requests.
What if my host already has a CDN?
A host CDN in front of your origin caches images but every miss still hits your server. Offloading the library to object storage takes the origin out of the path entirely.
Related reading
- Core Web Vitals and WordPress media delivery
- Why your media library is killing your page speed
- More SEO coverage
- Defyn Media Offload on WordPress.org – the plugin powering the techniques above.
