Two camps usually speak up in this argument: WordPress agencies, for whom WordPress is the answer to every question, and programmers, for whom WordPress is an insult. I do both - I look after WordPress sites and I build sites written from scratch - so I have nothing to sell in this dispute except the right fit. And the right fit depends on three things: who will edit the site, how fast it needs to be, and what it must be able to do in three years.
What the real difference is
WordPress is a ready-made system: an engine, an editing panel, thousands of plugins and themes. It powers over 40% of all websites, so every problem you hit has already been solved by someone. You pay for that with baggage: the site carries code for a thousand scenarios of which you use a few, and needs regular updates, because popularity makes it a target.
A custom-built site contains only what you need - in my case that means a static site: ready files served straight from the server, with no database and no admin panel to break into. Hence load times under a second where WordPress fights for three. The price of that lightness: every content change goes through the developer or a trained editor, and unusual features are programmed rather than installed.
When WordPress wins
- You edit content yourself - weekly news, menu changes, galleries. Anyone in the company can drive the WordPress panel without calling anybody.
- A blog is the core of the site - categories, tags, archives, comments: exactly what WordPress was born for and remains comfortable at.
- You need proven integrations - bookings, sign-ups, courses, multilingual content. A €50 plugin replaces weeks of programming.
- The budget is small and the site is needed now - with a good lightweight theme WordPress can be decently fast. The condition: someone must keep updating it, or in two years it comes back as a patient.
When custom wins
- The site must win customers from Google - speed is a ranking signal and a patience threshold, and the easiest way to be fast is to carry no baggage. My static sites clear Google's threshold with a wide margin.
- Content changes rarely - a service company's site edited three times a year does not need a panel, a database and fifty updates annually.
- You want no obligations - a static site has nothing to update and nothing to hack; the recurring care cost that is real with WordPress disappears.
- You have an unusual process - a quote calculator, a configurator, a client panel. Bending WordPress with plugins can cost more than building it directly - that is custom software territory.
A point-by-point comparison
| Criterion | WordPress | Custom (static) site |
|---|---|---|
| Editing content yourself | yes, a panel for everyone | via the developer or training |
| Typical mobile load time | 2.5-8 s, depending on discipline | under 1.5 s without effort |
| Yearly upkeep cost | hosting + licences + care | practically hosting alone |
| Break-in risk | real without updates | no panel = no target |
| Adding features | plugins: fast, if you stay disciplined | programming: slower, but clean |
The verdict without dogma: frequent editing and a blog - WordPress; speed, peace of mind and unusual needs - custom. Both options are priced in the honest price guide, and if you already have a WordPress that can barely breathe, start with the article on why sites load slowly - a repair may be enough, and no migration needed at all.