Page builders are genuinely useful for some projects. But the trade they involve is rarely explained honestly before a build starts, so it is worth setting out plainly.
What you gain
Speed at the beginning, and visual editing without a developer. For a small brochure site that will not change much, that can be the right answer.
What it costs
Weight
A page builder ships a general-purpose rendering engine to every visitor, because it cannot know in advance which of its features a page uses. That is hundreds of kilobytes of CSS and JavaScript before your own content loads, and it lands hardest on mobile, on a mid-range phone, on a poor connection.
Core Web Vitals
That weight shows up directly in Largest Contentful Paint and Interaction to Next Paint. These are ranking signals, and more importantly they are the difference between a site that feels immediate and one that feels sluggish.
Lock-in
This is the one people underestimate. Page-builder content is stored in the builder’s own format. Deactivate the plugin and your pages do not degrade gracefully. They become unreadable markup. You cannot leave without rebuilding.
Consistency drift
Because anyone can change anything, they do. Eighteen months later a site has nine button styles and five heading sizes, and nobody decided that. It accumulated.
The alternative
A hand-written theme with properly structured editable content. Your team can still edit text, images and content blocks. What they cannot do is accidentally invent a tenth button style. The site stays fast because it only ships the code it actually uses, and the content stays in standard formats you can take elsewhere.
It costs more up front. It costs considerably less over three years.
Want this looked at on your site?
We’ll audit it and tell you what we find, plainly.