Why Cloudflare plus Next.js is the best website setup for most UK small businesses in 2026

For most UK small businesses in 2026, the best website setup money can buy is Next.js deployed on Cloudflare Pages (or Vercel, which itself sits on a very similar edge network). It is faster than any traditional WordPress stack, costs between nothing and a pizza a month to run, requires no server administration, and passes Google's Core Web Vitals without needing a specialist to optimise it. The exceptions are narrow and specific. If you are reading this and wondering what platform to build on, start here.

That is a strong claim, so the rest of this article will back it up. What the stack actually is, why it beats the alternatives for most businesses, who should ignore this advice, and the handful of tips and mistakes that separate a fast site from one that only looks fast on paper.

What "Cloudflare plus Next.js" actually means

Next.js is a modern web framework built on React. It is the most widely used React framework in the world, it ships with excellent defaults for search engine visibility, image optimisation, and server rendering, and it is developed in the open by Vercel with contributions from the broader community.

Cloudflare is a global network of data centres (edge locations) that sit between your users and your origin server. Its original product was a content delivery network and security layer, but in the last five years it has grown into a full application platform. Cloudflare Pages hosts static and dynamic Next.js sites directly. Cloudflare Workers run code at the edge. D1, R2, and Workers KV provide storage. All of it runs on the same global network, from 300-plus cities.

When people say "Cloudflare plus Next.js" they usually mean one of two things. Either Next.js deployed directly on Cloudflare Pages, which runs the whole site on Cloudflare's edge. Or Next.js deployed on Vercel with Cloudflare sitting in front as the DNS and sometimes as a CDN layer. Both give you roughly the same user experience. Vercel is slightly smoother as a developer experience. Cloudflare is cheaper at scale and has fewer vendor boundaries. For most small businesses either path is a good answer.

Why this beats the alternatives for most businesses

Five reasons.

Speed first. A Next.js site served from the edge typically loads in under a second anywhere in the world, with Core Web Vitals comfortably in the green. A typical managed WordPress site on shared hosting loads in three to six seconds in the UK, and far worse from international visitors. This matters for conversion and for SEO. The search engines have been measuring page speed as a ranking factor for years, and the AI assistants that are increasingly mediating discovery actively avoid slow or flaky pages when they pick which sources to cite. Fast is no longer optional.

Cost. The cheapest credible WordPress hosting is around ten pounds a month once you factor in managed updates and a decent backup. The Cloudflare plus Next.js stack costs nothing at all for most small business traffic levels. Vercel's free tier covers a hundred gigabytes of bandwidth and a hundred thousand serverless invocations per month. Cloudflare Pages offers unlimited sites for free with generous bandwidth. You only start paying when you reach scale most small businesses never reach, and even then the costs are predictable and reasonable.

No server admin. There is no operating system to patch, no database to back up, no plugin to update at midnight because it broke the site. The deploy target is a managed platform. You push code, the platform builds and deploys. Security patches, SSL certificates, DDoS protection, and global distribution all happen by default.

Security. Traditional small business sites get hacked via outdated plugins or stolen admin credentials. A Next.js site has no admin panel to break into, no plugins to exploit, and no database exposed to the public internet unless you choose to connect one. Cloudflare's bot protection and rate limiting sit in front of everything for free.

SEO and GEO alignment. A static or mostly static site with clean URLs and server-rendered HTML is exactly what every search engine and every AI assistant wants to see. If you have read our plain English guide to SEO for small businesses, the technical basics that guide calls out are all handled by default in this stack. The same is true for AI search optimisation. Static HTML is the most legible format for machine readers, and every page can carry its own schema markup without any of the fragility that WordPress sometimes introduces.

Who should ignore this advice

Four kinds of business should probably pick something else.

Heavy content editing by non-technical staff. If your marketing team produces several articles a week, likes visual page builders, and expects to click around and publish without developer help, classic WordPress is still a better daily experience for them than a Next.js site connected to a headless CMS. You can combine the two (Sanity, Contentful, or Payload as the CMS with Next.js rendering the front), but it is an extra layer. For teams that genuinely live in the editor, the simpler thing usually wins.

Deep plugin dependency. If your business runs on a specific WordPress plugin ecosystem (a niche industry LMS, a regulated booking flow, a bespoke integration that only exists as a WP extension), moving to Next.js means rebuilding that functionality from scratch. Sometimes worth it, often not. The cost benefit needs to be assessed honestly.

True e-commerce beyond a handful of products. Shopify is better for most small e-commerce, full stop. You can build a custom Next.js front on top of Shopify's APIs if you want, but the default Shopify stack is already very fast and the admin experience is built for product operators. Do not reinvent a wheel that already works well. For a broader platform comparison see our piece on WordPress, Squarespace, and custom.

Very particular data residency or compliance needs. Certain regulated sectors require data to live in a specific jurisdiction, under a specific operator, with specific audit trails. Generic edge platforms can meet these needs, but configuring them is more work than meeting the same rules on a single managed server with documentation. If this is you, you probably already know, and the trade-offs lean different ways.

