How do I reduce the number of DOM elements in WordPress?

How do I reduce the number of DOM elements in WordPress?

How do I reduce the number of DOM elements in WordPress?

  • How do I reduce the size of my dom?
  • Does Elementor slow down your site?
  • How do you optimize an Elementor?
  • how reduce elementor dom elements?
  • How many DOM elements are too many?

Instruction (1):

  1. Lazy load YouTube videos – use WP YouTube Lyte or Lazy Load by WP Rocket.
  2. Limit number of blog posts/products per page – I usually try to keep a maximum of 10 blog posts per page and paginate rest of them.
  3. Lazy load blog posts/products – Add “load more” button or infinite scroll to load more blog posts or products.

Instruction (2): what’s the node dom?

A “node“, in this context, is simply an HTML element. The “DOM” is a tree structure that represents the HTML of the website, and every HTML element is a “node“. See Document Object Model (DOM). … The term “node” therefore (in the DOM context) means any object that implements the “Node” interface

At worst installing and activating the Elementor plugin can impact the speed of your website making it slower which can affect your SEO, but that shouldn’t be enough to make any difference to your current rankings.



The optimized DOM output experiment aims to improve performance by decreasing the number of wrapper elements present in the HTML that is generated by Elementor.

  1. Use Best-Practice Layout Techniques. …
  2. Minimize the Number of CSS Rules. …
  3. Minimize DOM depths. …
  4. Update Classes Low in the DOM Tree. …
  5. Remove Complex Animations From the Flow. …
  6. Modify Hidden Elements. …
  7. Update Elements in Batch. …
  8. Limit the Affected Elements.

How To Use This Experiment

  1. Go to Elementor > Settings > Experiments tab.
  2. Select Active from the Optimized DOM Output dropdown.

Click the Save Changes button.

More About The Optimized DOM

Starting with Elementor 3.0, some significant DOM improvements have been made to boost the speed and performance of new Elementor websites. The developers addressed a growing concern about the number of HTML wrapper elements that were output by Elementor. In response, we’ve removed some wrappers.

The presence of these wrappers was due to the diverse use of Elementor, the ability to use these selectors in various ways to customize your site, and the omni-purpose of Elementor as a solution for creating advanced websites visually.

Removing wrapper elements from the DOM contributes to more simplified code output, better readability and less complexity. A smaller DOM contributes to increases in speed and performance. This is, however, a potentially breaking change, so by default, Elementor will only use the Optimized DOM Output on new sites.

Which HTML Wrappers Were Removed in 3.0?

Three (3) HTML wrappers are removed, including:

  • .elementor-inner
  • .elementor-row
  • .elementor-column-wrap

HTML Wrappers Removed in 3.2

In this version we removed the following two (2) HTML wrappers:

  • .elementor-image
  • .elementor-text-editor

Who Does This Change Affect?

By default, this only affects new sites to avoid breaking existing sites that upgrade to 3.0. Using the Optimized DOM Output on existing sites that upgrade from pre-3.0 would potentially cause your website’s appearance and/or functionality to break. For this reason, the Optimized DOM Output is disabled on upgraded sites, and Legacy DOM remains in place. However, if you upgrade to 3.0 and wish to use the Optimized DOM Output, you can enable this feature. Simply go to Elementor > Settings > Advanced and select Enable in the Optimized DOM Output dropdown.

Important: If you have used any of these wrapper classes in either your custom CSS or custom code, you should refactor your code to use different wrapper classes that aren’t being removed. Otherwise, your custom styles or code will no longer function properly.

Another post: 

Check out our categories: Android Update, Elementor, flutter, Guide, Game, Plugin, Theme, webmaster, SEO


Leave a Reply

Your email address will not be published. Required fields are marked *