Definition
Largest Contentful Paint is the time it takes the largest image, text block or video in view to render. It is the loading performance measure among Google's three Core Web Vitals, which Google describes as measuring real-world user experience, and a good LCP is 2.5 seconds or less.
Example. A product page whose hero photo finishes rendering 3.1 seconds after the page starts loading has an LCP of 3.1 seconds, which sits in the needs improvement band.
You can see your page's LCP from real visitors, next to sites ranking in your niche, with the free Is My Page Speed Really a Problem? tool.
What is a good LCP score?
A good LCP score is 2.5 seconds or less. Anything over 4 seconds is poor, and the band in between needs improvement. The figure that counts is the 75th percentile of page loads, segmented across mobile and desktop, so a fast median does not pass a page whose slowest quarter of visits is slow.
| LCP | Band |
|---|---|
| 2.5 seconds or less | Good |
| Over 2.5 and up to 4 seconds | Needs improvement |
| Over 4 seconds | Poor |
How often do ranking sites fail LCP?
Ranking sites fail LCP more often than either of the other Core Web Vitals. In our benchmark of 38,950 domains ranking across 12 niches and 5 markets (July 2026 field data, phones), LCP was the metric failing most often in 58 of the 60 niche and market groups. Between 16% and 52% of the measured sites in a group failed it.
Two limits travel with those numbers. They describe sites ranking in a niche and market, not an industry average. And the benchmark has no ranking variable, so it shows how common a slow LCP is among sites that rank anyway, not what fixing it is worth.
Which element counts as the largest contentful paint?
The element that counts is the largest image, video or block of text visible in the first screen. The candidates are <img> elements, images inside an SVG, video poster images or first frames, background images loaded with url(), and block-level elements containing text. That is why a large hero image is the usual culprit, and why it is the first thing to check.
How do you improve LCP?
You improve LCP by finding which of its four parts is slow and fixing that part, rather than working through a generic speed checklist. web.dev splits every LCP into the same four parts and gives a rough target share of the total for each, as a guideline rather than a rule.
| Part | What it is | Rough share | The main fix |
|---|---|---|---|
| Time to first byte | Until the browser receives the first byte of HTML | About 40% | Fewer redirects, fewer cache misses at the CDN edge |
| Resource load delay | From first byte until the LCP image or font starts loading | Under 10% | Make the resource discoverable in the HTML, and never lazy-load the LCP image |
| Resource load duration | Loading the LCP resource itself | About 40% | Smaller files, served closer, cached |
| Element render delay | From the resource arriving until the element is painted | Under 10% | Fewer render-blocking stylesheets and scripts |
The two delays are the usual surprise: on many slow pages the image itself is fine, and the time goes on the browser not knowing about it yet, or not being free to paint it.
Does LCP affect rankings?
Google describes Core Web Vitals as aligning with what its core ranking systems seek to reward, and recommends good scores for success with Search. It stops short of saying how much they weigh against relevance, so treat a poor LCP as a real cost to visitors first, and a ranking question second.
Sources
- web.dev: Largest Contentful Paint (LCP)
- web.dev: Optimize Largest Contentful Paint
- Google Search Central: Understanding Core Web Vitals and Google search results
- Hawk Academy: Core Web Vitals benchmark of sites ranking in 12 niches and 5 markets
Last checked against these sources on 26 October 2026.