We get this question in almost every discovery call: "Should we build on WordPress or on Next.js?" The honest answer is that both are excellent – for different situations. Here's how we decide.
What each one actually is
WordPress is a content management system. It gives your team an editor, a media library, user roles and a huge plugin ecosystem. With a custom theme it can be fast and secure; with a page builder and 40 plugins it usually isn't.
Next.js is a React framework. It's not a CMS – it's a way of building websites and web applications with full control over performance, interactivity and integrations. Content typically lives in a headless CMS (Sanity, Contentful, Storyblok, or even WordPress itself) and is delivered through an API.
When WordPress is the right call
- Your marketing team publishes daily. The editing experience is mature and familiar.
- The website is mostly content: pages, posts, landing pages, a blog, maybe a small shop.
- Budget is limited and speed to launch matters. A custom WordPress theme can be live in two to four weeks.
- You need a broad plugin ecosystem – events, memberships, multilingual, forms – without custom development.
A well-built WordPress site (custom blocks, no page builder, tuned hosting) scores 90+ on Lighthouse and stays secure with a maintenance plan. Most of the horror stories come from neglected installations, not from WordPress itself.
When Next.js is the right call
- Performance is a competitive advantage – e-commerce, high-traffic media, anything where milliseconds change conversion rates.
- The site is really an application: dashboards, configurators, portals, personalised experiences.
- You're integrating many systems (CRM, PIM, ERP, search, payments) and want one clean front-end.
- You expect the product to grow into something WordPress plugins can't model.
Next.js gives you server rendering for SEO, streaming for speed, and a component model that keeps large sites consistent. The trade-off: you need developers to change more than content, and the editing experience depends on the CMS you pair it with.
The hybrid: headless WordPress
Increasingly we build WordPress as the editor, Next.js as the front-end. Editors keep the tool they know; visitors get a fast React site; developers get a clean separation. It costs more than a plain theme, so it's worth it when performance or design freedom really matters.
A quick decision table
| Situation | Our recommendation |
|---|---|
| Small business website, 5–15 pages | WordPress (custom theme) |
| Corporate site, multilingual, frequent edits | WordPress or headless WordPress |
| D2C store with strong brand | Shopify + Next.js (headless) or Shopify theme |
| SaaS marketing site + app | Next.js |
| Customer portal / dashboard | Next.js + Django |
| Content-heavy site with big traffic | Headless CMS + Next.js |
What we'd never recommend
- A page builder on WordPress "because it's faster to build". You pay for it in performance and maintenance for years.
- Next.js for a five-page site with a team that just wants to edit text. Over-engineering has a cost too.
Bottom line
Choose based on who edits, what the site must do, and where it's going. If you're unsure, a one-hour technical consultation is usually enough to settle it – and we'll tell you if the answer is the cheaper option.
