A measure of the main visible content
Largest Contentful Paint, or LCP, measures when the largest eligible visible content element is rendered during loading. It often relates to a prominent image or text block, depending on the page and viewport. It is one of the Core Web Vitals.
The good threshold is 2.5 seconds or less, assessed at the 75th percentile of visits and separated by device type. LCP is not a stopwatch for every background request to finish. The web.dev LCP guide explains the metric and which elements contribute.
Example: a large homepage hero image
Imagine a homepage with a high-resolution hero render. The image may look excellent, yet arrive late because it is oversized, discovered only after a script runs or incorrectly marked for lazy loading. Compressing the file helps only if transfer size is the main cause of the delay.
First identify the actual LCP element on the affected screen size. Then inspect when its request starts, how long the server takes to respond and what prevents it from appearing. A mobile layout may use a different element from the desktop layout, so the same change may not improve both.
Prioritise the cause of the delay
Use an appropriately sized image and make essential visual content discoverable early. Review server response time and render-blocking resources before adding more performance plugins. Avoid preloading many competing assets simply to make each one appear important.
Compare controlled tests with available real-user data and keep a record of the change. A fast result from a nearby desktop connection does not represent every customer’s phone or network. A strong design can retain detailed imagery while choosing sensible formats, dimensions and loading priorities. The useful goal is a prompt first view of the content that tells visitors they have reached the right place.
Common questions about largest contentful paint
Is LCP the same as total page load time?
No. It concerns the largest eligible visible content element. Other requests and background activity can continue after that element has appeared.
Will replacing every image with a smaller file fix LCP?
Not necessarily. The bottleneck may be server response, late discovery or rendering work. Identify the relevant element and delay before choosing the fix.
Related definitions
- Core Web Vitals — A set of user experience measures covering loading, responsiveness and visual stability. The current metrics are Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift.
- Lazy loading — Deferring an asset until it is approaching the area the visitor is viewing. Main above-the-fold imagery should be prioritised rather than delayed unnecessarily.
- Hosting — The infrastructure and services that make a website accessible online. Capacity, reliability, security, backups and support should match the site’s role in the business.
- Cumulative Layout Shift — A measure of unexpected layout movement while a page is being used. Reserving dimensions for images and other content helps reduce disruptive shifts.
Related SEO guides
Investigate the main visible content and its delivery when loading performance is poor.
For help connecting these decisions with your website, explore our SEO services or start with an SEO audit.
Put it into practice
Explore our technical seo service or talk with Refined IT about applying this to your website or business systems.