When you plan a new WordPress website, one decision shapes almost everything that follows: how will the pages actually be built? You can use a visual page builder like Elementor, Divi or WPBakery; the built-in block editor (Gutenberg) with a block theme; or a custom-coded theme designed specifically for your business.
Each approach affects how fast your site loads, how easily your team can edit it, how heavily it depends on third-party plugins and how painful the next redesign will be. Agencies often push the option they are most comfortable with. This guide lays out the trade-offs plainly so you can decide for yourself.
The three approaches explained
Page builders
A page builder plugin adds a drag-and-drop visual editor on top of WordPress. You design pages by dragging widgets - headings, images, buttons, forms, sliders - into rows and columns. Popular options include Elementor, Divi and WPBakery, often paired with a theme designed for that builder.
Block editor (Gutenberg) and block themes
WordPress's own editor uses blocks for every element. Since WordPress 5.9, block themes and full site editing let you edit headers, footers and templates with blocks too. This keeps you closer to WordPress core, with fewer extra plugins.
Custom-coded theme
A developer builds a theme from your approved design, coding only the templates and sections your site needs. Editing is usually done through custom blocks or structured fields (for example, Advanced Custom Fields), giving your team flexible but controlled options.
Head-to-head comparison
| Factor | Page builder | Block editor / block theme | Custom theme |
|---|---|---|---|
| Speed to first version | Fast | Fast to moderate | Moderate to slower |
| Page speed potential | Moderate - needs careful tuning | Good | Excellent if well built |
| Design freedom | High within builder widgets | Moderate to high | Highest |
| Ease of editing | Very visual, easy to learn | Familiar after short training | Easy if built with good blocks/fields |
| Risk of breaking layouts | Higher - anyone can move anything | Moderate | Lower - editable areas are defined |
| Plugin dependence | Depends on builder and addons | Low | Low |
| Long-term upkeep | Builder and addon updates | Core updates mostly | Developer maintains theme code |
| Ease of future redesign | Harder - content tied to builder format | Easier | Easier - content in standard fields/blocks |
Page builders: when they make sense
Page builders are popular for good reasons:
- Quick turnaround for simple sites and landing pages.
- Visual editing that non-technical team members find intuitive.
- Large ecosystem of templates and add-ons.
Where they hurt
- Extra code. Builders output additional wrappers, styles and scripts, which can slow pages - particularly on mobile.
- Addon sprawl. Many sites install several "addon packs" for extra widgets, each adding weight and update risk.
- Lock-in. Content built in a builder is stored in its own format. Switching away usually means rebuilding pages.
- Inconsistency. When everyone can change spacing, fonts and colours on every page, the design drifts over time.
Page builders work best for small sites with a limited budget of time, simple layouts and a disciplined team, or for marketing landing pages that change often.
Block editor: the underrated middle ground
Many business owners have not looked at the block editor since its early days. It has matured a lot. With a good block theme and a small set of well-designed patterns, your team can:
- Build pages from reusable patterns (hero, features, testimonials section, FAQ, call to action).
- Keep design consistent through global styles for colours and typography.
- Avoid a heavy third-party builder entirely.
The trade-off is that very unusual layouts may need custom blocks, which require a developer.
Custom theme: when it is worth it
A custom theme is the strongest choice when:
- Speed and SEO are business-critical - for example, when organic search is your main lead source.
- Brand consistency matters across many pages and everyone who edits them.
- The site has structured content - services, locations, team members, projects, products - that benefits from templates and fields rather than free-form layouts.
- You expect the site to grow for years and want clean foundations.
- Integrations are involved, such as CRM lead routing, custom calculators or API-driven content.
The hidden benefit: controlled flexibility
A good custom theme does not lock your team out. It gives them clearly defined editable areas - text, images, sections they can add, reorder or hide - while protecting layout, spacing and branding. Editors spend their time on content rather than fixing broken alignments.
Questions to ask before you decide
- Who will edit the site, and how often? Daily marketing updates favour easy, safe editing.
- How important is organic search? If SEO drives your leads, lean towards lean, fast builds.
- How many page types do you have? Many repeated page types favour templates and custom fields.
- How long should this site last? A site you plan to grow for years deserves solid foundations.
- What will the next redesign look like? Standard blocks and fields make future changes easier.
Decision guide by business type
| Business situation | Usually the best fit |
|---|---|
| Small business, 5-8 pages, rarely updated | Block theme or lean page builder setup |
| Service business relying on Google leads | Custom theme or well-built block theme |
| Many location or service pages | Custom theme with templates and fields |
| Marketing team running frequent campaigns | Block patterns or custom blocks for landing pages |
| Existing builder site that is slow and messy | Rebuild with custom theme or block theme |
| Content-heavy site with blog and resources | Custom or block theme focused on reading experience |
What good editing looks like in practice
Business owners often worry that a custom theme means calling a developer for every small change. It should not. Before you approve any build, ask for a short demo of the editing experience and check that your team can:
- Create a new service or product page from a template without help.
- Add, reorder and hide sections such as FAQs, feature lists and calls to action.
- Change images, headings and button links in a few clicks.
- Publish blog posts with headings, lists, tables and images.
- Edit SEO fields - page title, meta description and social sharing image.
- Preview changes on mobile before publishing.
If the answer to any of these is "the developer will do it", ask why, and whether it can be made editable.
Speed in plain terms
Speed is where the difference between approaches shows most clearly to Google and to your customers alike. A page builder page typically loads the builder's framework styles and scripts, then the widgets used on the page, then any addon packs. A block theme loads WordPress's own block styles, which are generally lighter. A custom theme loads only the styles and scripts written for that site.
None of this means a builder site must be slow or a custom site will automatically be fast. Hosting, images, caching and third-party scripts matter just as much. But a lean foundation makes good performance far easier to achieve and keep as the site grows.
Moving content between approaches
Content written in the standard block editor or stored in structured fields is portable - it can move to a new theme with relatively little effort. Content built inside a page builder's layout is tied to that builder. If you think you might change direction in a few years, this portability is worth weighing now.
If you already use a page builder
You do not have to rebuild tomorrow. Practical steps to improve an existing builder site:
- Remove unused addon packs and widgets.
- Enable the builder's performance features (asset loading only where needed, optimised DOM output where available).
- Standardise global colours and fonts so the design stays consistent.
- Replace heavy sliders and animations with simpler sections.
- Plan a rebuild when you next redesign, rather than layering more fixes.
Key takeaways
- Page builders are quick and visual but can add weight, addon sprawl and lock-in.
- The block editor has matured into a strong, lightweight middle ground.
- Custom themes offer the best speed, consistency and long-term flexibility, with editing defined by your developer.
- Choose based on who edits the site, how important SEO is and how long the site must last.
- Whatever you choose, keep plugins lean and design consistent.
Our team designs and builds WordPress sites using both block themes and custom themes, guided by UI/UX design and your actual content needs. Learn more about our WordPress development services or our broader website development work. Unsure which approach suits your business? Book a free consultation and we will walk through the options with you, then send a written proposal.
