Custom WordPress development: why we build business sites without page builders

We build business websites on WordPress with a theme we write by hand for each client, and we do not use page builders such as Elementor, Divi or WPBakery. The short reason: page builders make a site quick to start and expensive to live with. A hand-built theme loads faster, is harder for your team to break, needs fewer plugins and costs less to maintain over the five or so years a business site usually lasts. It costs a little more up front, and for most businesses that trade-off pays for itself.

This is how we reached that view, what custom WordPress development actually involves, what it costs, and the cases where a page builder is honestly fine.

Why WordPress at all?

WordPress runs around four in ten of all websites, according to W3Techs, which tracks the technology used by the top ten million sites. That popularity is the main argument for it, not a side effect. It means:

• You are never locked in to one agency. There are WordPress developers in every UK city, so if we got hit by a bus, someone in Manchester or Bristol could pick the site up next week.
• Your team has probably used it before, or knows someone who has.
• Most things a business needs (forms, shops, bookings, multi-language, membership) have a mature, well-supported option.
• Hosting is cheap and widely available, and you can move it whenever you like.
• The software itself is free and open source. You pay for design, development, hosting and upkeep, not a licence.

WordPress is not the answer to everything. Large catalogues with complex pricing may suit Magento, and some applications are better as custom software. For brochure sites, service businesses, content-heavy sites and small to mid-size shops, it is usually the right call. If you are still deciding, our CMS comparison covers WordPress, Shopify and Webflow side by side.

What a page builder actually does

A page builder is a plugin that replaces the WordPress editor with a drag-and-drop canvas. You pick a section, drop in columns, add a heading, a button, an image carousel, set colours and spacing by hand on each element. It feels like building with Lego, which is why a lot of agencies and DIY site owners love it.

Under the hood, the builder stores every page as its own structure of nested sections, columns and widgets, each with its own settings, and then generates the HTML, CSS and JavaScript to render it. That is where the trouble starts.

The problems we keep seeing on page-builder sites

We take over a lot of page-builder sites from businesses across the UK. The same issues come up again and again.

They are heavy

A typical page-builder page loads the builder’s framework CSS and JavaScript, icon fonts, animation libraries and the styles for widgets the page does not even use. We regularly see pages with several hundred kilobytes of scripts before any content, and a DOM (the structure the browser has to build) with thousands of elements for what is visually a simple page. On a mid-range phone over 4G, that shows up directly in poor Core Web Vitals. Builders have improved, and a skilled developer can trim a lot, but you are starting from behind.

Content gets locked in

Your words and images are wrapped inside the builder’s own shortcodes or data format. Switch the builder off and pages turn into a mess of brackets or vanish. Moving to a new design, or even a different builder, often means rebuilding every page by hand. That is a real cost that lands on you three or four years later.

Too much freedom breaks the design

Every heading can have its own font size, every button its own colour, every section its own padding. After a year of edits by three different people, the site has seven shades of blue and buttons in four styles. A good design system is about consistency, and page builders make consistency optional.

More plugins, more updates, more risk

The builder itself, its “pro” add-on, a third-party pack of extra widgets, a separate plugin for forms, another for sliders. Each one needs updating, each one can conflict with the others after an update, and each one is another entry point that automated attacks scan for. Several popular builder add-ons have had serious security vulnerabilities in recent years.

Accessibility is harder to control

We build every template to WCAG 2.2 AA. That means correct heading order, proper labels on forms, visible focus states for keyboard users, sufficient contrast and sensible markup for screen readers. Builders give editors the power to pick a pale grey on white or style a paragraph to look like a heading, and the generated code is not always semantic. It can be done, but it fights you.

How we build instead

We write a classic WordPress theme from scratch for each project. “Classic” here means a normal WordPress site, where WordPress both stores the content and displays the pages, rather than a headless set-up. In practice:

