Huge DOM

  • Resolved sonstiges

    (@sonstiges)


    7 years, 3 months ago

    Hi,

    In December 2017 we moved to wordpress and found your awesome plugin. We created one side and copied it over 800 times for all our old posts.
    Now Google changed the PageSpeed Insights Requests to Lighthouse and we get a penalty for the huge DOM on mobile. Main fault of this problem is the DOM created by your plugin. Is it possible to minimize the plugin? Do I really need 6 encapsulated DIVS? Will you optimize the plugin for PageSpeed Insights in nearer future?

    Thank your for your help!
    Darius

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Contributor alexgso

    (@alexgso)

    7 years, 3 months ago

    Hi Darius,

    Preface: Please note that not every point mentioned in Lighthouse leads to a direct penalization. Google looks at the overall value rather than specific values, but they still do weight certain amounts over others.

    I’ve run a few tests against your page, and while Lighthouse is flagging a large DOM size, it’s still below the recommendation for the other flags. For reference, that is:

    Browser engineers recommend pages contain fewer than ~1,500 DOM nodes. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.

    Your DOM, as per Lighthouse, is:

    Total DOM Nodes: 1234
    Maximum DOM Depth: 24
    Maximum Children: 113

    Due to the length of your page, upon excluding SiteOrigin Page Builder, you’re still exceeding) the maximum children without SiteOrigin Page Builder. While we’re not helping matters, you’ll need to review your website overall to work towards reducing the maximum children count.

    Do I really need 6 encapsulated DIVS?
    Yes. We conditionally output additional structuring/container divs based on setting choices so if the divs are outputting, it’s due to them being required to achieve the desired layout.

Viewing 1 replies (of 1 total)

The topic ‘Huge DOM’ is closed to new replies.