Choosing the technology behind your site: Next.js, WordPress and the rest

It is the most frequent debate in website projects, and it is almost always framed the wrong way. WordPress runs a huge share of the web; Next.js has established itself as the benchmark for fast sites. The question is not which is better in absolute terms — neither is — but which one serves your objective, and at what cost over three years.

The comparison at a glance

Criterion	WordPress	Next.js
Getting started	Very quick	Requires development
Performance	Variable, depends on plugins	Excellent by default
Technical SEO	Good, with plugins	Excellent natively
Security	Frequent target, needs upkeep	Reduced attack surface
Editorial autonomy	High, built-in admin panel	Depends on the integration, via a decoupled CMS
Hosting cost	Server with a database	Often free, static on a delivery network
Scalability	Good	Excellent

This table calls for an immediate qualification: the WordPress “performance” column is not a foregone conclusion. A carefully maintained WordPress site, with few plugins and good hosting, is fast. The problem is that this state is a balance to be maintained, whereas the speed of a static site is a default state. The difference is not one of degree but of nature: one requires discipline, the other requires neglect in order to degrade.

When WordPress is the right choice

More often than our profession cares to admit. If you publish several times a week yourself, if you depend on a specific plugin ecosystem — a proven e-commerce solution, a particular business connector — or if the initial budget has to stay low for a perfectly standard need, WordPress does the job and does it quickly.

The downside is well known and has to be accepted with your eyes open: performance and security depend on the quality and above all the number of plugins installed. A site left without updates for a year becomes slow and vulnerable, and putting it back in order regularly costs more than the maintenance you were trying to avoid.

When a modern architecture becomes necessary

It takes the lead as soon as speed and search visibility are priorities — which is to say almost always, once part of your customers arrive through a search. It also becomes necessary when you are aiming for a rich, interactive experience, when the site is in fact an application with accounts and data, or when you want to bring hosting and maintenance costs down for good.

Paired with a decoupled content manager, this approach offers a perfectly comfortable editing back office: you keep autonomy and performance. That is the point which defuses the myth below.

Compare over three years, not on the quote

This is the comparison that changes decisions, and almost nobody makes it. A quote can be compared in ten seconds; a total cost takes ten minutes and often gives the opposite answer.

Add up four items over three years. Construction, meaning the initial quote. Hosting, which ranges from next to nothing for a static site served by a delivery network to a few hundred euros a year for a server that has to be sized and monitored. Maintenance: plugin updates, security patches, backups, and the time spent checking that an update has not broken anything. And incidents, the item nobody writes down and which always ends up appearing — a plugin abandoned by its author, a breach, an outage on a Friday evening.

Across that total, the initial gap between the two approaches narrows sharply, and reverses as soon as the site becomes a genuine acquisition channel. This is not an argument against WordPress; it is an argument against choosing on entry price alone. The detailed calculation, item by item, is set out in our guide to the price of a website.

Migrating, when the time comes

A migration is not justified by the age of the technology but by a specific symptom: speed scores that will not come back up despite optimisation, repeated security incidents, a maintenance bill that exceeds the value produced, or a functional need — customer area, dashboard, application — that the current foundations cannot carry.

Once it is decided, the order of operations matters more than the tooling. You start by taking an inventory of existing addresses and their actual traffic, which reveals that a large share of the pages receive nobody. You decide explicitly what to keep, what to merge and what to remove — the most profitable moment of the whole project. You preserve the addresses of the pages that matter, or set up permanent redirects one by one. Then you rebuild, check page by page, and monitor errors over the following weeks.

The classic mistake is to switch over in one go, hoping that automatic redirects will be enough. They never are, and the loss of visibility that follows takes months to recover — for a mapping exercise that would have taken two days.

The myth of “WordPress is easy, everything else is complicated”

For the person writing an article or changing a price, a well-designed modern site with a decoupled back office is just as simple to update as a WordPress one. The fields are there, so is the preview, and publishing is immediate.

The complexity exists, but it sits on the design side, not the usage side. In other words, it is paid once by the provider instead of being paid every month by you, in maintenance and in slowness. It is a shift in where the cost falls, and those are the terms in which it should be compared.

Choosing in four questions

Are search visibility and speed critical to your acquisition? If so, the modern architecture. Do you need to edit content yourself every day? Then WordPress, or a modern architecture with a decoupled CMS — not a modern architecture without a back office. Are you aiming for a genuine application, with accounts, data and personalised areas? Then a modern architecture, without hesitation. Is the budget very tight for a standard need? Then WordPress may well be enough, and saying so is more honest than selling the opposite.

At HelyOs Global we build mainly in Next.js — this site illustrates it, and the detailed comparison gives the figures. But the right choice remains the one that serves your objective, and we do sometimes recommend the other.

Assessing a fashionable technology: the case of Web3

The same decision method applies to the technologies people talk about. Take Web3, which has had its peak of enthusiasm and its comedown: once past the noise, a handful of uses create real value and many create none at all.

In one sentence, Web3 describes a web in which users genuinely own digital assets and identities, without depending on an intermediary to hold them. The uses that stand up all follow from that ownership: loyalty schemes whose points genuinely belong to the customer and are transferable; proof of a product's origin, in luxury goods, art or food; ticketing that nobody can duplicate; taking payment in cryptocurrencies from an international clientele; access reserved for a community.

The failures, for their part, all look alike. Doing Web3 for its own sake, with no identifiable benefit for the customer. Imposing technical complexity on users who asked for nothing of the sort. Overlooking the regulatory and tax framework, which is not optional.

The assessment grid comes down to four moves, and it holds for any new technology. Identify the problem: this one solves questions of ownership, authenticity or intermediaries — if you have none of those, it brings nothing. Check the gain for the customer, tangible and expressible in one sentence, otherwise adoption will not follow. Aim for an invisible experience: successful projects hide the machinery, and the customer enjoys the benefit without knowing what lies underneath. And start small, on one segment, measuring adoption before extending.

The question to ask is never “how do we do X?” but “is this problem better solved with X than otherwise?”. Often not; sometimes yes, and then the advantage is real. That is exactly the logic guiding our AI agents, designed for a specific business problem rather than to follow a trend.

What to take away

There is no absolute winner, only a good choice in context — and the best indicator of a provider's seriousness is their ability to point you towards the solution they do not sell.

Going further

Our websites division sets out the formats we build and the technology chosen for each. The comparison puts our approach up against the market alternatives, the pricing gives the cost of each package, and the demos show the result in action. Describe your project to us in a few lines: we will point you in the right direction honestly, including when the answer is “you do not need us”.