# LCP: what does Largest Contentful Paint measure?

> Largest Contentful Paint explained: what counts as the LCP element, the 2.5-second target, a worked image example and the mistakes small sites make.

Updated on October 15, 2026 · https://app.pilotiko.com/en/glossary/lcp

Largest Contentful Paint (LCP) is the time from the start of navigation until the largest image, text block or video in the visible part of the screen is rendered. Web.dev rates an LCP of 2.5 seconds or less as good, and anything above 4 seconds as poor, measured at the 75th percentile of visits.

## In short
- LCP times the main visible element, not the whole page load.
- Good is 2.5 s or less; poor is anything over 4 s.
- Images, videos, CSS background images and text blocks can all be the LCP element.
- It is one of three Core Web Vitals, alongside INP and CLS.

## What exactly does LCP time?

Web.dev defines LCP as the render time of the largest image, text block or video visible in the viewport, counted from when the user first navigated to the page [1].

So it is not the moment the whole site finishes loading. Scripts can still be downloading in the background while the visitor already sees the hero photo and the headline. From their point of view the page has arrived, and that is the moment LCP captures.

LCP is one of the three [Core Web Vitals](https://app.pilotiko.com/en/glossary/core-web-vitals), next to [INP](https://app.pilotiko.com/en/glossary/inp) for responsiveness and [CLS](https://app.pilotiko.com/en/glossary/cls) for layout stability [2].

## Which elements can become the LCP element?

| Element type | Typical case on a trades or services website |
|---|---|
| img element | Crew photo in front of the service van |
| image inside an svg element | Vector drawing of a house cross-section |
| video element | Short clip of a finished renovation |
| Element with a CSS url() background image | Full-width banner photo behind the headline |
| Block-level element containing text | Big heading such as Emergency plumbing in Moncton |

CSS gradients do not count as background images [1].

## What are the LCP thresholds?

Web.dev treats 2.5 seconds or less as good, over 2.5 and up to 4 seconds as needing improvement, and over 4 seconds as poor [1]. The value to watch is the 75th percentile of page loads, with mobile and desktop tracked separately [2].

Google Search Central gives the same target: aim for LCP within the first 2.5 seconds of the page starting to load [3].

## How much time can a lighter photo save?

**Estimate: the homepage photo of a landscaping company in Kelowna**

- Original hero photo size : 3.0 MB
- Size after resizing and compression : 0.4 MB
- Data removed from the critical path : 2.6 MB
- Assumed mobile throughput : 20 Mb/s, about 2.5 MB/s
- Download time avoided (2.6 ÷ 2.5) : about 1 s
- **= A mobile LCP measured at 3.3 s (needs improvement) could move to roughly 2.3 s, inside the 2.5 s target.**

## Why is LCP often poor on small business sites?

Service businesses love a big homepage photo, often shot on a phone and uploaded straight from the camera roll. It becomes the LCP element and weighs several megabytes. Add a heavy theme, downloaded fonts and an image slider, and the first meaningful visual arrives late.

When someone searches for a furnace repair on a cold January night, every second of blank screen is a second in which they can go back and call the next company in the list.

## What mistakes do people make with LCP?

- Only checking the homepage, when the booking or [quote](https://app.pilotiko.com/en/glossary/quote) request page is the one that brings in revenue.
- Lazy-loading the hero image, which makes the most important element arrive last.
- Treating LCP as full page load time.
- Testing on a wired office computer and declaring victory.
- Swapping one hero photo for a five-image carousel and multiplying the problem.

## Does Pilotiko work on LCP?

Pilotiko does not advertise LCP measurement. It builds and hosts your business website, with versions and rollback, and generates [search engine optimization](https://app.pilotiko.com/en/glossary/seo) basics such as the [XML sitemap](https://app.pilotiko.com/en/glossary/xml-sitemap). To see your real LCP, open the Core Web Vitals report in Google Search Console.

## Frequently asked questions

### What is a good LCP score?

Web.dev rates 2.5 seconds or less as good when measured at the 75th percentile of visits. Between 2.5 and 4 seconds it needs improvement, and above 4 seconds it is poor.

### How do I find my LCP element?

Browser performance tools show which element was picked as the largest contentful paint for a given page load. On a service business site it is usually the hero photo or the main heading.

### Does LCP measure the whole page load?

No. It marks the moment the largest visible element is rendered. Images further down and background scripts can keep loading afterwards.

### Can a logo be the LCP element?

Yes, if it is the largest visible element when the page loads, which can happen on very short pages. Most of the time a photo or a large heading is bigger.

### Is LCP the same on mobile and desktop?

No. Screen size, processing power and connection all change, and even the LCP element itself can differ. Web.dev recommends tracking both separately.

### Is LCP enough to judge site speed?

No. It says nothing about how quickly the page reacts to taps, which INP measures, or how stable it is, which CLS measures. Look at all three together.

## Sources

1. web.dev (Google), « Largest Contentful Paint (LCP) », https://web.dev/articles/lcp (accessed on 2026-10-15)
2. web.dev (Google), « Web Vitals », https://web.dev/articles/vitals (accessed on 2026-10-15)
3. Google Search Central, « Understanding Core Web Vitals and Google search results », https://developers.google.com/search/docs/appearance/core-web-vitals (accessed on 2026-10-15)