Half your visitors will bail if your page takes longer than 3 seconds to load[3]. Largest Contentful Paint (LCP) is the metric that tells you whether they see content or a blank screen. It measures how long it takes for the largest visible element (usually your hero image or main heading) to finish rendering.
Why It Matters
LCP is the closest proxy to what a user perceives as "the page is ready." A slow LCP means users are staring at a blank screen. A significant percentage will leave before it finishes. Every 100ms of delay costs you conversions.
For agents, the stakes are different but equally high. Many agent crawlers render pages in headless browsers with strict timeouts. If your largest content takes too long to paint, the crawler captures an incomplete version of your page: missing product images, truncated descriptions, broken structured data. Agents can only recommend what they can see.
Google also uses LCP as a ranking signal[1], which means it directly affects your search position and your Quality Score for ads.
How It's Measured
Google rates LCP on a three-tier scale[2]:
- 2.5 seconds or less: good
- 2.5 to 4 seconds: needs improvement
- Above 4 seconds: poor
The browser identifies the largest element in the viewport at each frame during page load. The LCP value is the render time of the final largest element before the user first interacts with the page.
Common Causes of Slow LCP
- Unoptimized images: large, uncompressed hero images that take seconds to download
- Render-blocking resources: CSS and JavaScript files that prevent the browser from painting content
- Slow server response: a high Time to First Byte (TTFB) delays everything downstream
- Client-side rendering: pages that require JavaScript to execute before any content appears
- Third-party scripts: analytics, chat widgets, and ad scripts competing for network and CPU
How to Fix It
- Optimize your LCP image: use modern formats (WebP, AVIF), appropriate sizing, and add fetchpriority="high" to the hero image
- Eliminate render-blocking resources: inline critical CSS, defer non-critical JavaScript, and use async/defer on script tags
- Use a CDN to serve static assets from edge locations close to your users
- Preload key resources: use
<link rel="preload">for fonts, hero images, and critical scripts - Server-side render or statically generate key pages so content is in the initial HTML response
- Reduce TTFB: optimize server-side logic, use caching, and consider edge rendering
How Scanner Helps
Scanner measures LCP as part of its Lighthouse-based Performance audit. It identifies your LCP element, reports the render time, and flags it if it exceeds the 2.5-second threshold. The result feeds directly into your overall Site Score.