DOM element count and the Core Web Vitals

31.5% of audited sites (63,552) keep their DOM between 400 and 799 elements (99% good INP, 45ms median), while the 17.6% exceeding 1,500 DOM nodes drop to 99% good INP (58ms median).

Field data PhoneDesktopAll Scope All sites October 2026 edition · Desktop field outcomes

25.2% of sites use 800 to 1,499 DOM elements DOM element count, and 99% of those sites have a good INP, against 99% of all sites.

The State of Web Vitals · October 2026 · 210,902 crawled sites · 69,745 with desktop field data · 201,622 sites with DOM element countBy Arjen Karel · corewebvitals.io/state-of-cwv
1

Core Web Vitals pass rate

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

SitesGood, needs improvement, poor INPMedian
All sites69,74599%49ms
800 to 1,499 elements 25.2%18,12399%48ms
400 to 799 elements 31.5%16,36299%45ms
1,500+ elements 17.6%18,87299%58ms
Under 400 elements 25.7%15,44498%47ms
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · 210,902 crawled sites · 69,745 with desktop field data · 201,622 sites with DOM element countBy Arjen Karel · corewebvitals.io/state-of-cwv
2

DOM element count usage

400 to 799 DOM elements is the most used: 31.5% of sites. 800 to 1,499 DOM elements is 25.2% of sites.

400 to 799 elements 31.5% Under 400 elements 25.7% 800 to 1,499 elements 25.2% 1,500+ elements 17.6%
400 to 799 elements 31.5% Under 400 elements 25.7% 800 to 1,499 elements 25.2% 1,500+ elements 17.6%
The State of Web Vitals · October 2026 · 210,902 crawled sites · 69,745 with desktop field data · 201,622 sites with DOM element countBy Arjen Karel · corewebvitals.io/state-of-cwv
3

Understanding DOM element count

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 63,552 sites (31.5%) with 400 to 799 elements, 99% pass field INP at a 45ms median, and the 25.2% between 800 and 1,499 elements reach 99% good INP (48ms median). Once the document tree crosses 1,500 elements (17.6% of sites, 35,503), good INP drops to 99% and median INP rises to 58ms.

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, 31.5% sit at 400 to 799 nodes (99% good INP, 45ms median) versus 17.6% at 1,500+ nodes (99% good INP, 58ms median).

The State of Web Vitals · October 2026 · 210,902 crawled sites · 69,745 with desktop field data · 201,622 sites with DOM element countBy Arjen Karel · corewebvitals.io/state-of-cwv
Platform & Framework Takeaways

How DOM element count plays out per platform

What the field data shows when you isolate a single CMS or framework.

WordPress 65,509 sites
100% vs 99% good INP (400-799 vs 1,500+ nodes)

WordPress pages with 1,500+ DOM elements (15.9%) pass field INP at 99% vs 100% at 400 to 799 nodes.

Across 65,509 WordPress sites, 37.3% have between 400 and 799 DOM nodes (100% good INP, 45ms median) and 15.9% exceed 1,500 nodes (99% good INP, 56ms median).

Read the WordPress DOM element count breakdown →
Wix 5,825 sites
85% Wix sites under 1,500 DOM elements

85% of Wix sites have fewer than 1,500 DOM nodes (99% good INP at 400 to 799 nodes).

Across 5,825 Wix sites, 41.8% sit at 400 to 799 DOM elements (99% good INP), 35.9% sit at 800 to 1,499 elements (100% good INP), and 15.0% exceed 1,500 elements (100% good INP).

Read the Wix DOM element count breakdown →
Related signals Iframes per page → Media source → Image fetchpriority → Uses @import → By Arjen Karel · 210,902 crawled sites (69,745 with desktop Chrome field data, 201,622 sites with DOM element count, October 2026) · How we measured