Make "Conditional Visibility" Server-side

Currently, conditional visibility is a simple class assignment with Display:None. This makes it so that when you have a lot of content-rich sections hidden conditionally, the page will still load them into the DOM and consumes data for the user. This is not ideal for CMS pages that have unique sections and headers based on categories.

For example, if I want to have a unique hero header with a background video for each CMS item, I'd need to create all of them on the template page and hide them conditionally. Under current circumstances, the user will have to load all of these to load the page.

Server-side management of conditional visibility would make sure that the hidden sections never reach the DOM and are hence never loaded.

  • Khashayar Toodehfallah
  • May 14 2020
  • Reviewed
  • Stof Hofer commented
    December 14, 2023 11:28

    Agreed with everything mentioned. Please add this!

  • David Coleman commented
    November 19, 2023 17:03

    Very disappointed and concerned about this. I'm sure this will come back to bite me when SEO/accessibility audits pick it up. Basically means conditional visibility should only be used for very small elements.

  • Tom commented
    October 25, 2023 10:55

    we need this!

  • BrandBridge Media commented
    August 22, 2023 04:09

    Are there any updates on this? This is completely contrary to the requirements of SEO for website performance.

  • Roland du Toit commented
    March 08, 2022 23:37

    Yes please. This sort of blows my mind that this is how it's handled. Many of Webflows URL structure limitations and shortcomings can be overcome with the business plan for 60 CMS Fields per collection and using conditional visibility.


    The fact it still loads and then just hides it in the CSS and is not done on the serverside is pretty crazy.

    I would love this feature!

  • Benjamin Levis commented
    March 05, 2022 12:34

    Impressed by your ideas and writing skills

  • Esteban Suarez commented
    August 11, 2021 00:40

    It would solve all my problems if conditional visibility was server side. Why isn't it already? There are no drawback if moved to the server

  • Sam Pilgrim commented
    February 25, 2021 12:48

    Just discovered this. This is frustrating from a performance point of view.


    As has been pointed out elsewhere on the forum, deleting these elements from the DOM via JS has no real effect on performance since the elements have to be loaded anyway. https://forum.webflow.com/t/conditional-visibility-options-simply-display-none/120585

  • David Mack commented
    August 27, 2020 19:40

    This is impacting my page load speed as images are all loaded despite never shown

  • Glen Burnett commented
    July 13, 2020 09:48

    I concur with this feature wish list item. From an SEO point of view, it's not good to have content that is loaded when the page loads, to then be hidden from view. Google will still pick up on that content and mark down a site's search ranking results for hiding content that it thinks should be available for users to see.

  • +31