I just wanted to double check with you guys if when I hide components in Webstudio if they will appear on the live code (so slowing down the page speed / web vitals without any use).
In Webstudio it says under "Show" (where you set visibility of a component):
"Removes the instance from the DOM."
So it sounds like it should work well. But I want to double-check to know if I can rely on this method for scaling.
The case:Let's say I have this landing page here (s. screenshot).
In it there is a logo bar with the clients worked before. And I hide it in Webstudio. Will it be in the code?
Will it affect page speed for the user even while it's hidden?My idea is to build landing pages rapidly with an Airtable database and a Webstudio template that gets filled by this Airtable data (think a blog CMS but for landing pages). A/B Splittesting would be so easy from there on in Webstudio (at least with paid ads).
The landing page template is a long page with all possible sections and components – and we would hide the things we don't need with checkboxes in Airtable and conditional visibility in Webstudio.
This idea resonated with quite some clients so far because they can launch landing pages extremely fast with it and even a/b splittest what works best to max out results.
The question again:
Does Webstudio loads components in code of users that are hidden? Do hidden components affect page load speed and web vitals? 
