DOM element count on Wix sites

Sites with 800 to 1,499 DOM elements DOM element count have a good INP most often: 100%, against 100% of all Wix sites. Sites with 400 to 799 DOM elements DOM size have it least often, at 99%.

Sites with 400 to 799 DOM elements DOM element count have a good LCP most often: 96%, against 92% of all Wix sites. Sites with 1,500+ DOM elements DOM size have it least often, at 84%.

400 to 799 DOM elements is the most used: 41.8% of Wix sites. 800 to 1,499 DOM elements is 36.1% of Wix sites.

On React, 42% of sites use 400 to 799 DOM elements DOM element count, and 100% of React sites have a good INP, against 100% of all sites.

On React, 42% of sites use 400 to 799 DOM elements DOM element count, and 92% of React sites have a good LCP, against 92% of all sites.

FrameworkDOM element count on its sitesGood INP

All Wix sites 5,621 sites400 to 799 elements 42%800 to 1,499 elements 36%1,500+ elements 15%100%

React 5,620 sites400 to 799 elements 42%800 to 1,499 elements 36%1,500+ elements 15%100%

400 to 799 elements 800 to 1,499 elements 1,500+ elements Under 400 elements

Does the framework explain the DOM element count difference?

On React, 100% of sites with 800 to 1,499 DOM elements DOM element count have a good INP, against 99% of React sites with 400 to 799 DOM elements. Within React, sites with 800 to 1,499 DOM elements and 400 to 799 DOM elements have a good INP about equally often.

On React, 96% of sites with 400 to 799 DOM elements DOM element count have a good LCP, against 93% of React sites with 800 to 1,499 DOM elements. Within React, sites with 400 to 799 DOM elements and 800 to 1,499 DOM elements have a good LCP about equally 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 2,350 sites (41.8%) with 400 to 799 elements, 99% pass field INP at a 34ms median, and the 36.1% between 800 and 1,499 elements reach 100% good INP (38ms median). Once the document tree crosses 1,500 elements (15.0% of sites, 842), good INP drops to 100% and median INP rises to 44ms.