Page Speed Hints

      High This Hint is very important, and definitely warrants attention. Issue This Hint represents an error or problem that needs to be fixed.

      Has an excessive number of DOM nodes (greater than 1500)

      This means that the URL in question has more than the recommended 1500 elements in the DOM

      Why is this important?

      While browsers can handle larger DOM trees, they are optimized for a maximum of ~1500 nodes in total. A large DOM tree can harm your page performance in multiple ways:

      • Network efficiency and load performance. If you server ships a large DOM tree, you may be shipping lots of unnecessary bytes. This can also slow down page load time, because the browser may be parsing lots of nodes that aren't even displayed above-the-fold.
      • Runtime performance. As users and scripts interact with your page, the browser must constantly re-compute the position and styling of nodes. A large DOM tree in combination with complicated style rules can severely slow down rendering.
      • Memory performance. If you use general query selectors such as document.querySelectorAll('li') you may be unknowingly storing references to a very large number of nodes, which can overwhelm the memory capabilities of your users' devices.

      What does the Hint check?

      This Hint will trigger for any internal URL with a total of more than 1500 DOM nodes.

      Examples that trigger this Hint:

      The Hint would trigger for any URL with over 1500 elements in the DOM, such as the example below:

      Maximum DOM depth

      How do you resolve this issue?

      An optimal DOM tree:

      • Has less than 1500 nodes total.
      • Has a maximum depth of 32 nodes.
      • Has no parent node with more than 60 child nodes.

      In general, look for ways to create DOM nodes only when needed, and destroy them when no longer needed.

      If your server ships a large DOM tree, try loading your page and manually noting which nodes are displayed. Perhaps you can remove the undisplayed nodes from the loaded document, and only create them after a user gesture, such as a scroll or a button click.

      Here are a few questions you should ask yourself:

      • Are you using nested tables for layout purposes?
      • Are you throwing in more <div>s only to fix layout issues?
      • Is there a better and more semantically correct way to do your markup?

      Further Reading

      Ready to try Sitebulb?
      Start your free 14 day trial now

      Start Free Trial