Why it matters
- The largest image or block of text is what visitors wait for: until it appears, the page looks empty or unfinished, and many leave.
- Largest Contentful Paint (LCP) is one of the three Core Web Vitals, which Google's search ranking systems use.
- These are real visits, on real phones and networks: what the site's visitors actually waited, not a test in a lab.
How to fix
- Find the largest element first: Chrome's DevTools mark it in the Performance panel.
- When it is an image: make it smaller (AVIF or WebP, sized for phones), do not lazy-load it, and give it priority with
fetchpriority="high"or<link rel="preload" as="image">. - Make the server answer sooner: a cache or a content delivery network (CDN) cuts the wait before anything loads.
- Scripts and stylesheets that block the page delay everything: load scripts with
defer, and keep the CSS the first screen needs small.
How we detect
- With an API key, we ask the Chrome UX Report (CrUX) about the page's URL on phones: the last 28 days of visits in Chrome by users who share usage statistics and sync their browsing history. Chrome on iPhone, apps' web views and other browsers are not counted. When CrUX has no data for the URL, we ask about the whole site (its origin), and the finding says so.
- The rule fails when the 75th percentile of Largest Contentful Paint is over 4 seconds: Google's limit for poor.
- Without a key, or when CrUX has no data for the page or its site, as for many sites with fewer visits, the rule does not apply. A page on a local or private address is never sent to Google.
- CrUX covers the last 28 days, so a fix shows in it gradually, over about four weeks.