LCP — Largest Contentful Paint — measures how long it takes for the main visible content of a page to appear. Usually that's the hero image or the headline, whichever is largest in the initial viewport. Google considers anything under 2.5 seconds good; over 4 seconds is poor.
LCP is one of the three Core Web Vitals — see What Are Core Web Vitals? for how it fits alongside INP and CLS.
Why LCP matters more than it seems
A page that takes five seconds to show its main content loses around 25% of visitors before it finishes loading. Those visitors hit back and click the next search result, which tells Google this page wasn't satisfying — a direct link between a slow LCP and both lost visitors and a weaker search ranking.
What actually drives a bad LCP score
An unoptimised hero image. A multi-megabyte image serving at full resolution when a much smaller, compressed version would look identical on screen is the single most common cause. Modern formats (WebP, AVIF) and proper sizing fix this without a visible quality loss.
Render-blocking resources. A large CSS or JavaScript file that the browser must fully download and process before it can paint anything delays LCP regardless of how fast the image itself loads. Deferring non-critical scripts and inlining critical CSS both help.
Slow server response time. If the server itself takes a long time to respond to the initial request, everything downstream — including LCP — is delayed before the browser even starts rendering. This is a hosting and backend performance question, separate from front-end optimisation.
What to actually do about it
Compress and correctly size images, especially anything above the fold. Defer JavaScript that isn't needed for the initial render. Use a hosting provider or CDN fast enough that server response time isn't the bottleneck. None of this requires a rebuild — most sites can meaningfully improve LCP with image optimisation alone, which is usually the highest-leverage single fix.
A fast LCP is the first impression your site makes, measured in the most literal sense: it's how long someone waits before they see anything worth reading.
Frequently asked questions
What's a good LCP score?
Under 2.5 seconds is good. Between 2.5 and 4 seconds needs improvement. Over 4 seconds is poor, per Google's thresholds.
What's the single biggest driver of a bad LCP score?
Usually an unoptimised hero image or a render-blocking resource (a large CSS or JavaScript file) that delays the browser from painting the main content — see [What Are Core Web Vitals?](/blog/what-are-core-web-vitals) for how LCP fits alongside INP and CLS.
Does LCP matter for SEO, or just user experience?
Both — Google uses Core Web Vitals, including LCP, as a ranking signal, and the user-experience cost is real regardless: pages that load slowly lose visitors before they ever see the content.
Yash
Founder & Principal Consultant, Ynexgen
Yash leads Ynexgen, helping small and mid-sized businesses turn technology into a stronger foundation for growth — 7+ years across Salesforce CRM, websites, and AI adoption.
