A page builder is a reasonable trade when a site needs to exist cheaply and quickly. The cost is not paid at launch. It is paid in page weight on every visit, in a growing stack of plugin dependencies, and eventually in the day when nobody can safely update anything and the only remaining option is a rebuild.
Nobody explains this at the point of sale, which is the reason for writing it down.
The kilobytes
A page builder must be able to render any layout anyone might ever construct with it. It cannot know in advance which of its hundred modules a given page uses, so it ships the code for all of them.
In practice that means 300 to 700 KB of CSS and JavaScript loading before your first word of content. Add the icon font, the animation library and the companion plugin the theme requires, and a simple page about a plumbing service arrives at two or three megabytes.
For comparison, this page is a fraction of that, and the difference is not cleverness. It is that a hand written theme contains only the code its own site uses.
The dependencies
This is the cost that actually hurts, and it is invisible for the first two years.
A page builder site is not one product. It is a builder, a theme built for that builder, several addon plugins that extend the builder, and often a license for each. Those pieces update on independent schedules, maintained by different companies with different levels of commitment.
Eventually one of them updates and something breaks. Or one is abandoned. Or a WordPress core update breaks compatibility and the fix waits on a vendor. The practical result is a site the owner is afraid to update, which becomes a site running outdated software, which becomes a security problem.
I audit sites in this state regularly. The owner knows the site is stale and has learned through experience that touching it causes problems.
The lock-in
The one people find genuinely surprising.
Your content is not stored as content. It is stored as builder specific markup, wrapped in the builder’s own shortcodes and data structures. Deactivate the builder and your pages do not revert to plain text. They become unreadable fragments.
That means you cannot leave. Not without rebuilding every page by hand. The builder is not a tool you used to make the site, it is a permanent runtime dependency of the site continuing to exist.
Compare that to what you should actually own after paying for a website. A hand written theme is a folder of readable files. Any competent developer can open it and work out what it does in an afternoon. That portability is worth more than any feature a builder offers.
When a page builder is the right call
To be fair to them, there are real cases.
A very small budget where the alternative is no website. A business that genuinely needs to build new landing pages weekly without a developer. A team with an in-house marketer whose job includes page production. In those situations the trade is deliberate and defensible.
The mistake is not choosing a page builder. It is choosing one without knowing what it costs, because nobody said.
What it looks like without one
A theme written for one business contains the layouts that business needs and nothing else. It has no license, no companion plugins, and no vendor whose roadmap you depend on. It keeps working across WordPress updates because it is not fighting anything.
The honest trade-off in the other direction: you cannot drag a new section onto a page yourself. Layout changes go back to whoever built it. If you are still deciding what to build on at all, the honest comparison is about who updates the site rather than which technology is fashionable. For a business whose site needs to work rather than be constantly rearranged, a hand written theme is usually the better deal, and it is the trade this site is built on.
Questions
Can I remove a page builder from an existing site?
Not without rebuilding the pages. The content is stored in its format. Plan it as a project, not a task.
Are some builders better than others?
They differ in weight and in how much they lock you in, and the differences are real but small relative to the shared trade-off. The structural issues apply across the category.
What about block themes?
WordPress’s own block editor is meaningfully lighter than a third party builder and does not lock you into an external vendor. It is a genuine middle ground. It still invites accidental design damage, which is why layouts here are fixed and only articles use the block editor.
