It is one of the first questions for a new website: build on WordPress, which everyone knows, or go with custom code in Next.js? The answer depends on whether the site is a business card or a sales tool.
WordPress: when it makes sense
WordPress works when you need a simple site you will update yourself, you have a limited budget and you do not need maximum speed. It is a mature CMS with a huge plugin ecosystem.
The trouble begins at scale: every plugin is extra code, a security risk and a slowdown. The site "grows over" and gradually loads slower.
Next.js: when it is worth it
- Speed. Statically rendered pages served from the edge load under a second. That genuinely affects Google rankings and conversion.
- Security. No admin panel and no plugins means a smaller attack surface.
- Control. The site does exactly what you design, without someone else's engine compromises.
The difference shows in the numbers. We explain why speed translates into sales in Core Web Vitals and sales.
Maintenance cost, not just build cost
WordPress can be cheaper at the start but pricier to maintain: updates, premium plugins, security patching. Next.js costs more upfront but needs almost no technical maintenance.
How to decide in 30 seconds
- Simple business card, small budget, self-editing - WordPress.
- The site must be fast, secure and sell to premium clients - Next.js.
The myth: "WordPress is free"
WordPress itself is free, but a site built on it is not. The real cost is hosting, a premium theme, paid plugins (forms, SEO, backups, optimisation), plus time spent on updates and security patching. After two or three years a "cheap" site can cost more than a custom one, because you pay in small instalments forever. It is the same logic we lay out in How much does a website cost: what counts is the total cost of ownership, not the starting price.
Next.js flips the ratio: you pay more upfront, but the site needs almost no maintenance - there is no admin panel to hack and no plugins to update.
SEO and speed: where Next.js wins
Google has rewarded fast sites for years, and Core Web Vitals is a genuine ranking factor. A plugin-laden WordPress loads slower with every addition; Next.js renders statically and serves from the edge, so it starts in under a second. For a business fighting for rankings and conversion, that is not cosmetics - it is money. We show why speed translates into sales in Core Web Vitals and sales. Both engines can be SEO-correct, but with Next.js you have full control over structure, structured data and speed - without fighting someone else's theme.
Frequently asked questions
Can I edit content myself on Next.js? Yes. You edit content and posts in a panel (CMS), just like on WordPress - the difference is under the hood, not in daily use.
Is WordPress bad? No - it is a mature tool for simple sites and blogs you update yourself. The trouble shows at scale, with performance requirements and security.
What about an online store? That is a separate topic - we break it down in How much does an online store cost, comparing hosted platforms with custom headless.
We lay out the full cost and trade-off comparison in WordPress or custom code.