I used to be the person who installed a page builder on every new WordPress site. Drag, drop, ship. Then I started getting the follow-up emails six months later: the site broke after an update, the checkout looked different on mobile, and nobody could remember which of the forty widget settings controlled the button color. For a solo founder running a side hustle, that’s not a speed advantage. It’s a trap.
The core problem is that page builders store your layout as their own data format, not as WordPress blocks or theme templates. When the builder ships a breaking change — and they all do, roughly once a year — your pages don’t degrade gracefully. They render wrong or not at all, and the fix is usually ‘rebuild this section.’ I’ve watched a founder spend a Saturday rebuilding a product page instead of shipping the product. That’s the real cost, and it never shows up in the demo video.
So what do I recommend instead for a first store? The current WordPress block editor plus a block-friendly theme. The editor isn’t as flexible as a full builder, but it’s core software: it updates with WordPress, it doesn’t require a license, and when you switch themes your content survives. For a store with a homepage, an about page, a contact page, and product pages, you don’t need more flexibility than that. You need it to keep working.
Concretely, here’s the stack I’ve been handing to non-developers: a lightweight block theme, WooCommerce, and two plugins for layout help — one for reusable patterns and one for a simple grid block. That’s it. The homepage is a hero, a three-column product grid, and a short ‘how it works’ section. The product page is WooCommerce’s default template with the theme’s typography. You can build the whole thing in an afternoon, and more importantly, you can hand it to a client or come back to it in a year without a decoder ring.
Does this mean page builders are bad? No. If you’re building a marketing site with elaborate landing pages and you have someone who maintains it, a builder can be the right tool. The mistake is using one to paper over not knowing WordPress. The builder hides the underlying structure, so when something breaks you have no mental model to debug from. With blocks and a theme, you at least learn the machine you’re running.
There’s also the performance angle, which matters more for stores than blogs. Page builders load their own CSS and JavaScript on every page, and the heavier ones add hundreds of kilobytes before your product image even starts. On a $200 phone on mobile data, that’s the difference between a two-second load and a five-second one. WooCommerce checkout is already JavaScript-heavy; you don’t want to add a builder’s runtime on top of it. I’ve seen a store cut its checkout load time in half just by dropping the builder and using the theme’s default templates.
One caveat: if you’ve already built on a builder and the store works, don’t panic-migrate. The time to change is when you’re starting fresh or when an update breaks something you can’t fix. Migration is a project, and a working store beats a theoretically better one every time.
What I tell people now is simpler than any plugin list: your first store should be boring. Boring themes, boring templates, boring updates that don’t break anything. Save the creative energy for the product and the copy. The store is plumbing, and plumbing should be invisible.