How to Reduce LCP in WordPress: 9 Fixes That Actually Work

This guide gives you nine practical fixes to reduce LCP WordPress sites struggle with, ordered by the part of the load they speed up, plus a method to find which fix your page actually needs. Most slow LCP pages have one or two clear bottlenecks, not ten small ones.

What is a good LCP score?

A good LCP is 2.5 seconds or less for at least 75% of page visits, and anything above 4 seconds is poor. Largest Contentful Paint measures when the biggest image or text block in the viewport finishes rendering, which is usually the hero image, a featured image or the main heading.

web.dev’s guide to optimizing LCP splits the metric into four parts that add up to the total: time to first byte, resource load delay, resource load duration and element render delay. As a rough guide, about 40% each should go to server response and downloading the resource, and less than 10% each to the two delay phases. Knowing which part is too big tells you which fix to apply.

What are the 9 fixes that actually reduce LCP on WordPress?

The nine fixes below cover every LCP part, and on most WordPress sites the first four solve the problem. Measure before and after each one so you know what worked.

1. Use full page caching. Serve cached HTML through your host’s cache or a caching plugin so PHP and database queries do not run on every visit. This shrinks time to first byte more than any other change.
2. Put a CDN in front of the site. A CDN serves files, and ideally cached HTML, from locations near your visitors. It matters most when your audience is far from your server.
3. Remove redirects before the page. Links and ads should point at the final https URL. Each redirect adds a round trip before the HTML even starts.
4. Do not lazy load the LCP image. Make sure the hero or featured image has no loading=”lazy” attribute. More on this below.
5. Add fetchpriority=”high” to the LCP image. WordPress 6.3 and later adds it automatically to the image it judges most likely to be the LCP element, but page builders and custom heroes often bypass that logic, so check the HTML.
6. Keep the LCP image in the HTML. Hero images set as CSS backgrounds or injected by a slider script are found late. Use a normal img element, or preload the image if it must stay in CSS.
7. Compress and resize images. Serve WebP or AVIF, at the size it is displayed, with srcset so phones get a smaller file. A 2,000 pixel wide hero for a 400 pixel screen is a common waste.
8. Cut render blocking CSS and JavaScript. Remove unused plugin CSS, defer non critical scripts and avoid synchronous scripts in the head.
9. Replace sliders on the hero. Sliders often wait for JavaScript before showing the first slide. A static hero image is almost always faster.

Why is my LCP so high on mobile?

LCP is usually higher on mobile because phones have slower processors and networks, and because many WordPress themes send the same large hero image and the same scripts to every device. The field data in Search Console and PageSpeed Insights is split by device, so a page can pass on desktop and fail on mobile.

Common mobile only causes I see in audits:

• A different hero for mobile that is a CSS background image, so the browser discovers it late.
• No srcset, so phones download the full desktop image.
• Heavy scripts for menus and popups that delay rendering on slower CPUs.
• A cookie banner or popup that becomes the largest element and appears late.

Test with mobile emulation and network throttling in Chrome DevTools, and look at which element PageSpeed Insights names as the LCP element. On mobile it is often a different element than on desktop. Fix the mobile LCP element first, because Google’s mobile first indexing means the mobile version of your page is the one that counts most, and most visitors on many sites arrive on phones.

Does lazy loading hurt LCP?

Yes, lazy loading hurts LCP when it is applied to the LCP image itself, because the browser waits until layout is done before it even starts downloading that image. Lazy loading images further down the page is still a good idea.

web.dev documented this in its study on the performance effects of too much lazy loading. In HTTP Archive data, the median 75th percentile LCP was 2,922 ms for pages without lazy loading and 3,546 ms for pages with it. In an A/B test on WordPress archive pages, turning lazy loading off for above the fold images improved LCP by 13% on desktop and 15% on mobile. WordPress has since changed core to skip lazy loading for images it expects in the first viewport, but themes and plugins that add their own lazy loading can still undo that.

The quick check: view the page source, find the LCP image and make sure it has no loading=”lazy” and no data-src swap from a lazy load plugin. Most performance plugins have an option to exclude the first one or two images.

What does an LCP fix look like with real numbers?

Keep LCP in your monthly checks using my free SEO audit checklist, and check how your titles look while you are at it with the SERP snippet preview tool. If you want the work done for you, my technical SEO service handles Core Web Vitals fixes, and my WordPress website design builds start with a fast, simple hero by default. Faster pages help users and conversions, but no speed fix on its own guarantees rankings.

Frequently asked questions