Guidelines · WSG 3.6
Ensure code follows good semantic practices
A large DOM costs memory and CPU on every visit, and deeply nested markup usually signals styling and script that could be simpler.
How to satisfy it
- Use native elements (button, details, dialog) rather than rebuilding them in script.
- Flatten wrapper-heavy markup; every extra node is style and layout work.
- Aim well under 1,500 elements for a content page.
Measured pages failing this guideline
From the 60 most recently measured pages. Each links to its full report.
- seedmivo.stThe page renders 2711 DOM elements, above the 1,500 guideline. Large trees cost memory and CPU on every visitor's device.0.090 g CO₂e · 986 kB
- reflectstudio.comThe page renders 4153 DOM elements, above the 1,500 guideline. Large trees cost memory and CPU on every visitor's device.0.552 g CO₂e · 5.96 MB
- reflectstudio.comThe page renders 4169 DOM elements, above the 1,500 guideline. Large trees cost memory and CPU on every visitor's device.0.557 g CO₂e · 6.02 MB
- eu.mavi.comThe page renders 4871 DOM elements, above the 1,500 guideline. Large trees cost memory and CPU on every visitor's device.0.488 g CO₂e · 5.18 MB
- open.spotify.comThe page renders 3316 DOM elements, above the 1,500 guideline. Large trees cost memory and CPU on every visitor's device.0.551 g CO₂e · 6.05 MB
- news.ycombinator.comThe page renders 39721 DOM elements, above the 1,500 guideline. Large trees cost memory and CPU on every visitor's device.0.049 g CO₂e · 329 kB
- www.amazon.inThe page renders 1935 DOM elements, above the 1,500 guideline. Large trees cost memory and CPU on every visitor's device.0.379 g CO₂e · 3.17 MB
- www.build3.orgThe page renders 1656 DOM elements, above the 1,500 guideline. Large trees cost memory and CPU on every visitor's device.0.560 g CO₂e · 4.97 MB
- www.google.comThe page renders 1562 DOM elements, above the 1,500 guideline. Large trees cost memory and CPU on every visitor's device.0.273 g CO₂e · 2.81 MB
- qwen.aiThe page renders 2552 DOM elements, above the 1,500 guideline. Large trees cost memory and CPU on every visitor's device.0.553 g CO₂e · 4.91 MB
- openrouter.aiThe page renders 1613 DOM elements, above the 1,500 guideline. Large trees cost memory and CPU on every visitor's device.0.452 g CO₂e · 4.88 MB
- upcyman.comThe page renders 1764 DOM elements, above the 1,500 guideline. Large trees cost memory and CPU on every visitor's device.0.233 g CO₂e · 2.54 MB