Traditional web hosting usually gives your website server resources on which an application can run. A Cloudflare Pages-style setup can instead serve finished website assets across a global network, adding server-side code only where it is needed.
Neither approach is universally better.
They solve different problems.
For a straightforward small-business website, I often prefer the Cloudflare/static model because it is simpler, fast and extremely inexpensive.
For a website that genuinely needs a traditional application stack, traditional or managed hosting may be the better choice.
What does "traditional hosting" mean?
Traditionally, a business buys a hosting package from a provider.
That hosting account gives the website access to things such as:
server storage;
PHP or another server runtime;
a database;
email in some packages;
control-panel tools;
backups and support depending on the plan.
WordPress commonly runs in this kind of environment.
Every page request may involve the server running code and querying a database before returning the finished page.
Modern caching can make that very fast, but the application still exists behind the scenes.
How is Cloudflare Pages different?
A static deployment prepares the website pages before the visitor asks for them.
The resulting HTML, CSS, JavaScript and images can be distributed through Cloudflare's network.
The visitor requests a page and Cloudflare serves the asset.
There may be no application server or database involved in that page request at all.
When dynamic functionality is required, Pages Functions or Workers can run server-side code separately.
That gives you a useful split:
simple content stays simple; dynamic functionality is added where necessary.
Why does that affect cost?
Servers and application stacks create ongoing resource use and management.
Static assets are much cheaper to distribute at scale.
Cloudflare currently makes requests to Pages static assets free and unlimited on both free and paid plans.
That is why a simple custom website can have virtually no hosting bill.
Traditional hosting may still be inexpensive — particularly shared hosting — but it normally starts from the assumption that you are renting a hosting environment.
The Cloudflare model can start from the assumption that the site may not need one.
Does this mean Cloudflare is always cheaper?
No.
If a site uses substantial Workers compute, databases or other paid services, costs can appear.
If you need a specialist platform such as Shopify, comparing it only to Cloudflare hosting is not particularly useful because Shopify provides an entire commerce system.
Likewise, managed WordPress hosting may include support and maintenance that Cloudflare Pages is not trying to provide in the same way.
Compare the whole requirement.
Not one line of the invoice.
What about WordPress?
WordPress needs a suitable dynamic hosting environment.
Cloudflare can still sit in front of WordPress for DNS, security and caching, but Cloudflare Pages itself is not simply a drop-in WordPress host.
This is why the decision begins with the site architecture.
If the client needs WordPress, choose good WordPress infrastructure.
If the client does not need WordPress, do not install it simply because it is familiar.
I cover that directly in the planned static website vs WordPress comparison.
Maintenance is another major difference
A traditional CMS application has moving parts.
WordPress core, themes, plugins, PHP and database dependencies can need updating.
That maintenance is real.
A static site has fewer application components exposed to the public internet.
That does not mean it is magically maintenance-free.
Dependencies, forms and integrations still need sensible management.
But there is simply less runtime software to babysit.
That can reduce both technical risk and the amount of ongoing work required.
What about speed?
Static delivery can be extremely fast because the page is already prepared.
Cloudflare distributes content through its network, reducing the distance between the visitor and the asset.
A well-configured traditional host can also deliver very fast websites.
So I would not market this as:
Cloudflare fast, hosting slow.
That would be nonsense.
The useful point is that static architecture makes good performance easier to achieve because there is less work required to generate the page.
What about security?
Again, architecture matters.
A WordPress site is a live application with a login, database, plugins and server-side software.
That creates more components that may need security attention.
A static site exposes fewer moving parts.
Cloudflare also provides security and SSL/TLS features around the site.
But no platform makes a website invulnerable.
Good configuration, account security and sensible third-party integrations still matter.
What about backups?
A traditional site may need database backups and file backups because the live server contains changing state.
A static development workflow can be different.
The website source can be version-controlled, and deployments can be recreated from that source.
Cloudflare Pages also supports deployment rollbacks.
Again, that does not eliminate the need to think about backups.
It changes what needs backing up.
If your contact enquiries live in an external CRM, that data belongs to the CRM rather than the static site.
Which model is easier for the client?
That depends on what the client wants to edit.
A WordPress CMS gives the business a familiar browser-based content-editing interface.
That can be very useful for businesses publishing regularly.
A custom static site may require a different content workflow or a CMS layer if the client wants frequent self-service editing.
That is one of the strongest legitimate reasons to choose a CMS.
Technology should fit the operating reality of the business.
What I'd do
I would ask one very practical question before choosing the hosting model: who is actually going to update this website, and how often? If the owner wants to publish every week from a browser, a CMS may earn its extra complexity. If the site changes a few times a year and somebody else will make those edits, building an entire CMS around hypothetical future editing can be needless overhead.
Which is better for SEO?
Neither hosting label wins SEO by itself.
Google cares about what it can crawl, the content, performance, usability, relevance and the wider signals around the page.
A slow broken WordPress site can perform badly.
A fast empty static site can also perform badly.
The architecture should support the SEO strategy, not substitute for one.
How Built by Gavin chooses
I start from the business requirement.
If the client needs a straightforward marketing website, a lean static architecture is often ideal.
If the client needs frequent self-service publishing, a CMS may make sense.
If the project needs e-commerce, I would consider established commerce platforms.
If it needs custom server-side functionality, that can be added deliberately.
I do not believe a small business should inherit a complex hosting environment purely because it is the default package the designer sells.
Gavin's take
I do not think clients should be expected to arrive knowing whether they need Cloudflare, WordPress or traditional hosting. That is backwards. Tell me what the business needs the website to do, how it will be updated and what integrations matter; choosing the simplest suitable architecture is part of my job.
The cost question
This is where the choice becomes especially relevant for small businesses.
A static site can often avoid a meaningful monthly hosting charge.
A managed dynamic site may have a legitimate recurring cost.
What I dislike is pretending those two things are the same.
They are different technologies with different operating requirements.
You can see the broader pricing context in website hosting costs in Ireland.
So which should you choose?
For a simple brochure or lead-generation website, I would usually favour the lean static model.
For a content-heavy site where non-technical staff publish constantly, a CMS can be the better tool.
For a business application, the answer depends on the application.
The important thing is that the architecture serves the business.
Not the other way around.
The bottom line
Traditional hosting is not obsolete.
Cloudflare does not make every server unnecessary.
But modern static hosting gives small businesses another option — one that can be faster to maintain, cheaper to operate and simpler to own.
For many ordinary business websites, that is a very strong fit.
Want the simpler model where it makes sense?
See my website options or tell me how you expect to use the site.
I will recommend the architecture based on the requirement rather than trying to fit every business into the same hosting package.
---