WordPress or custom? An honest trade-off
Not every site has to be custom, and not every site fits in WordPress. Here is how to make the right choice.
WordPress fits if you want to create pages and their layout yourself, with an open system that runs on millions of sites. Custom work, in Astro for sites and Nuxt for applications, fits if the site has to do something of its own or should stay light. Both can be fast and findable. The set-up and the maintenance matter more than the name of the system.
Anyone having a new website built gets the question sooner or later: WordPress or custom? What you really want is a site that does what it should, that you can keep up to date and that is still standing in a few years.
We build both. Four of our cases run on WordPress, other sites we built in Astro and Nuxt, and we also maintain WordPress sites for clients. In this article you will read what the difference is, when each choice fits, what managing the site yourself means in each case, and how maintenance, speed, findability and switching work. At the bottom there is a decision table.
What is the difference between WordPress and custom?
WordPress is open source software under the GPLv2 licence. According to WordPress.org you may use it for any purpose, study how it works and change it. A WordPress site has three layers: WordPress itself, a theme that determines the design, and plugins that add features, such as a form, a shop or a translation. Admin and website are one system: you log in to the same installation your visitors see.
Custom here means: the site is built for your purpose with a framework, without a theme and without a stack of plugins. We use two tools for that. Astro builds every page in advance as plain HTML and only sends JavaScript where a page really needs it, such as for a form or a calculator. Nuxt is made for sites where the visitor does something, such as calculating a price or booking. The page first arrives as plain HTML, and then Vue takes over for everything that needs to respond. Astro and Nuxt are both open source, under the MIT licence.
With custom work the content lives in the site’s files, or in a separate content management environment if you want to edit texts yourself. Such an environment is called a headless CMS; more about that in our article on headless CMS.
| WordPress | Custom in Astro or Nuxt | |
|---|---|---|
| What is the site made of? | WordPress, a theme and plugins | Code written for this site, possibly with a separate content management environment |
| Who decides the layout of a new page? | You, in the WordPress editor, within what the theme allows | The website: you fill in the content in fixed fields |
| Create new kinds of pages yourself? | Yes | No, that goes through the developer |
| What needs to be kept up to date? | WordPress, the theme, every plugin, the database and the server | The framework and its packages, the server and, if there is one, the content management environment |
| What does speed depend on? | The theme, the plugins, the images and the hosting | The build, the images and the hosting |
| Carry on with another developer? | Many developers work with WordPress | Possible, with the code and the documentation; the new developer does need to get to know the code |
When does WordPress fit well?
Our page on web development puts it briefly: if you want to manage a lot yourself, we build in WordPress. That is the main reason. In WordPress you create a new page yourself, choose its structure and add a text, photo or button, without calling anyone. WordPress also fits if:
- You publish a lot and often, such as articles, news or a knowledge base, and want to do that yourself.
- You already work with WordPress and are happy with it. Then a new site in the same system is often the shortest route.
- There is a plugin that does exactly what you need, and you would rather use it than have something built.
- You want to be free to choose a developer later. WordPress is open source and, according to WordPress.org, runs on millions of sites, so you can easily find another party that works with it.
A WordPress site does not have to be small. For EZ Factory we built a site in WordPress in Dutch, English and German: 611 addresses, a knowledge base of 163 Dutch articles and a savings calculator with fourteen fields. MijnbouwSubsidie is the other extreme: seven pages and thirteen articles, with one form for every request for help. What else a site for a manufacturer needs is on web design for manufacturing companies.
When does custom work fit better?
Custom work fits if the site has to do something that does not come ready-made in a theme or plugin, or if you want as few moving parts as possible. Think of:
- Calculating or booking on the site itself. At Sittard Taxi a traveller chooses a destination or airport, sees the fixed price straight away and books directly. The homepage with that booking wizard is a Nuxt app; the service and town pages are static pages in the same style, about 32 KB of HTML per page.
- Many pages that should stay light. TaalPro has 159 pages in Dutch, English and Farsi. Every page is online ready-made; only a tool, such as the level test, loads its own script, on its own page.
- Connections with what you already use, such as your planning, your bookkeeping or a private area where customers log in. Which connections are possible, we find out before the build starts.
- A site that rarely changes. Then you need no content management environment, and so nothing to maintain on that side. The developer changes the texts when needed.
The sector does not decide it. Tandartsenpraktijk Alexander in Rotterdam runs on WordPress, with a page of its own for each of its eleven treatments and a form to register. Atiq Tandartsen in Zwolle we built in Astro, also with a page per treatment and a registration form, there with room for five family members. So the same features are possible in both. The question is what happens to the site afterwards: who maintains it, how often something changes and what it still needs to do.
If you are torn between Astro and another framework for custom work, read Astro or Next.js. How we build is under Astro and Nuxt.
What does managing it yourself mean in WordPress, and with custom work?
You can manage both yourself, but it feels different.
In WordPress you have a lot of freedom. You create new pages and decide their layout. The downside: if more people work on the site, pages drift apart more easily. One page gets a different heading, another a button in a different colour. A few fixed agreements, such as a style guide, help against that.
With custom work you fill in content in fixed fields, and the website decides how it looks. At TaalPro the school edits texts, exam dates, groups, teachers and reviews itself, without code. For that the site got Sveltia CMS, a content management environment that keeps the content in the site’s own files. A new kind of page, with a different structure, does go through the developer. Note: on a site in Astro a change only goes online after the site has been rebuilt.
What you should get in either case: at handover an admin manual to edit texts and images yourself, step by step, technical notes on hosting, domain and integrations, and a style guide. That is how our process works.
Are you tied to your developer with custom work?
That is the honest worry with custom work, and it is justified. With WordPress another developer already knows the system. With custom work they have to familiarise themselves with code written for your site. You are tied if you do not have the code, the login details or the documentation.
So ask beforehand who owns everything after handover. With us, domain, code, designs and data are put in your name on payment, with source files and documentation; only our general building blocks stay ours. That applies to a WordPress site just as much as to custom work. You can be tied with WordPress too, for example if the hosting or the licence of a paid plugin is in your developer’s name.
What about maintenance and security?
Every site needs maintenance, even if it looks fine. For WordPress this is well described by WordPress itself. The security guide on WordPress.org gives, among others, this advice:
- Always keep WordPress on the latest version, and make sure your plugins are always updated.
- Do not use plugins or themes from sources you do not trust.
- If you do not use a plugin, remove it.
- Make regular backups, including of the database.
- Turn on two-step login as extra protection.
Part of it happens automatically. Since version 3.7 WordPress applies minor updates, such as maintenance and security releases, automatically. Since version 5.6 new installations also get major updates automatically. For plugins and themes you switch on automatic updates yourself since version 5.5, per plugin and per theme. WordPress advises first making sure you can go back to a previous version if something goes wrong.
The WordPress security team looks after the core of WordPress. Plugins and themes belong to their own makers, each with its own pace. The more plugins, the more makers you depend on.
Custom work needs maintenance too, but with fewer parts. A site in Astro is online as ready-made pages; when a page is opened, no content management system runs along with it. What needs to be kept up to date: the framework and the packages the site is built on, the server, and the content management environment if there is one. With an application in Nuxt, the server that builds the pages is added to that.
We maintain both. With a maintenance plan updates and security run in a fixed monthly rhythm, a copy you can restore is ready every day, and each month you read in plain language what was done. That is also possible for a site we did not build, after a technical check.
Is custom work faster than WordPress?
Not automatically. A fast WordPress site is possible, and so is a slow custom site. In our own measurements they are close together. We measure the same way each time: phone screen, slow connection, empty cache, three runs and the median result. We measure the time until the largest piece of content is in view. The table only includes sites whose load time is on the case page.
| Site | Built in | Load time on a phone | Measured on |
|---|---|---|---|
| TaalPro | Astro | 0.78 s | 22 October 2026 |
| Daily Phones | WordPress | 0.94 s | 22 October 2026 |
| Ikiz | Astro | 0.98 s | 22 October 2026 |
| Sittard Taxi | Nuxt (homepage with booking wizard) | 1.23 s | 22 October 2026 |
Google rates up to 2.5 seconds as good, measured with real visitors. All four stay below that in our test measurement. For our other three WordPress cases there is no load time on the case page, so we say nothing about them.
With WordPress, speed depends mainly on the set-up: a heavy theme, many plugins, a page builder and oversized photos make a site slow. With custom work, speed lies more in the foundation: what is not sent along does not need to load. More in why every second of load time counts.
What does the choice mean for your findability?
Google does not look at the system, but at what a page shows. Google writes that it is still a good idea to render pages on the server or in advance, because it makes a site faster and not all bots run JavaScript. WordPress delivers complete pages from the server. Astro builds them in advance, Nuxt on the server. So all three are easy to read for search engines and AI assistants, as long as the content is in the page and not loaded later.
What makes more difference: pages that answer your visitor’s question, a clear structure and structured data, a description in the code that search engines read directly. That is possible in both. MijnbouwSubsidie runs on WordPress and has structured data on all 20 pages, with questions and answers on 12. Atiq Tandartsen we built in Astro, with structured data on all 85 pages. If you are already on WordPress and want to be found better, look at SEO and GEO first before thinking about switching.
How do you switch without losing your findability?
Switching is not a goal in itself. It is a project of its own, with its own costs. Do it when your current site can no longer do what you need, not because something is new. If it goes ahead, Google gives clear guidance for a move in which addresses change:
- Make a list of old and new addresses. Google calls this important: every old page gets a new place.
- Redirect every old page permanently. Google recommends permanent server-side redirects, such as a 301 or 308.
- Keep the redirects in place for a long time. According to Google as long as possible, generally at least a year.
- Keep the content that gets found. A page that attracts visitors deserves an equally good successor, not a summary.
- Check after going live that the links work and the structured data is correct, and keep an eye on Search Console.
Google warns that your visibility in the search results may fluctuate temporarily during a move. So do not plan a switch just before your busiest month. Before going live, we set up the redirects and check every page for links and structured data.
Which choice suits you?
Go through the questions below. If most answers fall in one column, you know the direction. If it comes out mixed, a conversation is the quickest route.
| Question | Choose WordPress if... | Choose custom if... |
|---|---|---|
| Who edits the site? | You or your team, including new pages and their layout | You fill in content in fixed fields, or the developer does it |
| How often does the site change? | Often, with new kinds of pages | Now and then a text, or always the same kind of content |
| What must the site do? | Inform, publish, something an existing plugin does well | Calculate, book, connect, or a private area where people log in |
| How many parts do you want to maintain? | You accept theme and plugin updates, or outsource them | As few as possible |
| What do you have now? | A WordPress site you are happy with | A site that can no longer do what you need |
| How important is a free choice of developer? | Very important | Important, but you get code and documentation with it |
What it costs depends on what the site has to do, not only on the system. Starting prices are on our pricing page. A website goes live with us in two to four weeks, a webshop or custom platform in six to ten weeks. After one conversation the price is fixed. How we build a webshop is on ecommerce website design.
How do you recognise a healthy technical foundation?
Many sites get stuck on small build choices that pile up: a plugin here, a workaround there. After a few years nobody dares to press the update button. That can happen with WordPress and with custom work. There is also a third option, a SaaS builder: maintenance is included in the price, but your freedom and your data sit with the provider. Every choice has an honest use. It goes wrong with the wrong combination, such as a custom platform for a simple brochure site or a page builder for an application your business runs on.
| Healthy foundation | Ticking time bomb |
|---|---|
| Updates are routine, not a project | “Do not update, something might break” |
| Someone can name every integration | Plugins nobody knows the reason for |
| The backup was restored as a drill this year | One external person who alone knows how it works |
| New wishes take days, not weeks | Every change starts with a sigh |
Two things weigh more than a few years ago. Your dependencies: the biggest weakness usually sits in everything around your own code, such as outdated plugins, abandoned packages and external scripts. Choose them deliberately and keep them up to date. And privacy: external fonts and scripts that send data to third parties are a legal risk, especially if you also sell in Germany. Host yourself what you can host yourself, and measure only with consent. How to restore that backup as a drill is in test your backup.
When this does not apply
This article is about websites for businesses and organisations: informing, being found, a request or booking. For a large webshop with thousands of products or an application that mainly runs behind a login, other questions come into play. That is what web development is about. And if you have a WordPress site that works well and that you maintain well, there is no reason to switch.
What we do not know: we have no figures on how often WordPress sites or custom sites are hacked, so we give none. We have not measured whether the same site scores better in Google in WordPress or in Astro. The load times are our own measurement of our own work, per site on one day, and not data from real visitors. For three of our four WordPress cases there is no load time on the case page.
Frequently asked questions
Is WordPress still a good choice in 2026?+
Is custom work faster than WordPress?+
Can I edit texts myself on a custom site?+
Is WordPress insecure?+
Will I lose my place in Google if I switch?+
Wondering what suits your site? Tell us what your site has to do and who maintains it, and we will advise WordPress or custom, with the reason. More about how we build is under web development. You work directly with Nawid, with a fixed team of five specialists.
Sources
Consulted on 3 November 2026.
- WordPress.org, About (open source, GPLv2, the four freedoms)
- WordPress Developer Resources, Hardening WordPress (security advice)
- WordPress Developer Resources, Upgrading WordPress (automatic updates since 3.7 and 5.6, updated 28 October 2026)
- WordPress.org, Plugin and themes auto-updates (since 5.5, updated 13 January 2023)
- WordPress.org, Security (security team, updated 24 April 2024)
- Astro, Why Astro?
- Astro on GitHub (MIT licence)
- Nuxt, Rendering Modes (universal rendering)
- Nuxt on GitHub (MIT licence)
- Sveltia CMS on GitHub
- Google Search Central, JavaScript SEO basics
- Google Search Central, Site moves with URL changes
- Empireyo, Daily Phones case
- Empireyo, TaalPro case
- Empireyo, Web development (technology and ownership)
- Empireyo, Process (handover and lead time)
Also worth reading: How much does it cost to have a website built?
Written with the help of AI, reviewed and edited by Nawid Rasa, who is responsible for the content. Sources are listed below the article. Spotted an error? Email hi@empireyo.com.
Unsure about the right foundation?
We advise honestly on WordPress or custom and build what fits your ambition.
Your request has reached us. You will usually hear back within two working days. Prefer direct contact? Email hi@empireyo.com or message us on WhatsApp with the chat button at the bottom right.