Back to blog
Technology 24 March 2025· 9 min read

WordPress vs Next.js: why we don't build WordPress sites

WordPress powers over 40% of the internet. So why don't we use it? Here's an honest, no-nonsense comparison, and when WordPress actually is the right choice.

Let's start with honesty

WordPress isn't bad. That's not what this article is about. WordPress has powered millions of successful websites and will continue to do so. The WordPress ecosystem is massive, the community is strong, and for certain use cases, it remains an excellent choice.

But for the small business websites we build (brochure sites, service pages, portfolios for tradespeople and local businesses across Halifaxand West Yorkshire), WordPress comes with baggage that our clients shouldn't have to deal with. Here's why.

Speed: this is where it gets embarrassing

The average WordPress business website scores between 25 and 55 on Google PageSpeed Insights (mobile). That's not a guess. Test any local business site built on WordPress with a page builder and see for yourself.

Why so slow? WordPress is a dynamic CMS. Every time someone visits your site, the server has to query a database, process PHP code, assemble the page, and send it to the browser. Add a page builder like Elementor or Divi on top, and you're also loading hundreds of kilobytes of CSS and JavaScript that the page builder needs to render its drag-and-drop layouts.

Next.js works fundamentally differently. It generates static HTML files at build time. When someone visits your site, the server simply hands over a pre-built HTML file. No database queries. No PHP processing. No page builder overhead. The page is ready before the browser even finishes asking for it.

The result? Our Next.js sites consistently score 95–100 on Google PageSpeed. Not through tricks or caching hacks, but because the architecture is fundamentally faster. You can verify this yourself on our portfolio page.

What about caching plugins?

This is the first thing WordPress defenders mention. “Just use WP Rocket” or “install W3 Total Cache.” And yes, caching plugins help. They can take a 35 score to maybe 55 or 60. But you're putting a plaster on a structural problem.

Caching plugins work by pre-generating static versions of your pages, which is exactly what Next.js does by default, without the overhead of WordPress underneath. You're paying for a plugin to poorly imitate what a modern framework does natively.

Security: WordPress is a target

Because WordPress is so popular, it's the number one target for hackers. Wordfence (a WordPress security plugin) reported blocking over 90 billion malicious login attempts in a single year. Outdated plugins, weak passwords, and unpatched vulnerabilities make WordPress sites a constant target.

Every WordPress plugin you install is a potential entry point. Contact form plugin? Security risk. SEO plugin? Security risk. That gallery plugin you installed two years ago and forgot about? Definitely a security risk.

A Next.js static site has no database to inject into, no login page to brute-force, no plugins to exploit. The attack surface is essentially zero. Your site is just HTML, CSS, and a bit of JavaScript sitting on a CDN. There's nothing to hack.

Maintenance: the hidden time tax

A WordPress site is never “done.” After launch, you need to:

  • Update WordPress core (several times a year, sometimes with breaking changes)
  • Update plugins (constantly, and sometimes updates break your site)
  • Update your theme (if it's still being maintained)
  • Monitor for security vulnerabilities
  • Manage database bloat and optimise tables
  • Deal with plugin conflicts when two plugins don't play nicely together
  • Renew hosting, manage backups, handle SSL certificates

Most business owners don't do any of this. Their WordPress site sits there accumulating security vulnerabilities like a house accumulating dust. Eventually something breaks, or worse, they get hacked and their site starts redirecting visitors to a casino in the Philippines.

A Next.js static site needs none of this. There are no plugins to update, no database to maintain, no server to patch. Once it's built and deployed, it runs. You focus on your business; the website takes care of itself.

Plugin bloat: the WordPress tax

The average WordPress business site has 20–30 active plugins. Each one adds weight to your site. Some add database queries. Many add their own CSS and JavaScript files that load on every page, regardless of whether they're needed.

Here's what a typical WordPress business site plugin list looks like:

  • Page builder (Elementor, Divi, WPBakery): the biggest performance killer
  • SEO plugin (Yoast, Rank Math)
  • Security plugin (Wordfence, Sucuri)
  • Caching plugin (WP Rocket, W3 Total Cache)
  • Contact form plugin (Contact Form 7, WPForms)
  • Image optimisation plugin
  • Backup plugin
  • Analytics plugin
  • Cookie consent plugin
  • Various utility plugins to fix things that should work out of the box

You're installing a security plugin to protect the plugins, a caching plugin to speed up the page builder, and an optimisation plugin to compress the images the theme didn't handle properly. It's plugins all the way down.

With Next.js, we write the code we need. A contact form? Built into the site. SEO meta tags? Part of the framework. Image optimisation? Handled at build time. No plugins, no bloat, no dependencies to manage.

Why do most agencies push WordPress?

Let's be straight about this: most web agencies use WordPress because it's easier for them, not because it's better for you.

  • Lower skill floor: You can build a WordPress site without knowing how to code. Drag-and-drop page builders mean agencies can hire junior designers and have them producing sites quickly.
  • Recurring revenue: WordPress sites need hosting and maintenance. That's a monthly retainer opportunity. Some agencies make more from retainers than from building sites.
  • Client lock-in: If your site runs on their managed WordPress hosting, leaving means rebuilding from scratch. That's not a partnership, it's a dependency.
  • It's what they know: Learning a new technology stack takes time and money. Most agencies have years of WordPress experience and no incentive to change.

None of these reasons benefit you as the client. They benefit the agency.

When WordPress IS the right choice

We're not dogmatic about this. WordPress genuinely is the better option in certain situations:

  • You need a blog with frequent posts and want non-technical staff to publish content through a visual editor. WordPress's CMS is mature and user-friendly.
  • You need a complex e-commerce store with hundreds of products, inventory management, and payment processing. WooCommerce is battle-tested for this.
  • You need to integrate with specific third-party services that only have WordPress plugins.
  • Your budget is under £500 and you just need something live quickly. A WordPress theme can get you online faster and cheaper.

For a standard small business website, one that needs to look professional, load fast, rank locally, and generate enquiries, WordPress is overkill in the wrong direction. You don't need a CMS. You need a fast, well-built website.

Our Next.js approach

Every site we build at Webvise uses Next.js with static export. Here's what that means for you in plain English:

  • Blazing fast: Pages load in under a second. Google rewards this with better rankings.
  • Unhackable: No database, no login page, no plugins. Nothing to exploit.
  • Zero maintenance: No updates to install, no patches to apply. It just works.
  • Free hosting: Static sites can be hosted on Vercel for free, saving you £10–£50/month compared to WordPress hosting.
  • You own it: No retainers, no lock-in. If you want to move to a different developer, the code is yours.

Want to see the difference for yourself? Run any site on our portfolio page through Google PageSpeed Insights and compare it to your current site. The numbers speak for themselves.

The bottom line

WordPress is a powerful platform with legitimate use cases. But for the typical small business website (a plumber in Halifax, a roofer in Huddersfield, a salon in Bradford), it introduces complexity, cost, and performance problems that simply don't need to exist.

We chose to specialise in Next.js because it delivers better results for our clients. Faster sites. Better Google rankings. Lower ongoing costs. No maintenance headaches. That's not a sales pitch. It's measurable, verifiable, and something you can test yourself.

Curious what a fast, modern website looks like for your business? Read our guide on what makes a fast website, or get in touchand we'll show you.

Ready for a website that actually performs?

No WordPress. No retainers. Just fast, modern sites built to rank.

Get a Free Quote