Available worldwide
Posts

WordPress or Next.js for a business website? How I decide

November 16, 2026
For a business website, choose WordPress when several people will publish content every week, you want to change pages and layouts without calling a developer, and the site is mostly content: pages, posts, galleries, maybe a WooCommerce shop. Choose Next.js when speed, a design that no theme can produce, or integration with your own systems is what makes the site worth having, and you are comfortable with a developer owning the code while editors work in a focused CMS. Neither is the modern choice or the safe choice; they are different tools, and the right one depends on who maintains the site after launch and what it has to do. I build on both. Most of my work is Next.js and React, and I still pick WordPress for some projects on purpose; the photography studio I run with my wife runs on it, for reasons I will get to. What follows are the criteria I actually use in an intake, written down so you can run them on your own project first. WordPress is a PHP application with a database, an admin panel, themes and tens of thousands of plugins, and it runs roughly four in ten websites. In 2026 editing happens in the block editor, in a page builder like Elementor or Bricks, or in a block theme with full site editing. It is a product: you install, configure and extend it. Next.js is a React framework, not a content system. It gives a developer routing, server rendering, static generation, image optimisation and code splitting, and it gives an editor nothing at all. Content comes from somewhere else: MDX files in the repository, or a headless CMS such as Sanity, Payload, Contentful or Storyblok. WordPress itself can play that role through its REST API or WPGraphQL, the headless setup. So the honest comparison is a configured product with a theme and plugins versus a toolkit, a CMS and a developer. Seen that way, most of the criteria below fall into place. This is the criterion most people underweight, and it decides most projects. WordPress wins on familiarity and freedom. Almost everyone has used the admin. An editor can add a page, swap a hero image, publish a post and upload photos from a phone without asking anyone, and a page builder lets a non-developer build a whole landing page on a Tuesday afternoon. That freedom is also how WordPress sites drift: four heading styles, a plugin for everything, and a homepage that looks nothing like the one that was designed. That trade was worth it for KAV Studio. My wife publishes a new gallery the day after a shoot, from her phone, with no build step and nobody in the loop. In Next.js, every new session would have gone through me and a deploy, exactly the wrong bottleneck for a working studio. Next.js has no editing experience of its own; it has whatever you put in front of it. MDX in git is fine for a developer and hostile to a marketing manager. A headless CMS, done well, is a calm editing screen with only the fields that exist, draft previews through the real site, and no way to break the layout because the layout is not editable. That is a feature for consistency and a limitation for freedom: any structural change, a new page type or section design, needs a developer. The rule I use: if more than one or two people publish weekly and want to arrange pages themselves, WordPress. If content changes monthly, is structured, and brand consistency matters more than freedom, Next.js with a CMS is the calmer option. Google measures three things on real visitors: Largest Contentful Paint, which should stay under two and a half seconds; Interaction to Next Paint, under two hundred milliseconds; and Cumulative Layout Shift, under one tenth. Both stacks can pass; the difference is how much room for error you get. Next.js is fast by default: static or server-generated HTML, JavaScript split per route, images resized and converted automatically, fonts self-hosted. But fast by default is not fast by guarantee. A Next.js site with a client bundle the size of a small app, three animation libraries and a dozen tracking tags fails the same thresholds as a bloated WordPress site. WordPress can be fast with discipline: a lean theme, few plugins, a caching layer and a good host. The problem is accumulation. Each plugin loads its own stylesheet and script on every page, the page builder outputs heavy markup, and the site gets a little slower every year. Fixing a four-year-old WordPress site usually means removing things people depend on, which is a harder conversation than the technical work. QMP Cars shows the Next.js side of the argument. A used-car storefront with a full-screen video hero and large photo galleries is not an easy site to keep fast, yet the inventory is filtered and rendered on the server and the dealer manages listings in a Supabase admin. The same brief on WordPress would have meant a car-listing plugin, a gallery plugin and an uphill fight. If speed is a sales argument, because customers arrive on mobile data, you pay for ads or you compete on search, Next.js gives you a bigger margin. If it only needs to be adequate, WordPress with restraint is fine. WordPress core is maintained seriously and minor releases update themselves. Compromised WordPress sites are overwhelmingly the result of outdated plugins and themes, abandoned extensions and weak credentials. The defence is routine: weekly plugin updates, backups and a staging copy to test on, done by you or by a managed host. The work is not technical, but it is relentless, and the sites that get hacked are the ones where nobody owned the chore. Next.js removes the plugin attack surface, and a fully static site has almost no server to attack. That is not zero maintenance. The project depends on npm packages, the framework ships major versions, and Next.js has had serious advisories of its own, including a middleware authorisation bypass in 2025. The difference is rhythm: a dependency sweep a few times a year, a framework upgrade when a major version lands, and a prompt patch on the rare day an advisory like that one appears, all done by a developer, instead of weekly clicks anyone can do. So the question is not which one is more secure but which kind of upkeep your business will actually do: frequent and non-technical, or infrequent and technical. Pick the one that will not be neglected. With WordPress you add features by installing them: forms, SEO metadata, bookings, multilingual content, a shop through WooCommerce. Mature plugins are standard, supported and fast to set up, and for a brochure site or a standard shop they are the quickest path. Each one is also a dependency with its own update cycle, licence renewal and performance footprint, and the feature is what the plugin author imagined, not what your business needs. The moment a plugin needs serious customisation, you are writing PHP inside somebody else's product. With Next.js, features are built. A quote flow, a client portal, a booking calendar tied to your own backend: code you own that does exactly what you asked. Libraries exist for everything, but they are building blocks rather than installable features, and each feature costs developer time to build and to change later. Integrations with a CRM, a payment provider or an internal API are natural, because the whole site is already code. My rule: if what you need matches what mature plugins do well, WordPress gets you there fastest. If the site has to do something specific to how your business sells, custom code ends up cheaper than bending five plugins into shape. WordPress needs PHP and a database running somewhere. Cheap shared hosting exists and is where most slow, hacked sites live; managed WordPress hosting with backups, staging and a CDN is the sensible choice, at a monthly fee that scales with traffic. Next.js runs naturally on Vercel, which built it, and fine on Netlify, Cloudflare or a server you control. A static Next.js site can be served from almost anywhere for very little, with one caveat: the free tiers of those platforms are meant for personal projects, so a business site belongs on a paid plan or its own small server. Over a few years the money lands in different places. A WordPress site is usually cheaper to build when the needs are standard, then costs hosting, plugin licences and maintenance hours every year, with a real chance of a full rebuild once it becomes unmanageable. A Next.js site costs more to build because more is built, then costs less to host and to keep secure, with every change passing through a developer. The figures depend on scope, but that is the shape of the trade. WordPress is the better fit when:
  • Several people publish often and want to arrange pages themselves.
  • The needs are standard: a blog, a brochure site, a portfolio, a shop with a normal checkout.
  • Nobody technical is on call, and a managed host or maintenance plan will handle updates.
  • The team already knows the admin.
Next.js is the better fit when:
  • Speed and a distinctive design are part of how the business sells.
  • The site has to integrate with your own systems or do something no plugin does.
  • Content changes are structured and infrequent, and editors are happy with a focused CMS.
  • A developer owns the code, now and in two years.
Headless WordPress behind a Next.js front end exists for when both are true: a large editorial team that insists on WordPress and a front end that must be fast and fully custom. It is two systems to maintain and costs accordingly: rarely worth it for a ten-page business site, often worth it for a publication with daily output. For my own clients this decision happens in the intake, before any design, and it feeds into the fixed project price. Most of my builds end up on Next.js. Some end up on WordPress because that is what the people running the site will keep accurate, and an accurate site beats a faster one that quietly goes stale. If you are weighing the two for your own business, the custom website design and development page explains how I work, and you can send me a few lines about your project. Which stack fits is part of the first conversation, whether or not we end up working together.

Custom website design

Tell me in a few lines what your business does and what you want to achieve. You get a reply within two working days with an honest assessment and a proposal for a 30-minute intake.

Get a proposal