For almost everyone else, Cloudflare plus Next.js is the right default.

Tips that separate a fast site from a slow one

Choose your database location carefully. This is the single most common mistake I see in the wild. A small business migrates to Next.js on Vercel, connects it to a US-based Postgres database (because that is what Supabase gives you by default), and then wonders why pages feel slow even though the code is deployed to the edge. Every request to render a page has to cross the Atlantic, query the database, and come back. Keep the database in the region closest to your users. For a UK-focused business that means London (LHR) or Frankfurt (FRA). Supabase, Neon, and PlanetScale all let you pick regions at project creation. If you are already on the wrong region, moving is painful but worth doing early.

Prefer static pages over dynamic ones wherever you can. Next.js will render a page at build time if you let it, and the result is a plain HTML file cached at every edge location. That is unbeatably fast. A page that needs fresh data on every request (a personal dashboard, a live inventory check) has to be server rendered and will always be slower. For a small business marketing site, the vast majority of pages can and should be statically generated. Use server rendering only where it earns its cost.

Use Incremental Static Regeneration for content that updates occasionally. Blog posts, case studies, team pages. Set a revalidation window of an hour or a day, and the platform regenerates the static page in the background when the content changes. You get the speed of static with the freshness of dynamic.

Turn on image optimisation. Next.js ships with an Image component that serves WebP or AVIF to browsers that support them, resizes on demand, and sets the right dimensions to prevent layout shift. Most small business sites still serve two-megabyte JPEGs. The difference in Core Web Vitals scores is embarrassing.

Put Cloudflare in front of Vercel if you are on Vercel, or use Cloudflare Pages directly. Either way you want Cloudflare's bot protection, rate limiting, and page caching rules. The combined effect is a site that survives the day it gets mentioned on Reddit without you touching anything.

Set up Core Web Vitals monitoring from day one. Vercel Analytics or Cloudflare Web Analytics will give you real user metrics for free, without cookies, without affecting privacy compliance. Check them weekly, especially after any content or design change. Speed drifts upward over time if nobody is watching.

Common mistakes

Edge functions served from the wrong region. Your site is deployed to Cloudflare's or Vercel's global edge, but a server function (say, the handler that processes a form submission) can end up pinned to a specific region. If that region is the US default and your users are in the UK, every form submission adds a transatlantic round trip. Configure your edge functions to run in the same region as your primary database, or the region closest to your users if the function does not hit a database at all.

Database queries in the middle of a server-rendered page. If a page needs one database lookup to render, that lookup latency becomes part of the page load. Every extra millisecond shows up in Core Web Vitals. Batch database calls, cache aggressively, and think hard about whether the query can be avoided (for example, by pre-generating the content at build time).

Running heavy third-party scripts without thinking. Every tag you add (analytics, chat widgets, ad pixels, heat maps) costs performance. I see small business sites with twelve tracking scripts and a Lighthouse score of 40. Audit what is actually on your site, remove anything that is not earning its cost, and load the rest asynchronously. A fast site with three clean scripts always outperforms a slow site with twelve.

Not configuring caching rules. Out of the box, Vercel and Cloudflare both apply sensible defaults, but if you are serving something unusual (a specific endpoint that returns user-specific data, a file type they do not know how to handle), the defaults can either over-cache or under-cache. Understand the cache hit ratio on your site. Aim for 90 percent plus on content pages.

Over-engineering the first version. A lot of teams hear "edge", "serverless", "static regeneration", and think they need to use all of it on day one. You do not. Build a static site first. Add dynamic features only where they are genuinely needed. Static beats clever almost every time for small business marketing sites, and the simpler your setup the fewer things can break.

How to decide for your business

If your website is mostly marketing content (homepage, services, about, case studies, blog, contact), pick Cloudflare plus Next.js. It is faster, cheaper, and more secure than anything else at this scale.

If your website is a product catalogue with a shopping cart and fewer than about two hundred SKUs, Shopify is probably still the right call and you should not spend time debating this.

If your website is primarily a content publication with a non-technical editor team posting daily, classic WordPress on managed hosting (WP Engine, Kinsta) is still a genuinely reasonable choice. The editor ergonomics matter more than pure speed for that use case.

If none of these fit cleanly, or if you are building something that crosses these boundaries, book a free call and we can map out the trade-offs specifically for your business.

One last thing

The argument for this stack is not fashion. It is performance, cost, and operational simplicity. Those three things compound. A site that loads in under a second and costs nothing to run frees up attention and budget for the things that actually grow the business, which is what Voll is about. If you are already on WordPress or Squarespace and it is working well, you do not have to migrate. But if you are choosing a platform for a new business in 2026, or your current site is slow and expensive, this is the setup to move towards. Our full guide to what makes a great small business website covers the design principles that go alongside the technical ones. And if speed is the specific thing costing you customers right now, our piece on the three main reasons websites lose customers is the quickest diagnostic.

Free 15-minute call if you want to talk about whether this setup fits your business: book one here.