Excessive DOM size
Silktide measures how many elements make up your page, and how deeply they are nested. Pages built from too many elements are slower to load, slower to respond, and use more memory on your visitors' devices.
Every heading, paragraph, image, and container on a page is an element in the browser's internal model of the page, the . Browsers handle a few hundred elements easily; pages with thousands make every style calculation, layout pass, and script update measurably slower.
Why this matters
Visitors experience an oversized page as sluggishness: the page takes longer to appear, scrolling stutters, and interactions like opening a menu lag noticeably. The effect is worst on the devices with the least power to spare - budget phones and older computers - so the visitors with the slowest hardware get the worst version of your site.
Oversized pages usually are not designed that way deliberately. They accumulate: page builders that wrap everything in layers of containers, hidden variants of the same content for different screen sizes, and long lists rendered in full even though visitors only ever see the first screen.
How to fix it
- Find what is inflating the page. Common culprits are page-builder themes that generate deeply nested wrappers, mega-menus that embed the entire site structure into every page, and long tables or product lists rendered in full.
- Render long lists incrementally: show the first items and load more as the visitor scrolls or pages through, rather than putting thousands of rows in the page at once.
- Avoid duplicating content for different devices. Style one copy with instead of shipping separate hidden desktop and mobile versions of the same content.
- Split very long pages into several smaller ones when the content allows it.
How Silktide tests this
- Load the page in a real browser, using the device type, connection speed, and test location configured for your speed tests.
- Count the elements that make up the fully loaded page, including anything added by .
- Measure three statistics, and identify the element responsible for each: the total number of elements, the deepest nesting of elements, and the largest number of children under one parent.
- Grade each statistic. Roughly 1,000 total elements, nesting about 24 levels deep, or one parent with about 45 children begins to lower the grade; around 1,500 elements, 32 levels, or 60 children is graded as poor.
Troubleshooting
The page doesn't look big
Element count is about structure, not visible content. A visually simple page can contain thousands of elements if each visible item is wrapped in many layers of containers, or if content for other screen sizes is present but hidden. The elements reported for each statistic show where the bulk actually is.
The large element count comes from my theme or page builder
That is common, and it usually is not something content editors can fix. Pass the finding to whoever maintains the site's theme or templates; switching off unused page-builder features or simplifying templates often removes hundreds of elements at once.