DEV Community

Jay Malhotra
Jay Malhotra

Posted on Originally published at jaymalhotra.in on

WordPress vs Next.js for a business website: how to actually choose

“Should we build on WordPress or Next.js?” is one of the most common questions I get from clients. Both are excellent. Both are also the wrong answer for some projects. Here is how I think about the decision after years of shipping sites on each.

The short answer

  • Choose WordPress when non-technical people will publish content often, you need a mature plugin ecosystem (forms, SEO, WooCommerce, memberships), and budget matters.
  • Choose Next.js when the site behaves more like an application — dashboards, logins, custom data, heavy interactivity — or when you need top-tier performance at scale and have developers to maintain it.
  • Consider both (headless WordPress + Next.js front end) when you want WordPress editing with a fully custom, very fast front end — and can afford the extra complexity.

1. Who edits the site?

This is the question that decides most projects. WordPress gives editors a familiar admin, a visual block editor, revisions, roles and scheduling out of the box. With a Next.js site, content usually lives in a headless CMS (Sanity, Contentful, Strapi or headless WordPress) — powerful, but it is another system to set up and pay for.

If your marketing team publishes weekly and doesn't want to call a developer for every landing page, WordPress is hard to beat.

2. Performance

Next.js has an edge out of the box: static generation, image optimisation, code-splitting and edge rendering are built in. But a well-built WordPress site — lean theme, no page-builder bloat, proper caching and a CDN — comfortably passes Core Web Vitals too. Most slow WordPress sites are slow because of heavy themes and too many plugins, not because of WordPress itself.

3. SEO

Both can rank equally well. WordPress makes on-page SEO easy for editors with plugins like Yoast or Rank Math. Next.js gives developers fine-grained control over metadata, structured data and rendering. What matters far more than the framework: content quality, internal linking, page speed and backlinks.

4. Cost — build and ongoing

  • Build: a marketing site on WordPress is usually faster and cheaper to deliver, because so much exists already (forms, SEO, caching, eCommerce).
  • Hosting: both can be inexpensive. Next.js runs well on Vercel, Netlify or Cloudflare; WordPress needs PHP hosting with good caching.
  • Maintenance: WordPress needs regular core, theme and plugin updates and security hardening. Next.js has fewer moving parts in production, but changes nearly always need a developer.

5. eCommerce

For most small and mid-sized stores, WooCommerce (WordPress) or Shopify is the pragmatic choice — payments, tax, shipping and inventory are solved problems. A custom Next.js storefront makes sense for brands with unusual product logic or very high traffic, usually on top of Shopify or another commerce API.

6. Custom features and integrations

If the project involves user accounts, dashboards, complex forms, third-party APIs or AI features, Next.js (often with a Laravel or Node back end) gives you a cleaner foundation. WordPress can do a lot of this with custom plugins, but past a certain point you are fighting the platform.

A quick decision checklist

  1. Will non-developers publish or edit content every week? → lean WordPress.
  2. Is it primarily a marketing or content site? → lean WordPress.
  3. Does it need logins, dashboards or app-like interactivity? → lean Next.js.
  4. Is raw performance at scale a business requirement? → lean Next.js (or headless).
  5. Do you have ongoing developer support? → if not, WordPress is easier to own.

My take

Pick the platform that fits how your team works and where the product is going — not the one that is trending. I build on both, and I'm happy to recommend against the more expensive option when it isn't needed. If you're weighing this decision for your own project, tell me what you're building and I'll give you a straight answer.

Originally published at jaymalhotra.in.

Top comments (0)