Where I Am Coming From
First, the disclosure: I build and maintain WordPress sites with page builders like Elementor as part of my day job, and I am good at it. This is not a take from someone who tried a builder once and rage quit. It is a take from someone who has spent real hours inside these tools, shipped client sites with them, and fixed what they break. I just do not think they are where websites are going.
They Are Slow, and Users Pay for It
Page builders generate heavy pages. A simple hero section becomes a tower of nested wrapper divs, and the builder ships its own CSS and JavaScript for every widget it supports, whether your page uses it or not. The visitor's browser downloads and processes all of it. You can feel the difference on a slow phone connection, and search engines can measure it. When a hand-built page and a builder page show the same design, the hand-built one almost always loads faster.
They Are Fragile
Builder content is not really yours in the way plain content is. It lives in the builder's own markup, shortcodes, and serialized data. Deactivate the plugin and your pages collapse into soup. Update the builder and pray your layouts survive. Add one more plugin and watch two JavaScript bundles argue about who owns the page. Every WordPress developer has a story about an update that turned a homepage into abstract art, and most of those stories have a page builder in them.
They Are Inefficient Where It Counts
The promise is speed: drag, drop, done. And for the first landing page, that promise mostly holds. But sites are not one page. By page ten, every page is its own little snowflake of hand-dragged settings, and changing the design means visiting every snowflake. A design system, where content lives in structured fields and templates render it consistently, is slower on day one and faster every day after. Builders optimize the demo, not the lifetime.
Where I Think It Is Actually Going
- Structured content: the content lives in fields (titles, images, sections), cleanly separated from how it is displayed. Change the design once and every page follows.
- Component-based frontends: templates and components, whether in a WordPress theme or a React framework, that render fast and consistent pages from that content.
- Performance as a feature: Core Web Vitals affect search ranking, and lean hand-built pages win that fight without trying.
- AI-assisted development: the historic argument for builders was that writing code is slow and hard. That argument gets weaker every month.
To Be Fair to the Builders
Page builders earned their place. They let small businesses get online without a developer, and they let non-technical editors feel ownership over their sites. That mattered, and for some projects it still does. My argument is not that builders were a mistake. It is that they are a transitional technology, a bridge between hand-written HTML and whatever comes next, and bridges are for crossing.
The website you are reading is my proof of concept: the first version was hand-written HTML, and this version is structured content rendered by components. Adding a new project to this site means adding one object to a data file. No dragging. Nothing to break. It loads fast everywhere. That is the future I am betting on.