DOM element count on React sites
36.1% of audited sites (3,454) keep their DOM between 400 and 799 elements (96% good INP, 74ms median), while the 19.4% exceeding 1,500 DOM nodes drop to 93% good INP (95ms median).
36.0% of React sites use 800 to 1,499 DOM elements DOM element count, and 97% of those sites have a good INP, against 95% of all React sites.
36.1% of React sites use 400 to 799 DOM elements DOM element count, and 91% of those sites have a good LCP, against 85% of all React sites.
Core Web Vitals pass rate
Sites with 800 to 1,499 DOM elements DOM element count have a good INP most often: 97%, against 95% of all React sites. Sites with 1,500+ DOM elements DOM size have it least often, at 93%.
Sites with 400 to 799 DOM elements DOM element count have a good LCP most often: 91%, against 85% of all React sites. Sites with 1,500+ DOM elements DOM size have it least often, at 73%.
DOM element count usage
400 to 799 DOM elements is the most used: 36.1% of React sites. 800 to 1,499 DOM elements is 36.0% of React sites.
DOM element count per platform
On Wix, 42% of sites use 400 to 799 DOM elements DOM element count, and 97% of Wix sites have a good INP, against 95% of all sites. On WordPress, 41% of sites use 800 to 1,499 DOM elements, and 98% of WordPress sites have a good INP.
On Wix, 42% of sites use 400 to 799 DOM elements DOM element count, and 94% of Wix sites have a good LCP, against 85% of all sites. On WordPress, 41% of sites use 800 to 1,499 DOM elements, and 61% of WordPress sites have a good LCP.
DOM element count or the platform
Does the platform explain the DOM element count difference?
On Wix, 98% of sites with 800 to 1,499 DOM elements DOM element count have a good INP, against 97% of Wix sites with 400 to 799 DOM elements. Within Wix, sites with 800 to 1,499 DOM elements and 400 to 799 DOM elements have a good INP about equally often. On WordPress, 99% of sites with 800 to 1,499 DOM elements DOM element count have a good INP, against 98% of WordPress sites with 400 to 799 DOM elements. Within WordPress, sites with 800 to 1,499 DOM elements and 400 to 799 DOM elements have a good INP about equally often.
On Wix, 97% of sites with 400 to 799 DOM elements DOM element count have a good LCP, against 95% of Wix sites with 800 to 1,499 DOM elements. Within Wix, sites with 400 to 799 DOM elements have a good LCP more often. On WordPress, 73% of sites with 400 to 799 DOM elements DOM element count have a good LCP, against 58% of WordPress sites with 800 to 1,499 DOM elements. Within WordPress, sites with 400 to 799 DOM elements have a good LCP more often.
How DOM tree size taxes style recalculation and layout during interactions
Every time a user taps a menu, filters a grid, or toggles a class, the browser recalculates styles and layout across affected DOM nodes. Across 3,454 sites (36.1%) with 400 to 799 elements, 96% pass field INP at a 74ms median, and the 36.0% between 800 and 1,499 elements reach 97% good INP (80ms median). Once the document tree crosses 1,500 elements (19.4% of sites, 1,860), good INP drops to 93% and median INP rises to 95ms.
Understanding DOM element count
Keep total DOM element count under 800 nodes on initial load and below 1,500 nodes on complex templates. Render modals, drawer menus, and offscreen tabs lazily on interaction, and paginate or virtualize long product and comment lists. Across all audited sites, 36.1% sit at 400 to 799 nodes (96% good INP, 74ms median) versus 19.4% at 1,500+ nodes (93% good INP, 95ms median).
By Arjen Karel · 9,570 crawled React sites (9,110 with all devices Chrome field data, October 2026). How we measured.