LCP – Largest Contentful Paint
Largest Contentful Paint (LCP) is a Core Web Vital that measures loading performance — specifically when the largest visible element on the page finishes rendering.
Reviewed by Alexander Yarovenko · Updated: 2026-09-18
What is Largest Contentful Paint?
Largest Contentful Paint (LCP) is a Core Web Vital that measures perceived load speed — the point at which the largest content element visible in the viewport (an image, video poster, or block of text) finishes rendering. It's the best single metric for how fast a page feels to users.
LCP Score Thresholds
| LCP Time | Rating |
|---|---|
| < 2.5 seconds | ✅ Good |
| 2.5 – 4.0 seconds | ⚠️ Needs Improvement |
| > 4.0 seconds | ❌ Poor |
Elements That Can Be the LCP
<img>elements (including<picture>srcsets)<video>poster images- Elements with a CSS
background-image - Block-level text elements (headings, paragraphs)
How to Improve LCP
- Preload the LCP image using
<link rel="preload"> - Use a CDN to serve assets from servers close to the user
- Compress images and use modern formats (WebP, AVIF)
- Remove render-blocking CSS/JS that delays initial paint
- Improve TTFB — fast server responses directly speed up LCP
SEO Impact
LCP is one of Google's three Core Web Vitals used as ranking signals. A poor LCP (over 4 seconds) can negatively affect rankings, particularly for competitive queries where user experience differentiates results.
How to use this concept in SEO
LCP measures when the largest visible content element finishes rendering. Improve the whole path: server response, discovery and priority of the LCP resource, transfer size, and rendering delay.
Audit checklist
- Confirm that the implementation matches the page purpose and the user task.
- Check the HTTP response, rendered HTML, canonical, robots rules, and internal links together.
- Use Search Console and analytics to verify the result instead of relying on one crawler signal.
- Test a representative URL on mobile and desktop after deployment.
- Document the expected outcome so regressions can be detected in the next audit.
Practical example
The hero image is preloaded only when it is the real LCP candidate, compressed to a modern format, sized responsively, and not lazy-loaded above the fold.
How to validate the result
Record the current crawl, indexation, performance, and traffic state before changing anything. Recheck the affected template and a representative URL after deployment, then monitor Search Console over the following crawl cycle. A technical change is complete only when the live response and Google’s observed state agree.