This is a technical decision with a business consequence, so it's worth understanding even if you don't write code. The difference between a plain React app and Next.js is felt most in one place: whether Google sees your content, and how quickly a visitor sees it.
The difference in one sentence
Plain React assembles the page in the visitor's browser: an almost empty document arrives, along with JavaScript that fills it in.
Next.js can assemble the page in advance, on the server, and send finished HTML.
Everything else follows from that difference.
Why it matters for visibility
A search engine arriving at a React app sees an empty document on the first pass. Google today runs JavaScript and usually gets to the content, but on a second pass and with a delay.
For a site that lives on search, that's an unnecessary risk. For systems that assemble AI answers the risk is bigger: some of them don't run JavaScript at all.
With Next.js the content is in the HTML that arrives from the server. No guessing.
Why it matters for the visitor
An empty document means the visitor stares at white until the JavaScript is downloaded and run. On a good connection you don't notice; on a phone with weak signal it's seconds.
Finished HTML shows straight away. The effect on speed measures is described in Core Web Vitals for business owners.
When plain React makes sense
It's not that it never does:
- An app behind a login. An internal tool, an admin, a dashboard: content a search engine isn't supposed to see anyway.
- Highly interactive interfaces where everything happens after login.
- Something embedded in an existing site.
For internal tools plain React is often completely fine, because search visibility isn't the goal there.
When Next.js wins
- A business website, always.
- An online shop.
- A blog and content that has to be found.
- Several languages, because routing by language is built in.
- Anything shared on social media, because a link preview needs tags in the HTML.
What else Next.js brings
- Image optimisation: modern formats and sizes per device, with no manual work.
- Routing by language with correct addresses.
- A server side for forms and data without a separate system.
- Built-in code splitting, so not everything is sent at once.
In practice, part of the work that would otherwise be assembled by hand comes in the package.
What the client actually cares about
The name of the tool doesn't need to be in the quote. What should be checkable is the consequence:
Is the content visible without JavaScript? Open the developer's site, turn off JavaScript in the browser and refresh. If it stays empty, it's a plain React app.
What's the mobile score? Run their projects through PageSpeed Insights.
Do their projects rank? Search for the client's name and the service they offer.
Those are three checks that take five minutes and say more than any list of technologies.
Frequently asked questions
Is Next.js more expensive to build?
Not significantly. For a business site it's often faster, because part of the work comes built in.
Is it more expensive to run?
No. Static pages are served for free at a small business's traffic.
Can an existing React site be moved over?
It can, and that's a common job. The scope depends on how it was written.
Are there other options?
Yes: Astro is excellent for sites that are mostly content. The decision depends on how much interactivity you really need.
How I do it
I build business websites and shops in Next.js, and internal tools depending on the case. The decision is explained at the start, because it affects how the site will behave for years.
Tell me what you're building or see my work.