Let me start with a disclosure: we build custom-coded websites. So I have an obvious interest here. That is exactly why I will try to be as honest as possible — because if I wrote that WordPress is simply bad, you would not believe me, and you would be right.
The reality is duller: both have their place.
When WordPress is the right call
WordPress runs a huge share of the internet, and there is a reason for that.
- You want to change content constantly yourself. If you post weekly, add products, change prices — the WordPress admin is built for that and it is good at it.
- You need something that already exists. Bookings, membership areas, courses, forums. There is probably a plugin for it that has been maturing for ten years. Rebuilding that from scratch would be foolish.
- Budget is small and speed is not critical. A theme plus hosting and you are online.
- You want to be able to switch developers later. There are WordPress people in every town.
If your situation is on that list, I will say it plainly: take WordPress.
When it starts to hurt
The problems usually do not show up on day one. They show up in year two.
Plugin pile-up
Every feature arrives as a separate plugin. Forms — plugin. SEO — plugin. Images — plugin. Caching — plugin. Each one brings its own JavaScript and CSS, loaded on every page whether it is needed there or not. Eighteen plugins later the homepage takes three seconds and nobody is quite sure why.
Updates
Every plugin has its own author and its own schedule. Most updates go fine. Occasionally something breaks and you find out when a customer calls. And if you don’t update, the site becomes a security risk — WordPress sites are among the most common break-in targets for exactly that reason.
You pay for what you do not use
The theme you bought was built to suit as many people as possible. It contains restaurant, gym and law-firm features all at once. You use maybe a tenth of them, but the browser loads all of it.
When custom code is the right call
- Speed genuinely matters to you. If the site is where your customers come from, load time is money. A custom site contains only the code you use, and that is usually far less.
- You need something a template does not do. Once you start bending a template, you end up fighting the tool more than doing the work.
- You want the site to look like you, not like a theme. Honestly: a trained eye recognises the popular templates.
- You do not want monthly maintenance worry. No plugins means no plugin updates.
And the downsides of custom code
They exist and you should know them.
- Editing content is more limited. If you want to invent a new page type every day, a custom build without a solid admin will get in your way. (We build an admin in, but it is never as broad as WordPress’s.)
- Switching developers is narrower. Fewer people know this specific code. That is why it matters that the code is clean and that you own it.
- The upfront price can be higher. Though the gap is smaller than it used to be, precisely because the building itself got faster.
What we do ourselves
Our sites are written in real code with no plugin layer, and AI makes that building significantly faster than doing it by hand. The result is sites that load quickly because there simply is not anything extra in them — not because we did something magical.
But if you are reading this and thinking “WordPress would just be more convenient for me”, that is a perfectly sensible conclusion and I am not going to argue you out of it.
A simple decision rule
If you change content every week and need ready-made features — WordPress. If the site is your storefront and has to be fast and yours — custom code.
If you are unsure, write to us and describe what you do. If the answer is WordPress, I will say so.