Coded site or WordPress? The difference no one tells you

When you ask for a site, nine times out of ten you're offered WordPress. It's no accident: according to W3Techs (2025) WordPress powers about 43% of all websites in the world, and over half of sites built with a CMS. It's the de facto standard. But "the most widespread" doesn't mean "the best for you": it means "the easiest to resell". Let's look at the real difference, no tribalism.

What they are, in plain words

A WordPress site is like a prefab house: you start from a ready-made structure and bolt themes and plugins on top (ready-made pieces written by others) to add features. Quick to put up, but you carry all the weight and constraints of the prefab, even the rooms you'll never use.

A coded site is like a house built to measure: you write only what's needed, exactly as needed. It takes more craft up front, but the result is light, tailored and free of useless pieces that slow things down and can break.

1. Speed

This is where it shows most. A typical WordPress site loads dozens of components, plugins and libraries on every visit, even when they're not needed. A coded site sends the browser only the bare essentials. Result: it starts faster, especially on phones and slow connections — and that's exactly where first impressions and Google ranking (Core Web Vitals) are decided.

2. Security

Precisely because it's everywhere, WordPress is the number-one target. In Sucuri's 2023 report (a firm that cleans up compromised sites) WordPress accounted for 95.5% of the infected sites analysed. Read it honestly: it doesn't mean WordPress is badly made, but that it's the most widespread and that the weak point is almost always plugins and updates not done — in the same report, about 39% of the hit sites had an out-of-date CMS at the time of the attack.

Translated: every plugin you add is one more door someone else built and that you have to keep updated. A coded site has far less attack surface, simply because there are far fewer third-party pieces to watch over.

3. Cost and maintenance over time

WordPress costs little up front and more later: paid plugin licences, updates that occasionally break something, maintenance to keep everything secure. A coded site costs a bit more to build, but it's more stable and lighter over the years — fewer pieces that break means fewer emergency calls.

• WordPress: quick and cheap start, but costs and maintenance that grow over time and with plugins.
• Coded: a slightly higher initial investment, but better performance, security and stability in the long run.
• The right question isn't "how much does it cost to build", but "how much does it cost me to own it for the next 3-4 years".

When WordPress is perfectly fine (I'll say it myself)

I'm not a code purist. WordPress is a great choice in some cases: a very frequently updated blog managed in-house, a project with a small initial budget, or when the company already has someone who can administer it. If those conditions are there, I'll tell you so myself.

The right tool is the one that's right for you, not the one that suits whoever's selling it. If WordPress is the sensible choice, I'll be the first to recommend it.

What I choose, and why

For a showcase site that has to be fast, secure and bring in customers — the need of most businesses — I start from code (Next.js and React). I get sites that load in under a second, with very little attack surface and no plugins to chase. For those who genuinely need to manage a lot of content in-house, I weigh the right solutions case by case.

If you don't know what's under your current site or what you really need, on a free call we'll look at it together and I'll tell you, no beating around the bush, the sensible choice for your situation.