How to improve LCP in WordPress and pass Core Web Vitals

Tap a link, watch the screen sit blank for a beat too long, and you start to wonder whether something broke. That pause before the main image or headline finally lands is exactly what Largest Contentful Paint measures, and on WordPress it’s the speed problem most sites get wrong.

LCP is the hardest of Google’s three Core Web Vitals to pass. As of 2025, only around 62 percent of mobile pages hit a good score, so if yours is lagging, you’re in crowded company, and there’s real ground to take from competitors who haven’t sorted theirs out either. The causes are well understood: slow hosting, no page caching, oversized hero images, and an LCP element the browser discovers too late. Most sites are guilty of more than one.

This guide covers what LCP actually measures, why it matters for your traffic, rankings, and conversions, and how to get it under Google’s 2.5-second mark on a WordPress site, without writing code or guessing at which element to target.

If you’re looking at broader performance improvements, it’s also worth understanding how to speed up your WordPress site as a whole.

• LCP measures when your main content actually appears, usually the hero image, headline, or large text block in the visible part of the page. It’s the moment a visitor feels the page is ready, not just that something started loading.
• A good score is 2.5 seconds or less, measured at the 75th percentile of real mobile and desktop visits. Three out of four visitors need to see your main content within that window for the page to pass.
• LCP is the hardest Core Web Vital to pass, with only around 62 percent of mobile pages hitting a good score in 2025. That makes it both a common weak spot and a realistic place to gain ground on competitors.
• Most slow LCP on WordPress comes from a few fixable causes: slow hosting, no page caching, oversized hero images, render-blocking code, and an LCP element the browser finds too late.
• Caching, image compression, and minification handle most of the work, and a good performance plugin can apply them without code. The fiddly part is preloading the right element, which is where most sites get stuck.

Largest Contentful Paint measures how long it takes for the largest piece of content in the visible part of your page to appear, timed from the moment a visitor starts loading it. On most WordPress sites that largest element is a hero image, a big headline, a block of text, or a video thumbnail.

Think of it as a stopwatch on the question every visitor asks without realizing it: has the main thing I came here for actually shown up yet? First Contentful Paint tells you when the browser drew anything at all, which might only be a loading spinner. LCP tells you when the content that matters is on screen.

One quirk worth knowing: the largest element can change as the page loads. The browser might paint your headline first, then switch to your hero image once it finishes downloading. LCP tracks whichever element ends up largest in the viewport.

Google sets three bands:

• Good: 2.5 seconds or less
• Needs improvement: 2.5 to 4 seconds
• Poor: more than 4 seconds

The catch is in how it’s measured. Google looks at the 75th percentile of real visits across mobile and desktop, making it important to optimise your WordPress site for mobile users as well. Three out of four people need to see your main content within 2.5 seconds for the page to pass. One fast load on your own laptop doesn’t count for much when a quarter of your visitors are waiting twice as long on a phone.

LCP is also the hardest of the Core Web Vitals to pass. As of 2025, only around 62 percent of mobile pages hit a good score. If yours is lagging, you’re in large company, and there’s real ground to gain on competitors who haven’t sorted theirs out either.

Three reasons, in rough order of how much they tend to sting.

Visitors judge your speed by it. A fast LCP reassures people the page is working and worth their attention. A slow one sends them back to the search results, often before they’ve read a single word.

It affects your Google ranking. LCP is one of three Core Web Vitals, alongside Cumulative Layout Shift and Interaction to Next Paint, that Google factors into search ranking. A slow score can quietly hold back a page that otherwise deserves to rank.

It costs you money. On a store or a landing page, the seconds before your main content loads are the seconds when people decide whether to stay. Faster pages convert better, and LCP is the part of page speed your visitors feel most directly.

WordPress has a handful of common culprits, and most sites have more than one:

• Slow hosting. Budget shared hosting can take a long time to deliver the first byte of your page, and that delay is counted in your LCP before anything even renders.
• No page caching. Without it, WordPress rebuilds each page from PHP and the database on every single request, while your visitor waits.
• Oversized hero images. A 2 MB header image is often the LCP element itself, which makes it the single biggest thing standing between your visitor and a finished page.
• Render-blocking code. Themes and plugins load stylesheets and scripts that the browser has to work through before it can paint your main content.
• Late discovery of the LCP image. The image that defines your score is often buried deep in the HTML or pulled in by CSS, so the browser doesn’t find it until late in the load.

The fixes are well understood, and a good performance plugin can handle most of them for you.

Start with caching, so your pages are served as finished copies instead of being rebuilt for every visitor. Compress and correctly size your images using proven image optimisation techniques, and serve them in a modern format like WebP. Minify your CSS and JavaScript, and defer the scripts that aren’t needed for the first screen. Then, for the element that actually defines your LCP, tell the browser to load it early instead of letting it find out late.

That last step, preloading the right element, is the fiddly one. You have to work out which element is the LCP element on each type of page, add the correct preload hint by hand, and redo it whenever your design changes. Get it wrong, and you can slow things down instead of speeding them up.

A lot of people treat Core Web Vitals as a box-ticking exercise, but that’s not how I look at it. LCP is one of the hardest metrics to pass, which means many of your competitors haven’t solved it either. If you can get your main content loading quickly, especially on mobile, you’re creating a genuine advantage. It’s one of the few ranking factors where improvements are entirely within your control.

Auto LCP in WP-Optimize Premium does that last step for you. Turn it on, and WP-Optimize detects the largest element on each page automatically and tells the browser to start loading it sooner, so your main content appears faster without you writing a line of code or guessing at which element to target.

It works alongside the caching, image compression, and minification already built into WP-Optimize, so you’re not speeding up the hero image while the rest of your load time goes untouched. You’ll find it in the Cache settings, on the Auto LCP tab. Switch the toggle on, and WP-Optimize takes it from there.

One honest note, because it’s worth setting expectations. Preloading the LCP element targets one of the most common causes of a slow score, the browser finding your main image too late. It works best with page caching switched on, since loading a hero image earlier won’t do much if your server is still slow to respond in the first place. Used together, they’re how you get a page that shows up fast and stays fast.

If you only change one thing after reading this, make it page caching, because nothing else you do to your LCP matters much while your server is still slow to respond. Get caching in place, compress and right-size your hero image, and clear the render-blocking code, and most WordPress sites land inside the 2.5-second mark or close to it.

The part that stops people is the last step: working out which element defines your LCP on each template and telling the browser to load it early. Do it by hand and you’re re-checking it every time your design changes. Auto LCP in WP-Optimize Premium does that detection for you and keeps it current, so the fiddly step that usually gets skipped is the one you no longer have to think about.

Run a fresh measurement once your changes are live, give the field data a few weeks to catch up to real visits, and check the score again. LCP isn’t a one-time fix you set and forget, it’s a number worth watching as your site grows.