React 19 went stable in early December, and the developer corner of the internet has been busy with it. Actions, the use hook, better support for server components, and form handling that finally feels native. If you build web applications, it's a good release.
But here's a conversation we have often with clients: someone on their team has heard that "modern websites are built in React" and wants their new company website built that way. Sometimes that's right. Often it isn't.
What React is good at
React shines when a page has lots of interactive state. Think dashboards, booking systems with live availability, product configurators, chat interfaces, admin panels. Anything where the screen changes constantly based on what the user does.
React 19 makes that work smoother. Actions let you handle form submissions, pending states and errors without the usual pile of useState calls. Server components let you render more on the server and ship less JavaScript to the browser.
What most business websites actually are
Most company websites are documents. A home page, services, about, case studies, a blog, a contact form. Content changes when someone edits it, not every second.
For that kind of site, server-rendered HTML with a little JavaScript where needed is usually faster, cheaper to build, and easier to maintain. There's no build pipeline to keep updated, no hydration step, and pages work even if a script fails to load.
Search engines can handle JavaScript-rendered pages these days, but plain HTML is still the most reliable thing you can give a crawler.
The hidden costs
Choosing a JavaScript framework for a simple site brings a few costs that don't show up in the first quote:
- Maintenance. The JavaScript ecosystem moves quickly. A project left alone for two years can be painful to update.
- Hosting. Some setups need a Node server or a specific platform, rather than the standard PHP hosting most Indian businesses already pay for.
- Hiring. Simple content edits may need a developer instead of whoever manages your site.
When we do use React on content sites
We're not anti-React. We use it in pieces where it helps. A quote calculator on a services page, an interactive map, a filterable product catalogue. These "islands" of interactivity sit inside an otherwise ordinary page. It's a good middle ground: fast pages, rich features where they matter.
A simple rule of thumb
If you can describe your website as "pages people read", start with server-rendered HTML. If you describe it as "a tool people use", React (or something like it) is likely worth the complexity.
React 19 is a good reason for app developers to be excited. It isn't, on its own, a reason to rebuild a brochure site.
