Core Web Vitals
What is LCP?
Largest Contentful Paint measures how long it takes for the main visible content to appear. For most pages, that is a hero image, heading, product photo, or large text block.
Plain-English version
When the biggest visible element on the page finishes loading.
Target
Under 2.5s
LCP thresholds
Use thresholds as a triage tool. Field data matters most when there is enough real Chrome traffic for the page.
Good
≤ 2.5s
Needs work
2.5–4s
Poor
> 4s
Why it matters
What a visitor feels when LCP is bad.
Why LCP matters
LCP is the clearest loading metric for visitors. A page can feel slow even when the Lighthouse score looks fine if the main content appears late on real mobile connections.
What a poor result usually means
A poor LCP usually means the browser discovers the main image too late, waits on render-blocking CSS, receives a slow server response, or downloads too much before it can paint the important content.
nimo audit lens
How nimo reads LCP in an audit.
The glossary explains the metric. The free audit checks the page, separates field data from lab diagnostics, and points at the first review step.
How nimo interprets it
nimo treats LCP as the loading bottleneck for the main visible element, not as a generic page-speed score.
Source to trust first
Use CrUX field data first when the URL or origin has enough Chrome traffic. Use Lighthouse to identify the LCP element and its blockers.
Evidence to inspect
- Mobile and desktop LCP status separately.
- The LCP element reported in the Lighthouse trace.
- TTFB, render-blocking requests, and image discovery timing.
- Whether the problem is URL-level, origin-level, or lab-only.
First fix to review
Review the LCP element path: image size and format, preload or fetch priority, and CSS that blocks rendering.
How to validate
Rerun the same audit after the change, compare the LCP element and lab LCP immediately, then watch field data when CrUX updates.
What to fix first
Do not chase the score. Fix the bottleneck.
The right fix depends on the metric, the page template, and whether the issue appears in real visitor data.
- Identify the LCP element on mobile and desktop.
- Preload or prioritize the hero image when it is the LCP element.
- Inline critical CSS and defer non-critical styles.
- Reduce server response time and unnecessary redirects.
- Compress, resize, and serve the LCP image in a modern format.
How nimo helps
Run the free audit, then ask: “Why is my LCP slow and how do I fix it?”
nimo compares real Chrome field data with Lighthouse diagnostics so you can see whether LCP is a visitor problem, a lab-only warning, or both.
No signup needed. Takes about 30 seconds.