Next.js or WordPress for a Malaysian small-business website?

WordPress powers roughly two in five websites on the internet, so it is the default answer most people reach for. Default is not the same as correct. For a Malaysian small business launching or rebuilding a brochure-and-leads website in 2026, the right question is not "which is more popular" but "which one costs me less over three years and brings in more enquiries." I build on Next.js, and below is the honest case for and against each, so you can decide before anyone quotes you.

What each one actually is

WordPress is a content management system. You get an admin dashboard, a theme that controls the look, and plugins that bolt on features. It is mature, flexible, and almost every freelancer in KL knows it.

Next.js is a modern web framework. A site built on it is compiled into fast, mostly static pages and deployed to a global edge network. There is no plugin marketplace and no theme bazaar. The tradeoff is that more of the build is bespoke, and fewer people can hand it off cheaply.

Speed, and why it is not a vanity metric

Google ranks on Core Web Vitals, and Malaysian buyers browse on mobile data far more than on office wifi. A typical WordPress site loads a theme framework, a page builder, and a stack of plugins on every request, then queries a database to assemble the page. A Next.js site ships a pre-built page from a server close to the visitor.

The practical result is that a clean Next.js build routinely loads in under two seconds on 4G, while a plugin-heavy WordPress site often takes four to eight. That gap is the difference between a visitor reading your offer and a visitor bouncing back to Google. If you want the detail on why this matters for lead flow, I wrote about it in why your KL website gets no leads.

Security and maintenance: the part nobody quotes for

This is where the real cost lives. WordPress's popularity makes it the most-attacked platform on the web. Every plugin is a door, and every door needs patching. Skip updates for a few months and you risk a defaced site, injected spam, or a Google "this site may be hacked" warning that quietly tanks your rankings.

• WordPress: core, theme, and plugin updates needed regularly. Updates occasionally break the layout. Backups and a security plugin are not optional.
• Next.js: no plugin attack surface and no database to harden for a brochure site. The hosting platform patches the infrastructure. Far less to monitor.

If you are not paying someone to maintain a WordPress site, you are not saving money. You are deferring a bill that arrives as downtime at the worst possible moment.

Where WordPress genuinely wins

I am not here to pretend one tool fits everything. WordPress is the better choice when:

• You publish often and want non-technical staff editing posts daily in a familiar dashboard.
• You need a specific plugin ecosystem, such as a mature membership, booking, or forum system.
• You run a large WooCommerce store with hundreds of products and complex shipping rules.
• You want any local freelancer to be able to pick up the site later with zero ramp-up.

For those cases I will tell you straight and point you to a good WordPress shop rather than force a Next.js build that fights your workflow.

Where Next.js is the better call

• A marketing site whose job is to look credible, load fast, and turn visitors into WhatsApp messages and form fills.
• A business that wants strong SEO and clean structured data without wrestling a page builder.
• An owner who would rather pay a flat care fee than babysit plugin updates.
• A brand that wants a custom design, not a recognisable template other KL businesses are also using.

The three-year cost, honestly

A cheap WordPress build looks cheaper on day one. Add a year of plugin licences, a maintenance retainer, a page-builder subscription, and the eventual rebuild when the theme is abandoned, and the gap closes fast. A Next.js site costs a little more up front and very little to keep running, because there is simply less moving underneath it.

Neither platform makes a bad website good. Clear copy, a fast page, an obvious next step, and real local SEO matter more than the framework. The framework just decides how much you fight to keep those things.

How to decide in five minutes

Ask yourself one question: will my team be editing content every week, or is this a credible storefront I update a few times a year? Daily editing leans WordPress. A fast, low-maintenance storefront leans Next.js. Everything else is detail.

I build modern sites on Next.js with fixed pricing and named delivery dates. If you want to know which platform actually fits your business, see how I build websites or book a 15-minute calland I will give you the honest answer, even when it is "use WordPress."