The "Next.js or WordPress" question is almost always framed as modern versus outdated. It is really a choice between two spending patterns: WordPress is cheaper to start and gets more expensive every year, Next.js costs more upfront and then asks for very little. Below is the comparison on speed, SEO, security, three-year cost of ownership and editing comfort — plus three situations where WordPress is unambiguously the right call.

Two different ways to spend money on a website

WordPress is a finished system where roughly 80% of the functionality was written by someone else. You pay for assembly: theme, plugins, configuration. Next.js is a framework where you write the front end yourself and pull content from a separate CMS. You pay for manufacturing. The difference is not quality — it is when the invoice arrives and how long it keeps arriving.

Speed and SEO: where the gap is real and where it is folklore

One myth worth killing immediately: Google awards no bonus for your framework. Rankings come from content, links and technical signals. But one of those signals is Core Web Vitals, and that is where architecture starts to affect positions indirectly, through user behaviour.

• The starting point differs. A clean Next.js build serves prebuilt HTML from a CDN in 100–300 ms. WordPress boots PHP, queries MySQL and assembles the page — 400–900 ms to first byte with no cache in front.
• Caching closes most of the gap, not all of it. Full-page caching brings WordPress TTFB down to the same 150–250 ms. What remains is the client side: a theme plus eight plugins ship 400–900 KB of JavaScript, and no cache removes that.
• JavaScript hurts INP, not load time. A page can paint in a second and still feel sticky, taking 300+ ms to respond to a tap, because the main thread is busy with a slider, a page builder and three analytics scripts.
• Images are the biggest lever on both. next/image converts to AVIF/WebP and serves screen-appropriate dimensions automatically. WordPress reaches the same result, but through a dedicated plugin and separate configuration.
• Milliseconds convert into enquiries, not positions. Across our projects, cutting LCP from 3.5 to 1.5 seconds added 10–20% to form conversion and almost nothing to average ranking position.

Three-year cost of ownership

Comparing websites by build price is like comparing cars by showroom sticker while ignoring fuel and servicing. Here is an approximate three-year picture for a 25-page corporate site with forms and two languages.

The conclusion usually surprises people: over three years the totals nearly meet. WordPress wins year one and loses year three, with maintenance and risk eating the gap. Stretch the horizon to five years and the comparison flips entirely. For the wider budget picture, see our breakdown of what a website actually costs.

Security, and what someone has to do every month

WordPress vulnerabilities are almost never in the core, which ships fixes quickly and reliably. The problem is that a typical working site carries 20–30 plugins from different authors, and each is an independent supplier of risk who may simply stop maintaining their code.

On Next.js the list is shorter — no public admin panel, pages served as static output. Not empty, though: dependencies age too, and twice a year someone bumps versions and rebuilds. The difference is planned work measured in hours, not a monthly watch rota.

Who edits the content, and how

This is the strongest argument in WordPress’s favour, and it rarely gets stated honestly. Your editor already knows the interface: they can build a page from blocks, drop in a banner and ask nobody. In a headless setup they see structured fields instead — heading, body, image. Safer, since the layout cannot break, but less freedom.

Technically, content updates in Next.js are handled by incremental regeneration: a page rebuilds on a schedule or on a webhook from the CMS, without rebuilding the whole site.

// app/[slug]/page.tsx
export const revalidate = 3600; // rebuild this page at most once an hour

export async function generateStaticParams() {
  const pages = await cms.getPages();
  return pages.map((page) => ({ slug: page.slug }));
}

The practical read: if someone publishes promotions and campaign pages daily without a developer, WordPress saves you money and friction. If content changes monthly and always fits existing templates, page-builder freedom buys you nothing while its risks stay real.

Choosing in five minutes

Skip the abstract comparison and answer four questions instead. They resolve about 90% of real situations.

1. 1How long will this site live? Under two years — WordPress, because a cheaper start outweighs cost of ownership. Over three — run the full lifecycle numbers.
2. 2Who publishes the content? A non-technical person assembling new pages weekly favours WordPress. Infrequent, template-shaped publishing favours Next.js.
3. 3Is there non-standard logic? Calculators, customer accounts, stock synchronisation, a Telegram bot integration. If yes, Next.js writes it directly while WordPress turns it into a plugin hunt and a fight with someone else’s assumptions.
4. 4How critical is speed? If most traffic is mobile and paid, every 500 ms has a currency value. That makes a fast front end pay for itself within months.

Three situations where we recommend WordPress without hesitation: a publication with several authors posting daily; a site with a constant stream of campaign landing pages the marketer builds alone; and a budget under $1,000, where the real choice is between WordPress and no website at all.

Frequently asked questions

In short

• WordPress is cheaper to start and more expensive to keep; Next.js is the reverse. Over three years the totals usually converge.
• Google does not rank by framework, but Next.js makes strong Core Web Vitals easier — and those move conversion, not position.
• The WordPress risk is not the core, it is plugins: every one you install expands both the attack surface and the monthly maintenance load.
• If a non-technical person publishes daily and needs freedom to assemble pages, choose WordPress.
• If you have non-standard logic, speed-critical traffic or a horizon beyond three years, choose Next.js.