Your files stay on your device

# LCP element analyzer

Paste a DevTools trace or page HTML and see the LCP element with its time split into TTFB, load delay, load duration, and render delay, plus one fix per phase.

Paste page HTML, a recorded LCP entry, or a DevTools trace to analyze it.
Page HTML, LCP JSON, or trace

Everything runs in this tab; the paste is never uploaded and no URL is fetched. The measured routes reproduce what the browser recorded, split the way web.dev defines the LCP phases, and a phase stays unknown when the paste does not carry it, rather than being guessed. The static HTML route is an estimate: it scores markup by declared size and position and cannot see images that scripts add, styles that change at runtime, or which candidate the browser finally picks. Neither route equals the field LCP Google assesses, which comes from real visitors on real devices.
Options

## More web & auth tools

- [INP interaction profiler](/browser/inp-interaction-profiler)
- [Capability dashboard](/browser/capabilities)
- [Deep probes](/browser/probes)
[All web & auth tools](/web)

Was this tool useful?
YesNo

---

Canonical HTML: https://nutter.tools/web/lcp-element-analyzer
Markdown version: https://nutter.tools/web/lcp-element-analyzer.md
Plain-text version: https://nutter.tools/web/lcp-element-analyzer.txt
Agent index: https://nutter.tools/llms.txt