A good Largest Contentful Paint (LCP) is 2.5 seconds or less; web.dev rates over 4.0 seconds as poor, measured at the 75th percentile of page loads on mobile and desktop separately. When the LCP element is an image, its file size and how early the browser starts downloading it usually decide the score.
LCP thresholds at a glance
Rating | LCP |
|---|---|
Good | 2.5 s or less |
Needs improvement | More than 2.5 s, up to 4.0 s |
Poor | More than 4.0 s |
The 75th percentile means three out of four visits should hit the target, not just your own fast connection.
What counts as the LCP element?
LCP measures when the largest image or text block in the viewport finishes rendering. According to web.dev, the candidates are:
- img elements
- image elements inside an SVG
- video elements
- elements with a background image loaded through CSS url()
- block-level elements that contain text
On many marketing pages, product pages and blog posts, the largest thing on the first screen is a photo. That is why images and LCP are so often discussed together.
How much do images affect LCP?
It depends on whether the LCP element is an image, and you can check that in PageSpeed Insights or Chrome DevTools. If it is, web.dev's breakdown of LCP into four parts shows where an image can cost time:
- Time to first byte: the server response. Images don't affect this.
- Resource load delay: the gap before the browser starts fetching the image. web.dev suggests keeping this under about 10% of LCP.
- Resource load duration: how long the image takes to download. web.dev suggests this is around 40%. File size drives it directly.
- Element render delay: the time from download to the image appearing. Also under about 10% in web.dev's guidance.
So an image can hurt LCP in two ways: it is too heavy (load duration), or it is discovered late or deprioritized (load delay).
How to fix a slow LCP image
Make the file smaller. web.dev's advice for load duration is to serve the optimal image size, use modern image formats and compress images. A hero photo straight from a camera can be several megabytes; resized and saved as AVIF it is often a few hundred kilobytes. In our sample run of 54 business photos at 2,048 px wide, the median AVIF was 220 KB, against a median original of about 3.0 MB.
Don't lazy-load it. web.dev is direct: never lazy-load your LCP image, because it always adds load delay. Lazy loading belongs on images further down the page.
Raise its priority. Add fetchpriority="high" to the LCP img, or preload it with high priority if it is a CSS background image. WordPress 6.3 and later adds fetchpriority="high" automatically to the image it judges most likely to be the LCP element, according to the WordPress core team's developer note.
Make it discoverable in the HTML. An image injected by JavaScript or hidden in a stylesheet starts downloading later than an img tag in the initial HTML.
Serve the right size to each screen. Use srcset and sizes so phones download a smaller file than desktops.
Does LCP affect SEO?
Google's documentation says Core Web Vitals align with what its core ranking systems seek to reward, and recommends good scores for success with Search. It also says good page experience does not guarantee higher rankings. Treat LCP as one part of a good page, not a shortcut to rankings.
Get the hero image right first
If your LCP element is a photo, our website image optimization workflow resizes, converts and compresses it, and on Starter and up writes responsive sizes for srcset. The Free plan covers your first 15 photos, once, as AVIF or JPG.
Keep reading
Sources
Questions
Short answers to what people ask about this.