The State of Web Vitals

DOM depth

The deepest nesting level in the DOM tree.

Field data PhoneDesktopAll Scope All sites Q2 2026 edition · All devices field outcomes
Metric LCP INP CLS
1

At a glance the headline numbers for DOM depth

The deepest nesting level in the DOM tree.

18
on the typical site
half of sites sit at or below
23
1 in 4 sites exceed this
the top quarter
41
the heaviest 1%
the long tail
180,684
sites measured
all-device field data

The typical DOM tree is 18 levels deep.

The State of Web Vitals · Q2 2026 · 189,915 sites · all devices field datacorewebvitals.io/state-of-cwv
2

Distribution & median LCP site count and median LCP at each level of DOM depth

0ms 750ms 1500ms 2250ms 3000ms
2.5s
0 31312 62624
0 1 2 3 4 5–6 7–9 10–13 14–18 19–26 27–37 >p98
Good (≤2.5s) Needs improvement Poor (>4s) Site count
The State of Web Vitals · Q2 2026 · 189,915 sites · all devices field datacorewebvitals.io/state-of-cwv
3

Passing LCP by DOM depth which level passes the LCP most often

DOM depthSitesPassing LCPLCP
1 416 83% 1.5s
2 1,687 80% 1.5s
3 629 79% 1.4s
4 526 82% 1.2s
5–6 1,741 86% 1.2s
7–9 6,184 91% 1.1s
10–13 28,312 90% 1.3s
14–18 57,381 85% 1.5s
19–26 62,624 78% 1.7s
27–37 17,994 77% 1.7s
>p98 3,189 77% 1.6s
Good Needs Improvement Poor Faded rows: under 100 sites

DOM depth 18. p75 23. p99 41. At the low end (1): LCP 1.5s. At the high end (>p98): LCP 1.6s. computed

The State of Web Vitals · Q2 2026 · 189,915 sites · all devices field datacorewebvitals.io/state-of-cwv
4

Why this matters for the Core Web Vitals, and where to start fixing it

Depth is a different problem than size. Styles inherit downwards. Toggle a class high in the tree and the browser recalculates everything below it. Layout changes also travel through ancestors, and percentage heights and flexbox make that worse. Selector matching walks the ancestor chain too, so deep trees pay more for every CSS rule.

In practice this shows up as INP. The click is fast and the JavaScript is fast, but the style and layout pass after the update is slow because the change affects too many nested levels. A flatter tree holds the same content but keeps each update local.

How does DOM depth affect the Core Web Vitals?

Passing INP barely moves across the range: 92% at one end, 90% at the other. This signal does not separate passing sites from failing ones.

The effect is bigger on LCP. In the flattest trees, 83% of sites pass it. In the deepest trees, 77% do.

Go fix it Fix excessive DOM size →
Related signals Script coverage (used vs unused) → Image loading attribute → Images per page → Compression mix → Chrome field data from 189,915 sites, representing millions of real page loads · How we measured