Opinions split on page builders because both sides are true. Builders are genuinely useful and they genuinely cost something. Advice that only states one half is no help in making a decision.
What builders are genuinely good at
A builder has one core value: letting someone change a page without going through a developer. If the copy on a campaign page has to change today and the person responsible cannot touch code, a builder turns that into a few minutes. This is not a small thing — whether marketing can ship a page unaided directly changes how fast a company moves.
There is a designer benefit too. You can test a layout against real content before handing anything to code, and that exercise surfaces plenty of problems early.
The cost: layout becomes data
Pages built this way are stored in the database rather than in files. It is the same species of problem as the Additional CSS panel from part three, at much larger scale: this time it is the entire layout.
The cost that surfaces latest is portability. Deactivate the builder and those pages generally do not revert to anything usable. Changing or removing a builder therefore stops being a settings change and becomes rebuilding the pages. That is easy at five pages and effectively impossible at eighty.
Design consistency leaks quietly too. A builder gives editors freedom to pick any colour and any spacing, and that freedom becomes eight shades of grey and twelve spacing values. It is not the editors’ fault; it is what high freedom always produces.
Draw a line and you can have both
The answer that works in practice is not “use it” or “avoid it” but how far you let it reach.
The criteria are how often it changes and who owns it. The site frame — header, footer, shared templates — changes rarely and is owned by designers and developers, so it lives in code. Pages that change often and belong to marketing live in the builder. Then, if you ever have to remove the builder, what you lose is limited to a known set of pages.
If you do adopt one, make a habit of checking a single thing: deactivate the builder on a staging copy and see which pages fall apart. That list is your exposure to the plugin, and a list that keeps growing means the line is leaking.
How builders affect performance is covered further in the Themes & plugins archive, and keeping a builder-based site while sorting out speed and security is part of our optimization program.
Next part
The last part is a theme audit: measuring what your theme actually downloads, and removing what nothing uses without breaking anything.