Black FridayCyber Monday 2026
15Days
07Hrs
09Mins
11Secs
Flat20% OFF

Our biggest sale of the year20% off the first payment on all maintenance plans. Code BF2026

Grab the deal
WordPress

Largest Contentful Paint in WordPress: Why Your Main Content Loads Late and How to Fix It

Visitors judge your page by when the main content appears. Find the LCP element, split the delay into four parts, and fix the biggest part first, with steps for WordPress.

wpallsolution Updated 9 min read

Largest Contentful Paint in WordPress is the metric behind one question every visitor asks silently: when does the main thing on this page actually show up? Until then they stare at a half-empty screen, and some of them leave. The good news is that LCP is one of the more fixable speed problems, because it usually comes down to a single element. This guide shows you how to find that element, split the delay into four parts, and fix the part that is really costing you time.

Quick answer

Web.dev says a good LCP is 2.5 seconds or less, measured at the 75th percentile of page loads. LCP records when the largest image, text block or video in the visible area is rendered. To improve it, do these in order: find the LCP element in PageSpeed Insights, check whether the server is slow to send the first byte, make sure the LCP image is not lazy-loaded and starts loading early, size and compress it properly, check fonts if it is text, and then look at what delays the paint (render-blocking files, fade-in animations). Measure after each change.

How this guide was prepared: the steps follow the web.dev and WordPress documentation listed under Sources, read on October 21, 2026. The example near the end is a lab test on our own homepage, not a promise of the same result on your site. Results depend on your host, theme, plugins and images.

Before you change anything

  • Back up the site and test big changes on staging. See Is your WordPress backup really safe?
  • Test the mobile result first. Slow LCP shows up on phones before desktop.
  • Run each test three times. Single runs vary, so write down all three before you change anything.
  • Change one thing at a time and clear caches between tests.

Largest Contentful Paint in WordPress: the decision tree

Largest Contentful Paint in WordPress flowchart: five questions covering server response, image priority, image size, fonts and render delay
Five questions show which part of the LCP delay is costing you the most.
  1. Is the first byte of the page slow (high TTFB)? Look at the server, caching and redirects (Step 2).
  2. Is the LCP element an image that is lazy-loaded or hidden in CSS? Fix image discovery and priority (Step 3).
  3. Is the image much larger than it is shown? Fix size and format (Step 4).
  4. Is the LCP element text that waits for a font? Look at font loading (Step 5).
  5. Does the element load quickly but appear late? Look at render delay (Step 6).

Symptoms and likely causes

What you seeLikely causeStart with
Everything is slow, even before anything paintsSlow server response or redirect chainStep 2
Hero image appears late, rest of the page is fineImage starts loading late or is lazy-loadedStep 3
Image downloads for a long timeFile is too big or in an old formatStep 4
Headline appears lateWeb font or CSS blocks the textSteps 5 and 6
Fast download, still late on screenRender-blocking CSS and scripts, or a fade-inStep 6
Lab test is fine, real users are slowSlower phones and networks than your testStep 7

7 steps to fix Largest Contentful Paint in WordPress

Step 1: Find the LCP element before you touch anything

Do not assume it is your hero image. Web.dev lists what can be an LCP candidate: image elements, images inside SVG, video poster images, elements with a CSS background image loaded with url(), and block-level elements that contain text. On a page with text and a hero image, the browser may first report a heading and later the image. Run the page through PageSpeed Insights and open the diagnostics for the LCP element. Check your home page, a post and your most important landing page, because each can have a different element.

Step 2: Check the time to first byte

Web.dev says a high Time to First Byte (TTFB) can make a 2.5 second LCP challenging or even impossible. It names causes such as multiple server redirects, visitors far from the server, poor network conditions, and not being able to use cached content because of query parameters. In WordPress, that usually means: a page cache is missing or misconfigured, the host is slow, or the URL goes through a redirect chain, for example from http to https and then from non-www to www. Fix the redirect so it takes one hop, turn on page caching, and ask your host about PHP version and server-side caching. If TTFB is already good, move on.

Step 3: Make sure the LCP image starts loading early

Web.dev explains that the LCP resource should be discoverable in the initial HTML, so the browser can start loading it right away. Two things get in the way.

