SPPB Pro Impact of Hidden Elements - Forum | JoomShaper
Solved SP Page Builder

SPPB Pro Impact of Hidden Elements

Asked by johnny 9 months ago Last activity 9 months ago

I have a large number of elements on my SP Page Builder pages that are set to Hidden. These elements are visible while I’m in the frontend editor, but they do not appear on the live site.

Does keeping many elements set to Hidden have any negative impact on the site, for example:

  • page load time / performance
  • SEO
  • accessibility
  • overall frontend output

In other words, are hidden elements completely excluded from frontend rendering, or are they still loaded in some form?

Accepted answer

Marked as the solution
Atick Eashrak Shuvo Staff
9 months ago

Hello johnny,

Thank you for your question. In SP Page Builder, elements set to “Hidden” are hidden via CSS (using display: none). This means the content is still delivered in the page’s HTML but is not visible to users.

Regarding your concerns:

  • Performance / Page Load Time: Hidden elements add some overhead because they are still parsed by the browser. For a few elements, this impact is negligible. However, if you have many hidden blocks—especially those containing images or dynamic addons—it may slightly affect page load times.
  • SEO: Hidden content is generally indexed by search engines but does not contribute significantly to SEO unless it is used manipulatively. Regular use for layout or drafts has minimal SEO impact.
  • Accessibility: Elements hidden with CSS (display: none) are ignored by screen readers, so they typically do not affect accessibility.
  • Frontend Output: There is no visual effect on the live site, but the DOM size increases with more hidden elements, which may affect complex pages.

As a best practice, we recommend using hidden elements for temporary drafts or design variations. For long-term management of multiple layouts or versions, consider duplicating pages, using revisions, or exporting/importing sections to keep pages streamlined.

Best regards

Log in to reply.