I build custom sites. Clients ask whether a page builder would do the job instead, and the honest answer is that page builders are good tools that made the web easier for everyone. They are just not as good as custom when what you need is something specific, fast, and fully yours.
What the builders traded away
A page builder has to work for everyone, so it ships a little of everything. Extra scripts, extra styling, a database call for every piece of content. A typical WordPress page runs somewhere between 30 and 80 database queries just to load. A hand-built HTML page runs zero. You feel that difference as weight.
That weight shows up in the numbers. Only about 44 percent of WordPress sites pass Google's Core Web Vitals, the speed and stability checks Google uses to judge a page. Sites built as lean, custom code pass at over 88 percent, and in head-to-head tests static pages have loaded around 78 percent faster than their WordPress equivalents.
Why it suddenly matters more
Speed has been a Google ranking factor since 2010, and Core Web Vitals became an official ranking signal in 2021. So a slow, heavy site was always a quiet tax on how well you showed up. Most people made peace with it.
Then AI search changed the stakes. Tools like ChatGPT and Google's AI answers now read the web to write their responses, and they are pickier than a person. Many AI crawlers cannot reliably run JavaScript, so anything a builder renders with scripts can be invisible to them. They also work on a time budget and skip slow pages. If you want to be quoted in an AI answer, your content has to sit in clean, fast, readable HTML. That is exactly what custom code is.
The clean-HTML advantage
There is a name for optimizing to be cited by AI: answer engine optimization. The fundamentals are almost boringly simple. A clear heading structure, real content in the raw HTML, and light, fast pages. Pages that get cited in AI overviews tend to score noticeably better on heading structure alone. Custom code lets us build every page that way on purpose, instead of hoping a theme happens to.
But can you still edit it yourself?
This is the honest catch, and the reason builders won for so long. Custom code used to mean calling a developer for every small change. If you could not write code, you were locked out of your own website.
That barrier is over. Large language models can now read and write code, so the work that used to belong only to developers is quickly becoming something anyone can do with a little help from AI. The old gap between using a builder and editing real code is closing fast, and it is not coming back. The thing that made page builders feel safe, that you could touch it yourself, is no longer theirs alone.
We build for that reality. Your site is set up to be simple to update where you need it, and we stay on as the people who keep it current. You get the performance of custom without the helplessness that used to come with it.
How I actually decide
Most of my projects still run on Webflow, and that is not a compromise. If a site is mostly pages of content, if the team wants to move things around themselves, or if the budget is better spent on the brand and the photography than on the build, Webflow is the right call and I will say so.
I move to custom code when the project starts pushing against what a platform will do. An interaction that has to feel a specific way. A layout that does not fit the box. A site where every tenth of a second of load time is worth paying for because being found is the whole point. That is where custom stops being ideology and starts being the practical option.
Page builders are not going away and they are not bad. For plenty of sites they are perfectly fine. But if you want the thing built exactly the way you imagined it, custom is still better, and it is no longer the expensive, fragile choice it used to be.
