By · Published 27 April 2026 · Updated 29 September 2026

Largest Contentful Paint (LCP) is the time from when a page starts loading to when the largest element visible in the viewport finishes rendering. It is one of Google's three Core Web Vitals, alongside CLS and INP, and it is the one that best matches what a visitor means by "the page has loaded".

The thresholds are measured at the 75th percentile of real visits:

This guide covers what LCP measures, how to find the element that is setting your LCP, how to work out which of its four phases is slow, and the fix for each — plus the WordPress-specific causes that come up most often.

What LCP Actually Measures

As a page loads, the browser keeps track of the largest content element it has painted in the viewport so far. Every time something bigger appears, that becomes the new LCP candidate. Recording stops as soon as the visitor interacts — a tap, a scroll or a key press — and the last candidate standing is the LCP element. Its render time is the LCP value.

Only certain elements can be the LCP element:

In practice, on an article or landing page it is usually the hero image. On a product page it is the main product photo. On a text-only page it is often the headline or the first paragraph — which is why a slow web font can be an LCP problem.

How to Find Your LCP Element

You cannot fix LCP until you know which element it is, and it is frequently not the one you would guess — a cookie banner or a large block of intro text can beat the hero image. Three ways to find it:

  1. PageSpeed Insights or Lighthouse. In the Diagnostics section, the audit titled "Largest Contentful Paint element" (in newer versions, "LCP breakdown") shows the element itself, with the description "This is the largest contentful element painted within the viewport." Directly beneath it is the time spent in each of the four phases described below — the single most useful table for diagnosing LCP.
  2. Chrome DevTools. Open the Performance panel. The live metrics view shows your LCP as the page loads and names the element; hover it to highlight it on the page. Recording a trace adds an LCP marker to the timeline, so you can see what the browser was doing just before it.
  3. A few lines of JavaScript. Paste this into the console and reload to log each LCP candidate as it appears:
    new PerformanceObserver((list) => {
      const entries = list.getEntries();
      const lcp = entries[entries.length - 1];
      console.log('LCP', Math.round(lcp.startTime), 'ms', lcp.element);
    }).observe({ type: 'largest-contentful-paint', buffered: true });

Test on mobile settings. The LCP element on a phone is often a different element from the one on desktop, because the layout reflows and different content lands in the viewport.

LCP by Phase: Where the Time Goes

Google breaks every LCP into four consecutive phases. They add up exactly to the LCP time, so finding the largest one tells you what to fix:

PhaseWhat it coversTarget
Time to First ByteFrom navigation until the first byte of HTML arrives, including redirects, DNS, connection and server time~40%
Resource load delayFrom the first byte until the browser starts downloading the LCP resource<10%
Resource load durationHow long the LCP resource takes to download~40%
Element render delayFrom the resource finishing until the element is actually painted<10%

The shares are Google's own guidance, not hard rules, but they are a useful check. If load delay or render delay is taking a large part of your LCP, that time is almost entirely wasted, and it is usually the cheapest to win back. If your LCP element is text, the two resource phases are zero and everything happens in TTFB and render delay.

Fix 1: Slow Server Response (TTFB)

Google rates a TTFB of 0.8 seconds or less as good. On a 2.5-second LCP budget, TTFB much above a second leaves too little time for everything else, however well optimised the front end is.

In August 2026 we measured the homepage of every Australian domain in the Tranco top-1 million list — 6,421 sites that responded — for our Australian web delivery report. The median TTFB was 480 ms, measured from an Australian connection. A quarter of sites took longer than 924 ms, and 23% took longer than a full second — a large part of the budget spent before the browser has seen a single tag.

Two findings from that scan are directly relevant to LCP:

The fixes for a slow TTFB, roughly in order of how often they are the answer:

Fix 2: Resource Load Delay (Late Discovery)

If the LCP image is only discovered late — because JavaScript inserts it, or it is a CSS background — the browser spends time doing nothing about it. The fix is to make the LCP resource visible in the initial HTML and to mark it as important:

Fix 3: Resource Load Duration (a Heavy File)

The browser found the image promptly but it takes too long to download. Make it smaller — the image optimisation guide covers this in depth:

Fix 4: Element Render Delay

The image has arrived, but the browser cannot paint it yet because it is still busy with other work — usually CSS or JavaScript that blocks rendering. See render-blocking resources for the detail:

Largest Contentful Paint on WordPress

WordPress sites hit the same four phases, but the causes are predictable enough to check directly:

A Diagnostic Workflow

  1. Measure. Run the URL through Site Speed Check for the mobile and desktop LCP, the score against Google's thresholds, and the opportunities that affect it — server response time, redirects, render-blocking resources, image formats and sizing.
  2. Find the element using the Lighthouse "Largest Contentful Paint element" audit or the DevTools Performance panel.
  3. Find the slow phase in the phase breakdown, and compare it against the rough shares above.
  4. Apply the fix for that phase only. Optimising the image does nothing if the problem is a two-second TTFB.
  5. Check field data. Lab tests like Lighthouse use one simulated device and connection. Google's assessment uses real Chrome users over the previous 28 days, so after a fix, lab results change immediately while field data catches up over about four weeks.

The Short Version

Most slow LCPs come down to one of three things: a server that answers slowly because HTML is not cached, a hero image that is too heavy or found too late, or scripts in the head that delay painting. Find the element, find the slow phase, fix that phase. Once your 75th percentile is under 2.5 seconds, visitors see your main content in about the time they expect — and the page passes the Core Web Vital that sites fail most often.

Measure your LCP now

Site Speed Check reports LCP, CLS, INP, and the rest — instant diagnostics on what to fix first.

Run a Speed Test →

Slow server response dragging LCP? ModusOp hosting runs on LiteSpeed in Sydney →