WordPress, custom code or a website builder: which fits you?

Anyone having a website made sooner or later gets the question: WordPress, a website builder or a custom site? Every party sells its own route as the best. We build custom work ourselves, so you may read our opinion with some suspicion. That is why we try to be as honest as possible here: no route always wins, and for some businesses a website builder or WordPress is simply the wisest choice. Below you can read how the routes differ and on which points you should compare them.

What we mean by the three routes

• Website builder (hosted): an online service with which you assemble a site yourself or with help, including hosting and maintenance of the platform. You work within the possibilities of the platform.
• WordPress (or another CMS): open-source software that you install on your own or rented hosting, usually with a theme and plug-ins. You can customise a lot, but you also manage more yourself.
• Custom code: a site designed for your situation and built in code, with or without a content management system. Everything is possible, but you pay for the design and build.

The boundaries are not sharp: you can customise WordPress heavily, and a custom site can use an existing CMS. It is about the choices underneath.

Six questions to compare the routes

1. How unique must the design and behaviour be?

A theme or template is a good basis if you mainly need a neat, recognisable site. If your brand or way of working is really different, or if visitors need to be able to do something standard components do not offer, you run into limits. That is not a matter of right or wrong, but of fit. On the “generic” side we wrote in AI slop versus custom work.

2. Who does the maintenance and what happens if it is not done?

This is the question that is underestimated most often. With a hosted builder the platform belongs to the provider; they maintain the basics. With WordPress you (or your partner) manage the software, the theme and all the plug-ins. The WordPress security guide describes security as risk reduction, not risk elimination, and advises keeping WordPress itself up to date. The same therefore applies to everything around it. With custom code without a content management system there is less software to update, but also less convenience for anyone who wants to change text themselves. What this involves in practice is in Website security for business owners and in the maintenance checklist.

3. How fast and smooth must the site be?

Speed is not a property of a system but of how it is used. In Web Vitals, web.dev describes the measurements for loading speed, interactivity and visual stability. A bare WordPress installation can perform perfectly well; a site with many plug-ins and a heavy theme may not. A website builder can perform well as long as you stay within the standard options. With custom code you decide yourself what is loaded, which gives more control but also more responsibility. More about the measurements: Core Web Vitals explained.

4. What about accessibility and search engines?

Accessibility depends on the execution, not on the route: the W3C's WCAG 2.2 give the criteria, and any system can meet or miss them. So check what the theme or builder does by default and whether you make the text, colours and images accessible yourself. Something similar applies to search engines: Google's SEO Starter Guide describes the basics (helpful content, clear titles, reachable pages) and you can do that well or badly in any route. See also Accessible website and the European Accessibility Act.

5. Who owns it and can you leave?

This is one of the most important and least discussed questions. Can you export your content and design and use them elsewhere, or are you stuck on the platform? With WordPress and custom code you usually hold the files and the database, but there too what you may use has to be in the agreements, for example which licences a theme or plug-in has. With a hosted builder, ask explicitly what you can take with you if you stop. This is not legal advice; have agreements about ownership read if you are unsure.

6. What does it cost in a few years?

A builder has a running subscription and low entry costs. WordPress has hosting, sometimes paid plug-ins and maintenance. Custom code has the highest entry costs, but often fewer separate subscriptions. So always calculate over several years and not just the build; how to compare quotes is in What does a website cost?.

WordPress's technical requirements in brief

WordPress.org lists as recommended requirements for the host, among others, PHP 8.3 or newer, MariaDB 10.11 or newer (or MySQL 8.0 or newer) and HTTPS support. Older versions sometimes still work, but according to the documentation they are end-of-life and may be vulnerable. It is a practical test for a cheap host: does it support the current versions, and who makes sure your site keeps up when the requirements change? This is also where WordPress sites most often go wrong: not at the software itself, but at an outdated environment or a forgotten plug-in. The OWASP Top Ten, an overview of the most serious risks for web applications, lists “Security Misconfiguration” and “Software Supply Chain Failures” among its categories in the 2025 edition. That touches exactly on this problem: wrongly configured environments and other people's software that your site relies on.

When which route makes sense

• Website builder: you want to start quickly and cheaply, your site is simple (a few pages, a form), you need little custom functionality and you do not mind staying inside the platform.
• WordPress: you want to be able to change text yourself, you have a blog or many pages, you want to use existing extensions and you have someone who takes maintenance seriously.
• Custom code: you need your own brand experience or specific behaviour, you want control over what is loaded and you want a site built around one goal, for example bringing in enquiries. That is what we do, and what we describe under custom websites.

Common misconceptions

1. “WordPress is free.” The software is; the hosting, the extensions and the maintenance are not.
2. “A builder is always insecure/slow.” That depends on the execution, not on the label.
3. “Custom is always better.” Only if the goal calls for it; for a simple site it is sometimes overkill.
4. “You can always switch later.” You can, but a move costs time and money, and without proper redirects you lose search traffic; see Moving a website without losing SEO.

A short decision aid

Write down what the site must do (for example, produce enquiries), who will change the text, how much time you want to spend on maintenance and how important a distinctive look is. Hold that against the six questions above. If you are still unsure after that exercise, it is a perfectly good subject for a conversation: we will tell you honestly whether we are a match, and if another route fits better, we will say so. Book a free intro call.

Sources

Reviewed on 28 October 2026 against the sources below. Rules and guidelines change; this article is general information, not legal or tax advice.

• WordPress requirements (WordPress.org)
• Hardening WordPress (WordPress Advanced Administration Handbook)
• Upgrading WordPress (WordPress Advanced Administration Handbook)
• Web Vitals (web.dev)
• OWASP Top 10:2025 (OWASP Foundation)
• Web Content Accessibility Guidelines (WCAG) 2.2 (W3C)
• SEO Starter Guide (Google Search Central)

Book an intro call