Two routes lead to a WordPress site. One is a page builder — Elementor, Divi, WPBakery and the rest — which gives you visual control over layout without writing code. The other is a custom build, where the design system and the templates are written for the project.
Both produce working websites. They fail in different places, and they suit different businesses. The mistake is not picking one over the other; it is picking without knowing which trade-offs you have accepted.
What a page builder is good at
A builder collapses the distance between an idea and a page. A marketing team can put a landing page live on a Tuesday afternoon without a developer, restructure it on Wednesday, and run a campaign against it on Thursday. That is a real commercial advantage, and no amount of architectural purity replaces it.
It also lowers the cost of the first version. If the budget has to produce something credible now rather than something optimal later, a builder is often the honest answer.
And it removes a dependency that businesses underestimate: the dependency on the developer. A site your own team can change is a site that stays current.
What it costs
Weight
A builder ships a general-purpose rendering layer capable of producing any layout the editor allows, on every page, whether that page uses those capabilities or not. On a good connection nobody notices. On a phone on mobile data — which is how a large share of UAE traffic arrives — the difference is visible.
This is manageable rather than fatal. Scoping the builder’s assets to the pages that need them, controlling plugin count and caching properly will recover most of it. It does need someone to do that work deliberately; it does not happen by installing the plugin.
Portability
Layout built in a builder is stored in that builder’s format. Moving away later means rebuilding those pages rather than exporting them. That is a genuine cost, and it is worth pricing at the start rather than discovering in year three.
It matters less than it sounds if the site is a marketing site whose pages you would want to rewrite in three years anyway. It matters a great deal if the site holds structured data — a catalogue, a member area, a property listing set — which is why that kind of content belongs in proper post types and custom fields rather than inside page layouts, whichever route you take.
Drift
Give every editor freedom to set any margin, colour and font size on any element and, eighteen months later, the site has fourteen shades of the brand colour and six heading sizes, because each was set individually by whoever was editing that day.
This is the most preventable of the three and the most commonly ignored. A defined set of global colours, typography and spacing — enforced in the tool rather than written in a brand guideline nobody opens — keeps a builder site consistent for years.
What a custom build is good at
A custom build starts from the requirement rather than from a set of available components. Content that has a real structure gets a real structure: post types, taxonomies and fields that match how the business actually thinks about the thing being published.
Only the CSS a page needs is shipped. Behaviour that would otherwise require a plugin is written once, in a few lines, with no settings screen and nothing to update. And because the design system lives in code, consistency is the default rather than something that depends on the discipline of whoever is editing.
The cost is time at the start, and a dependency on someone who can change the templates when the requirement changes.
The questions that actually decide it
- Who edits this site, and how often? A team publishing weekly needs different tooling from a company that changes three sentences a year.
- Is the content structured or is it pages? Products, projects, properties and people belong in defined content types. Marketing pages do not.
- What is the performance requirement? A brochure site and a store where every second of load time costs orders are not the same problem.
- How long does this version need to last? A campaign microsite and a five-year platform justify different investment.
- What happens when you want to move it? Ask the question before you commission, not after.
The answer is usually both
In practice, most sites we work on land somewhere in the middle: a custom theme and custom content types carrying the structure and the design system, with visual editing available on the ordinary pages so the client’s team is not blocked on us to change a headline.
What matters is that the decision is made deliberately, with the trade-offs named, rather than inherited from whatever the previous developer happened to install.
If you would like to talk through which approach fits your project, get in touch, or read more about how we approach custom WordPress development.