DOM tree depth on Wix sites
0.6% of audited sites (34) keep maximum DOM depth between 15 and 20 levels (100% good INP, 95ms median), while 37.0% nest 21 to 31 levels deep (96% good INP) and 62.3% reach 32+ levels (96% good INP).
62.3% of Wix sites use 32+ DOM levels maximum DOM depth, and 96% of those sites have a good INP, against 96% of all Wix sites.
INP pass rate
Sites with 32+ DOM levels maximum DOM depth have a good INP most often: 96%, against 96% of all Wix sites. Sites with 21 to 31 DOM levels DOM depth have it least often, at 96%.
Maximum DOM depth usage
32+ DOM levels is the most used: 62.3% of Wix sites.
Maximum DOM depth per framework
React sets the maximum DOM depth to 32+ DOM levels on 62% of its sites, and 96% of React sites have a good INP, against 96% of all sites.
DOM nesting depth or the framework
Does the framework explain the maximum DOM depth difference?
On React, 96% of sites with 32+ DOM levels maximum DOM depth have a good INP, against 96% of React sites with 21 to 31 DOM levels. Within React, sites with 32+ DOM levels and 21 to 31 DOM levels have a good INP about equally often.
Why deeply nested wrapper chains slow down event bubbling and layout
Maximum DOM depth measures the longest chain of nested parent-child elements from the root html tag to the deepest leaf node. Across 34 sites (0.6%) at 15 to 20 levels, 100% achieve good INP (95ms median). Another 37.0% (2,079) nest 21 to 31 levels deep (96% good INP, 75ms median), while the 62.3% (3,504) exceeding 32 levels drop to 96% good INP (80ms median).
Understanding maximum DOM depth
Keep maximum DOM nesting depth below 20 levels by replacing nested flex/column wrapper divs with CSS Grid and using fragments in component frameworks so component boundaries do not emit extra DOM containers. Across all audited sites, 0.6% sit at 15 to 20 levels (100% good INP) and 62.3% exceed 32 levels (96% good INP).
By Arjen Karel · 5,621 crawled Wix sites (3,077 with phone Chrome field data, October 2026). How we measured.