Five years ago recommending Gutenberg over a page builder meant accepting real limitations. That is no longer the case. The block editor plus a good block theme now covers what most business sites need, at a fraction of the weight.
The remaining case for a page builder is genuine, and it is narrower than the market share suggests. Here is where each one wins.
Quick Info
What changed in Gutenberg
The block editor was launched half-finished and judged accordingly. What it can do now is a different product.
What it still lacks is fine-grained positioning, built-in interaction and animation, and the comfort of a pure drag-and-drop canvas.
The honest case for page builders
If you need three of those five, use a builder. That is a real requirement, not a failure of discipline.
The cost of a builder
Weight
A builder ships its own CSS and JavaScript framework on every page. In my own testing on comparable pages, the builder version consistently lands 100 to 400KB heavier and a fraction of a second slower on mobile. Bricks and the newer builders are considerably better than the older generation, but the runtime never gets to zero.
Lock-in
This is the bigger issue. Builder pages are stored as the builder's own markup. Deactivate the plugin and your pages become unrendered shortcodes or empty divs. You are committed for the life of the site, and if the builder is abandoned or changes its pricing, you have no cheap exit.
Dependency
A builder update can break a live site's layout. It happens rarely and it happens, and it is the reason a staging environment stops being optional once a builder is involved.
The question is not whether the builder can do it. It is whether you are happy to still be paying for it in 2032, because leaving means rebuilding.
How I decide
If you use Gutenberg well
If you use a builder well
Where this is going
Gutenberg keeps absorbing what builders do, and the builders keep moving upmarket into interaction design and workflow. The performance gap will narrow and the lock-in difference will not, because it is structural rather than technical.
For that reason my default recommendation for anything new is core blocks, and my recommendation for existing builder sites is to leave them alone and spend the money on content.
Frequently Asked Questions
For most business sites, yes. Full site editing, patterns and global styles cover what previously required a builder.
Bricks generally benchmarks best among the major builders, with Elementor improved but still heavier. All of them add a runtime that core blocks do not.
Not for its own sake. It is a rebuild, and the gain is a fraction of a second and future flexibility. Do it when the site is due for a redesign anyway.
Not directly. They can hurt Core Web Vitals through added weight, and heavily nested markup is harder for machines to parse cleanly. Both are manageable.
Your pages lose their layout and typically show raw shortcodes or unstyled content. That is the lock-in, and it is the main argument against builders.
Yes, and it is a reasonable approach: the builder for a few marketing pages, the block editor for posts. Keep the boundary clear so nobody has to guess which tool a page uses.
Before You Go
Gutenberg for anything new, a builder when you genuinely need popups, animation and pixel control without a developer, and leave working sites alone.
The decision is really about the next five years rather than the next five hours. If you are also choosing a theme, the theme guide pairs with this one.
Core blocks unless you can name why not.
I'm a marketing consultant, entrepreneur and content creator. I help businesses grow through practical marketing, websites, SEO, content and AI.
More About Tariq →