Largest Contentful Paint
good ≤ 2.5 s · poor > 4 s00:0004:0008:0012:0016:0020:00
62% good19% needs improvement19% poor
Product tour · Epsilon Delta Gemini · Website monitoring
Core Web Vitals insights: why your scores look the way they do
Insight details explains why Core Web Vitals are in their current state, and links each metric to the elements, resources and conditions behind it.
Insight details why Core Web Vitals look the way they do
“Why are Core Web Vitals in this state?”
- Sample data
- Last 24 hrs
- All events
- Median
- All platforms
- LCP
- 1,634 ms
- ▼ 13% vs last week
- INP
- 144 ms
- ▼ 5% vs last week
- CLS
- 0.08
- ▼ 27% vs last week
- TBT
- 574 ms
- ▼ 26% vs last week
- INP poor for 17% of interactions
- LCP long tail: p90 is 4× the median
- High 4xx rate: 1.9M errors this window
- Images drive LCP (80%): optimise the hero image
Page weight composition
446 KB median total · before FCP / above fold / before LCP- Before FCP 201 KB
- Above fold 77 KB
- Before LCP 168 KB
Above-fold requests: 35 (target ≤ 4) · Requests before LCP: 52 (target ≤ 6)
LCP element type
80%image
- Image80%
- Text20%
Top referrers
108 sourcesSample data on example domains (shop.example.com). Your dashboard shows your own sites and apps.
What you can see on Insight details
- The LCP element and its sub-parts
- Page weight before FCP and LCP
- Blocking resources
- Entry points, referrers and browsers
Questions about Insight details
What are the LCP sub-parts?
TTFB, resource load delay, resource load time and render delay. Together they add up to LCP.
Does it suggest fixes?
It points to the element, resource or phase that costs the most, which is where a fix pays off first.
Last updated 6 Nov 2026 · Reviewed by [Name], [Role]