The case against page builders for business-critical sites
Page builders solved a real problem in 2016. Today the block editor solves it better, with a fraction of the weight and none of the lock-in.
On this page 5 sections
Key takeaways
- Page builders ship their whole component library to every page, which makes sites heavier and slower to respond.
- Builder content is stored in a proprietary format; the native block editor stores HTML that survives theme changes.
- Builders are fine for quick campaigns and prototypes.
- For long-lived business sites, a custom theme on the block editor costs more up front and less every month after.
We have fixed a lot of page-builder sites, including some genuinely tangled ones. This is not a rant against the people who use them. It is an argument that, for any site a business depends on, a custom build on the native block editor is now the better choice.
The weight problem#
A builder ships its entire component library to every page, plus styles for options you never used. Hundreds of kilobytes of CSS and JavaScript before your content appears is common. A custom theme for the same design usually needs a fraction of that, and it shows in how quickly pages load and respond.
The lock-in problem#
Builder content is often stored as shortcodes or proprietary data. Switch builders, or stop paying for the pro licence, and pages can fall apart. Block editor content is HTML with small annotations; it survives theme changes and exports cleanly.
The maintenance problem#
Each builder update can change rendering, break add-ons or require a template migration. The native editor is maintained by WordPress itself and evolves with it.
What builders still do well#
Rapid prototypes, campaign landing pages, and letting a founder launch something tonight. If that is the job, use one. Just do not expect it to be the foundation of a fast, long-lived site.
The alternative#
A design system defined once, a handful of custom blocks and patterns, hand-written CSS, and an editor your team already knows. This website is built that way: no page builder, one stylesheet, one small script.
When we rebuilt PolicyAdvisor’s blog templates, their CTO’s review singled out the improved site speed and Google PageSpeed results, alongside the new content types. Speed was a by-product of building less, not of a plugin.
Sources and further reading
- Block Editor Handbook — WordPress Developer Resources developer.wordpress.org