• A design system first. Colours, type sizes, spacing, buttons and form styles are defined once and used everywhere. Editors pick from them; they cannot invent new ones.
• A fixed set of content blocks. We build custom blocks for the native WordPress editor (or structured fields where a page has a rigid layout): hero, text and image, testimonials, pricing table, FAQ, team, call to action, and whatever your business needs. Each one is designed, coded and tested once.
• Only the code each page uses. Styles and scripts are loaded per block, images are served in modern formats at the right size, and there is no framework sitting underneath.
• Few plugins. On a typical brochure site we use somewhere between five and ten well-maintained plugins (SEO, forms, security, caching, backups), not thirty.
• Tested before launch. Lighthouse 95+ and WCAG 2.2 AA on every template, on real phones as well as desktops.
• Everything in your name. You own the theme code, the content and the hosting account.

Page builder vs hand-built theme at a glance

“But I want to be able to edit it myself”

You will. This is the most common worry, and it comes from older custom-built sites where every change meant emailing the developer. A modern WordPress block editor with custom blocks is genuinely easy: you add a block, type into it, swap an image, reorder sections. What you cannot do is change the font on one heading or make a button lime green, and that is deliberate.

At handover we run a training session (in person if you are within reach of London and the Home Counties, otherwise on a video call), record it so new staff can watch it later, and write a short guide specific to your site. If you need a new kind of section in a year’s time, we build it as a new block, usually in a few hours.

What custom WordPress development costs

Fixed-price packages

Most new business sites fit one of our packages. Current offer prices, excluding VAT:

Our Startup Website (£350) is a simpler five-page site; add the CMS option (+£149) if you want to edit it yourself.

Hourly WordPress development

For work that does not fit a package, such as custom blocks, integrations, migrations or ongoing changes, you can book WordPress development hours at £50 an hour excluding VAT. Hours are paid online and never expire. Volume discounts apply: 5 % on 10 hours, 10 % on 15, 15 % on 20, 20 % on 50 and 25 % on 100.

Worked example: replacing a page builder on an existing site. A 12-page Elementor site for a professional services firm, keeping the content and broadly the look, but rebuilding it on a hand-built theme with eight custom blocks. That is usually 35 to 45 hours including design tidying, block development, content migration, testing and redirects. At 40 hours: 40 × £50 = £2,000, less the 15 % discount for 20+ hours = £1,700, plus VAT of £340 = £2,040. Buying 50 hours instead takes the discount to 20 %, so 50 × £50 = £2,500 − £500 = £2,000 + VAT £400 = £2,400, leaving about ten hours banked for future changes.

Running costs

Budget for hosting (from roughly £10 to £40 a month for a business site on decent managed hosting), the domain, and maintenance: updates, backups, security monitoring and small fixes. Because a hand-built site has fewer plugins and no builder licences, maintenance is quicker and cheaper. Our guide to WordPress maintenance plans sets out what a plan should include.

Rebuilding a page-builder site you already have

If your current site works and brings in business, do not rebuild it just because of how it was made. Rebuild when one or more of these is true:

• Mobile Core Web Vitals fail and tuning has not fixed them.
• You are planning a redesign anyway.
• Updates regularly break something, or you are stuck on old versions because updating is risky.
• Your team avoids editing the site because things move about when they do.
• You are paying for several builder and add-on licences every year.

Our process: we audit the existing site, map every URL, design the block library around your actual content, migrate the content into the new structure, set up 301 redirects for anything that moves, and test against the old site before switching over. Done properly, a rebuild should hold or improve rankings. For a sense of the speed side, see our WordPress speed fixes.

When a page builder is fine

We are not dogmatic about this. A page builder is a reasonable choice when:

• You are building the site yourself with no budget for a developer, and the alternative is no site.
• It is a short-lived campaign or event site that will be switched off in a few months.
• You run lots of landing-page experiments and the marketing team needs total layout freedom, and you accept the performance cost.
• You already have a builder site that is fast, accessible and stable. Leave it alone.

For a business site that needs to rank, convert and last five years, we would build it by hand every time.

Working with us

We are a small development team based in St Albans, building WordPress sites for businesses across the UK, from sole traders to charities and national organisations. Have a look at our CMS development service, or send us your current site or brief through our contact page. We will tell you whether a package, a block of hours or a rebuild makes most sense, with a fixed figure before any work starts.

Photo: Daniil Komov via Pexels