When someone asks me to build or fix a WordPress site, one of the first things they assume is that it has to run on a page builder. Elementor, Divi, one of those. The editor that comes built into WordPress gets written off as the free beginner option, the one you reach for until you can afford the real tool.
I don’t build that way, and it’s one of the few opinions I hold strongly enough to lead with.
What a page builder is.
A page builder is a plugin that bolts a drag-and-drop design layer on top of WordPress. Elementor and Divi are the two you’ve probably heard of. They were useful for years, back when the editor that shipped with WordPress could barely handle two columns side by side. If you learned WordPress before about 2020, a page builder was close to required, and plenty of good sites still run on one today.
What’s changed is the problem they were solving for. WordPress now has its own block editor built in, no extra plugin, and it has quietly gotten good. For the kind of sites I build most, small businesses and nonprofits, it handles the layouts, the columns, the galleries, all the normal pieces, without a second design system layered on top.
Why I don’t reach for one by default.
Three reasons, and none of them are about the builders being bad tools.
The first is speed, the kind Google measures. A page builder adds a lot of code to every page so it can offer all that drag-and-drop flexibility, and most of that code loads whether a given page uses the fancy parts or not. Sites built on the heavier builders tend to struggle with Core Web Vitals (Google’s page-speed scores), and on a phone over a so-so connection, you feel it.
The second is what happens at update time. A page builder is a big piece of software sitting between you and your content, and every update carries some risk of shifting a layout or breaking a section you can’t easily put back. I’ve had an Elementor update break a client site; I don’t know exactly what it changed, but I had to revert the site and then turn off automatic updates for the builder so it couldn’t happen again unattended. When the builder is what broke, you can’t fix it without the builder, which brings me to the third reason.
The third is lock-in, and it’s the one I care about most. A page builder builds your pages in its own format. Turn the plugin off, or let the license lapse, and your carefully built pages can come apart, because the layout lived inside the builder, not inside WordPress itself. That ties you to one plugin (and often its yearly fee) for as long as the site exists. I’d rather the site be yours, in a form you can hand to anyone, including a future developer who isn’t me.
When I do reach for one.
When the client already has a reason to. If you’re on Elementor or Divi today and your team knows it and likes it, I’m not going to march in and rebuild everything to prove a point; I work on plenty of page builder sites and keep them running just fine. The difference is I won’t talk someone into a page builder who doesn’t already have a preference, because for most of the sites I build, it’s a cost (in speed, in fragility, in lock-in) without a matching payoff.
How to tell what yours is built on.
If you’re curious what’s running your own site, the quickest tell is the editing screen. When you go to edit a page, a page builder usually opens its own full-screen workspace with a panel of widgets you drag around (Elementor and Divi both look like their own apps). The block editor looks more like a clean document where you click a small plus sign to drop in a heading or an image. Neither one is wrong. But if your site is on a builder and nobody ever told you, it’s worth knowing, because it’s part of what you own.
That’s the whole reason I default to the block editor. A site should be something you can keep, move, and hand off without asking anyone’s permission, and the fewer paid layers standing between you and your own pages, the easier that is.
If you’re not sure what yours is built on, or what that means for you, that’s a good thing to find out, and a fine reason to say hello.