Poor Largest Contentful Paint (LCP)

What This Means

The page's Largest Contentful Paint — the time until the largest visible content element (typically a hero image or headline) is fully rendered — is in the "Poor" range (above 4.0 seconds). Google considers LCP below 2.5 seconds "Good" and above 4.0 seconds "Poor".

Why It Matters for SEO

LCP is directly correlated with user perception of load speed. Users experience a "slow" page primarily as waiting for the main content to appear. Google uses LCP as one of its Core Web Vitals page experience ranking signals — pages with poor LCP may rank below pages with equivalent content and authority that load faster.

LCP is commonly the most impactful Core Web Vital to fix because its causes (large hero images, slow server response, render-blocking resources) are specific and addressable.

What the Platform Checks

The platform uses performance data (PageSpeed Insights API or lab-based measurement) to measure LCP for each crawled page. Fires when the LCP score is in the "Poor" band (>4.0 seconds).

How to Fix It

• Optimize the LCP element: Identify what element is the LCP (usually the hero image or the largest heading). If it is an image, optimize its file size, format, and serve it with high priority.
• Preload the LCP image: <link rel="preload" as="image" href="hero.webp"> tells the browser to fetch the LCP image immediately.
• Reduce server response time (TTFB): A slow first byte directly delays LCP. Optimize server performance, use CDN edge caching, and minimize database query time.
• Remove render-blocking resources: Render-blocking scripts and stylesheets that load before the LCP element delay its rendering. Defer non-critical JS and inline critical CSS.
• Use lazy loading carefully: Do not lazy-load the LCP element — only apply loading="lazy" to images below the fold.