The first is lazy-loading: a lazy-loaded hero image waits until the browser decides it is near the screen. WordPress core has handled this since version 6.3: its notes say WordPress now adds fetchpriority="high" to the image it thinks is the LCP image, and improves the automatic decision of when to leave out loading="lazy". Core will not put both attributes on the same image, because lazy-loading an image that is also marked high priority is an anti-pattern. Themes, builders and caching or optimization plugins can still override this, so check the final HTML in your browser.

The second is a CSS background image: the browser finds it late unless it is preloaded. Where you can, use a normal img element for the hero.

Step 4: Send the right size, in the right format

If the LCP image is 3,000 pixels wide and displayed at 800, you are making every visitor download pixels they never see. Upload images at the size you need, let WordPress generate its responsive sizes, and use a modern format such as WebP or AVIF where your setup supports it. One warning from web.dev: making the file smaller helps only if the other parts are healthy too, because the time you save can just shift into the render delay. That is why you must look at all four parts of LCP, not only the file size.

Step 5: If the LCP element is text, look at the font

Web.dev notes that a text LCP element that needs a web font to render can be sped up by preloading that font. Use fewer font families and weights, host fonts on your own server if your setup allows it, and avoid loading a font that is only used far down the page. After the change, check that the headline still looks right while the font loads.

Step 6: Reduce the render delay

Render delay is the time between the LCP resource arriving and the element actually appearing. Web.dev’s target is that this part, like the first part, should be close to zero. Common WordPress causes are render-blocking CSS and JavaScript from many plugins, sliders that hide the first slide until a script runs, and animations that start an element at zero opacity.

On our own homepage we found exactly that: the hero text faded in from invisible, and a lab test showed most of the LCP time was render delay.

After we kept the text visible and only let it slide, and replaced two animated blurred shapes with cheaper gradients, the lab LCP dropped from about 3.0 seconds to about 1.4 to 1.8 seconds on a throttled mobile test. Your page will be different, so treat this as a method, not a guarantee.

Step 7: Check lab data and field data

A lab test shows one controlled run. Field data shows what real visitors experienced, at the 75th percentile. PageSpeed Insights shows both when enough visitors exist. If the lab score is good and field data is poor, your visitors have slower phones and networks than your test. In that case, make the page lighter instead of tuning for the test. For more on measuring before you change settings, see Elementor website slow.

Version and hosting differences

  • The automatic fetchpriority handling needs WordPress 6.3 or later.
  • Page builders, sliders and optimization plugins can change image attributes, so inspect the final HTML.
  • CDN and cache settings differ by host, and some hosts already add their own image or cache optimization.
  • Pages that depend on logged-in state, such as shops and membership pages, are often not page-cached.

How to verify the fix

  • PageSpeed Insights names the same LCP element, and its time is lower in three runs on mobile.
  • The LCP image is not lazy-loaded, and it appears early in the network waterfall.
  • The layout does not shift when the image or font arrives.
  • The page still looks right on mobile and desktop, and forms and checkout still work.

How to prevent it from happening again

Frequently asked questions

What is a good Largest Contentful Paint?

Web.dev says 2.5 seconds or less, measured at the 75th percentile of page loads across mobile and desktop.

Is the LCP element always my hero image?

No. It can be a heading, a paragraph, a video poster or a background image, and it can change as the page loads.

Should I lazy-load all images?

No. Images below the fold benefit from lazy-loading, but the image that is the LCP element should not be lazy-loaded.

Will a speed plugin fix it?

What to do next

Find the element, split the delay and fix the biggest part. If your Largest Contentful Paint in WordPress is still slow, keep the PageSpeed report and the LCP element name, and send them to your host or theme developer. If you would like a person to look, wpallsolution offers independent plugin support and WordPress maintenance plans. We cannot promise a score without seeing your site.

Sources and official documentation

Last reviewed: October 21, 2026. WordPress is a trademark of the WordPress Foundation. wpallsolution is not affiliated with or endorsed by the WordPress Foundation, Automattic or Google.

Keep reading

More guides

Need a hand with this?

Tell us what is happening. We reply with honest next steps.

Talk to us