Tech
React vs Next.js: which one does your website need?

Zeeshan Sangi
· 6 min read

When I tell clients I build websites with React and Next.js, a common follow-up question is: are they not the same thing? It is a fair question. The two names appear together in almost every job advert and developer profile, and from the outside it is not obvious where one ends and the other begins.
The difference matters more than it sounds. It affects how fast your website loads, how easily Google can read it, and how much work it takes to build and maintain. In this article I will explain what each one is, how they work together, and how to decide what your project actually needs.
What React is
React is a JavaScript library for building user interfaces. It was created at Facebook (now Meta) and is now one of the most widely used tools for building websites and web apps. React lets a developer build a page out of small, reusable pieces called components: a navigation bar, a pricing card, a contact form. Each piece knows how to display itself and how to react when something changes, such as a button being clicked.
What React does not do on its own is decide how your whole website is put together. It does not handle page addresses, it does not prepare pages for search engines, and it does not optimise your images. Those jobs are left to whatever you build around it.
What Next.js is
Next.js is a framework built on top of React, made by the company Vercel. It uses React for all the visual parts of a site, then adds the things a real website needs: a page for every address, pages prepared on the server or in advance, automatic image optimisation, and tools for setting page titles and descriptions for search engines.
A useful way to picture it: React gives you excellent building blocks. Next.js gives you the building plan, the foundations and the plumbing, so the blocks become a complete house. You still use React with Next.js. You are simply using it inside a framework that handles the rest.
The React team itself now recommends starting new projects with a framework such as Next.js rather than plain React, because most real websites need these extra features sooner or later. In February 2025 it also retired Create React App, the old starter tool for plain React projects.
The big difference: who builds the page
With a plain React site, the server usually sends a nearly empty page plus a bundle of JavaScript. The visitor's browser then runs that code to build the page. On a fast laptop this feels fine. On an older phone or a slow connection, visitors can stare at a blank screen while the code downloads and runs.
With Next.js, pages can be built on the server, or prepared in advance when the site is published, and sent to the browser as finished HTML. The visitor sees the content almost immediately, and React then takes over in the background to make the page interactive. For a business website, where first impressions and speed matter, this is a significant advantage.
What this means for SEO
Search engines are much better at reading JavaScript than they used to be, but a page that arrives as finished HTML is still the safest option. Google can read your headings, text and links straight away without waiting for code to run.
Next.js also makes the other SEO basics straightforward: a unique title and description for every page, clean page addresses such as /services/web-development, a sitemap, and preview images for when your pages are shared on social media. With plain React, each of these has to be added and maintained by hand.
If people find your business through Google, and most local businesses do, this alone is a strong reason to choose Next.js for a public website.
Speed and images
Photos are usually the heaviest part of a small business website. Next.js includes an image component that can resize images, serve modern formats and load them only when they are about to appear on screen. With plain React, a developer has to set this up separately, and it is easy to forget.
Next.js also splits your code by page automatically. A visitor reading your homepage does not download the code for your booking form until they visit the booking page. The result is a lighter first load, which is exactly what visitors on phones need.
When plain React still makes sense
Next.js is not the answer to everything. Plain React, usually set up with a fast tool called Vite, is a good choice in some situations.
- +Internal tools and dashboards that sit behind a login, where search engines never need to read the pages.
- +Apps that are mostly interactive, such as editors or calculators, where there is little text to index.
- +Small widgets added to an existing website, such as a quote calculator or a booking form.
When to choose Next.js
For most public-facing business websites, I recommend Next.js. It is the better fit when:
- +You want to be found on Google for your services and location.
- +Your visitors mostly arrive on phones and expect pages to load instantly.
- +You have several pages, such as services, projects, a blog and contact.
- +You may want to add features later, like bookings, a client area or an AI assistant.
Does Next.js cost more?
Not really. Because Next.js already includes routing, image handling and SEO tools, a developer spends less time building those from scratch. For a typical small business website, building with Next.js is often quicker than building the same site with plain React and adding everything by hand.
Hosting is affordable too. A Next.js site that is mostly prepared in advance can be hosted on modern platforms such as Vercel or Firebase at a very low cost for small business traffic. Whoever builds your site, make sure the domain, hosting and code are in your name, so you stay in control.
Common myths
A few ideas come up again and again when clients compare the two. Most of them are not quite right.
- +Next.js is a different language. It is not. Next.js is written in the same JavaScript and React, so any React developer can work on a Next.js site.
- +Next.js is only for big companies. Large companies do use it, but it works just as well for a five-page website for a local business.
- +React sites cannot rank on Google. They can, but plain React needs extra care. Next.js removes most of that risk by sending finished pages.
- +You need a server running all the time. Many Next.js sites are prepared in advance and served as simple files, which is cheap and very reliable.
Questions to ask before you start
If you are hiring someone to build your website, a few simple questions will tell you whether they have thought about these choices or are simply using what they always use.
- +Will my pages be sent as finished HTML, so Google can read them straight away?
- +How will images be optimised for visitors on phones?
- +Will each page have its own title and description for search results?
- +Where will the site be hosted, and who will own the account?
- +How easy will it be to add new pages or features next year?
An example from my own work
Take an accountancy website like the one I built for Tyson Roselyn, an online accountancy firm for UK small businesses. Most visitors arrive from Google, often on a phone, looking for help with a specific task such as a tax return or company formation. They want to understand the service quickly and book a consultation.
For a site like this, Next.js is the natural fit. Each service has its own page with its own title and description, so it can appear in search results for the right questions. Pages are prepared in advance, so they open quickly even on a slow connection. The consultation button is visible straight away instead of waiting for code to load. None of this would be impossible with plain React, but Next.js provides it out of the box, which means less time spent on setup and more time spent on the content and design that win clients.
How I use them together
Every business website I build uses React for the components and Next.js for everything around them. Pages are prepared in advance where possible so they load quickly, each page gets its own title and description for Google, and images are optimised automatically. For features that need live data, such as a contact form that saves messages to a database, Next.js lets me add them without slowing the rest of the site down.
The short version: React is the engine, and Next.js is the complete car. For a website that needs to be fast, easy to find on Google and ready to grow, Next.js is the right starting point. If you are not sure what your project needs, tell me what you want your website to do and I will recommend the simplest option that gets you there.
Sources

