LCP (Largest Contentful Paint)
Checks Largest Contentful Paint — how fast the main content appears. Target under 2.5s.
What this check measures
We fetch real-user LCP values from CrUX (Chrome User Experience Report) for your domain over the last 28 days. Target: p75 under 2.5s. Lab data from PageSpeed Insights is used as fallback.
Why it matters
LCP is the "when does the page look done" metric. Users perceive it most viscerally. Over 4s on mobile nearly doubles bounce rate. Google ranks it as a page-experience signal.
How our audit detects it
Query CrUX API for p75 LCP over 28 days. Fall back to Lighthouse lab LCP from PageSpeed API.
Typical findings
- error_outlinep75 LCP 3.8s mobile — unoptimized hero image.
- error_outline5MB JPEG hero without preload.
- error_outlineRender-blocking web fonts delay text paint.
How to fix
Identify the LCP element in DevTools → Performance. Preload it with `<link rel="preload">`. Convert images to WebP/AVIF. Defer non-critical JS/CSS. See /prompts/improve-lcp.
Copy-paste fix prompt for your stack
Lovable · Cursor · Bolt · v0 · Replit · Windsurf · Claude Code · Base44
Frequently asked questions
Does lazy-loading help LCP?expand_more
Want this checked on your site?
Pantra runs the full audit (SEO, Security, GEO, Performance, Schema, Technical, Images) in 10 seconds and generates stack-specific fix prompts.
Scan my siteRelated checks
CLS (Cumulative Layout Shift)
Checks Cumulative Layout Shift — how much the page jumps during load. Target under 0.1.
PerformanceINP (Interaction to Next Paint)
Checks Interaction to Next Paint — responsiveness to clicks/taps. Target under 200ms.
PerformanceFCP (First Contentful Paint)
Checks First Contentful Paint — when the first text or image appears. Target under 1.8s.
PerformanceTTFB (Time to First Byte)
Checks Time To First Byte — server response time. Target under 600ms.