WordPress or React: how to choose for your site
This is a question developers enjoy and clients rarely benefit from. The decision almost never turns on which technology is better, but on who will maintain the content.
If you have been looking for someone to build your site, you have probably had contradictory advice. One says WordPress because it is simple, another says WordPress is slow and offers something modern. Both can be right, because they are answering different questions. Here is how I make the call, and which question actually settles it.
The question is not which technology is better
Both WordPress and React can produce a fast, tidy, well-ranked site, and both can produce a slow, unmaintainable one. The technology sets an upper bound; the execution determines the result. I have seen WordPress sites that load in a second and React applications that barely function on a phone.
So the first question is never technical. I ask who will change the content, how often, and how much that person is willing to learn. The answer usually resolves ninety percent of the dilemma before any tool gets mentioned.
When WordPress makes sense
WordPress is the answer when the content is alive. If you change prices by season, add properties, publish news, or want to swap photographs yourself without emailing a developer, you need an editing system, and WordPress is the most widespread one in Croatia. That also means it is easier to find somebody who knows it if our paths diverge.
The price of that flexibility is maintenance. WordPress and its plugins need regular updates, and every plugin is something that can break or slow the site down. That is not a reason to avoid it, but it is a line item to plan for: an installation nobody has updated in two years is a security problem, not just technical debt.
When React makes sense
React makes sense when the site does something specific that off-the-shelf systems handle badly, or when speed and interface behaviour are part of the product. Calculators, configurators, interactive displays, applications with their own logic. It also makes sense when the content barely changes, because then there is no reason to pay for and maintain an entire CMS layer.
What often goes unsaid is that a React site is not automatically good for search engines without extra work. If content is drawn only in the browser, some of the tools that read the page will see nothing. There is a solution, called prerendering or server-side rendering, but it is work somebody has to do. If you are offered a React site, ask how that part is handled.
The mistake made most often
The most expensive mistake is choosing the technology before knowing who maintains the content. That is where React sites come from whose owner cannot change a phone number without an invoice, and WordPress installs with fifteen plugins on a site that has not changed since launch.
The second common mistake is choosing by novelty. Technology that was popular five years ago is often a burden today, and what is popular now will be in the same position in five years. A more useful question than "is this modern" is "will somebody be able to take this over in three years".
Cost over time, not just at the start
The initial price is the visible part. What gets calculated less often is the cost across several years: hosting, updates, small changes, and the time you spend maintaining it yourself. WordPress usually has a lower entry price and higher maintenance. A static or React build usually has the opposite profile.
So I ask how long the site needs to last. For a site that is an advertisement for one season and a site that underpins the business for the next five years, the answer is not the same, even when they look almost identical.
Five questions that decide it for you
- Who will change the content, and how often
- Does the site do anything beyond displaying information
- How much are you willing to spend on maintenance each year
- Does the site need to exist in several languages
- How long do you expect this version of the site to last
The answer in one sentence
If you change the content yourself and often, take WordPress and budget for maintenance. If the content rarely changes or the site does something specific, a static or React build gives you a faster and quieter result. If you are not sure, that is a sign the conversation needs to be about content first, not technology.