Cloudflare comes up constantly in conversations about website performance. Someone reads that a CDN will make their site faster, adds Cloudflare, and either notices a difference or doesn’t and wonders why. Most explanations of what a CDN does either oversimplify it to “it makes your site faster” or go deep into network architecture that isn’t useful to someone running a small business website.
Here’s the plain-English version — what a CDN actually does, when it helps, and when you probably don’t need the paid version.
The Problem a CDN Solves
Your website lives on a server in a specific physical location. When someone visits your site, their browser sends a request to that server, the server responds, and the content travels across the internet to reach them. The further away the visitor is from your server, the longer that trip takes.
If your server is in Dallas and your visitor is in London, the request has to travel across the Atlantic and back. That adds latency — not a huge amount with modern fiber infrastructure, but measurable, and it compounds with every asset on the page.
A Content Delivery Network is a globally distributed network of servers — called edge servers or points of presence — spread across data centers around the world. When you use a CDN, copies of your site’s static content (images, CSS, JavaScript, fonts) get cached on these edge servers. When a visitor requests your site, they get served from the edge server closest to them rather than from your origin server in Dallas.
Without CDN vs with CDN — where content comes from
What a CDN Actually Caches
CDNs cache static assets — files that don’t change between visitors. Images, CSS stylesheets, JavaScript files, fonts, videos. These are the files that make up the bulk of most page weight and don’t need to be generated fresh for each visitor.
What CDNs don’t cache (by default): dynamic content. When you load a WordPress page, the HTML is generated fresh on each request — pulling content from the database, applying your theme, building the page. That dynamic generation still happens on your origin server. The CDN serves the images and scripts from nearby edge servers, but the HTML comes from Dallas.
Some CDN configurations can cache even dynamic pages, but that requires more careful setup and isn’t the default. For most small business WordPress sites, the standard CDN setup — caching static assets — is what you want.
What Cloudflare Specifically Does
Cloudflare is the most widely used CDN for small and medium websites, largely because their free tier is genuinely useful. When you add your site to Cloudflare, you update your domain’s nameservers to Cloudflare’s — all traffic to your site now passes through Cloudflare’s network before reaching your server.
This gives you several things beyond just CDN caching:
- DDoS protection — Cloudflare absorbs and filters malicious traffic before it reaches your server
- SSL termination — Cloudflare handles SSL for your domain even if your origin server doesn’t have it configured
- Minification — Cloudflare can automatically minify your HTML, CSS, and JavaScript on the fly
- Analytics — basic traffic analytics without adding JavaScript to your pages
- Firewall rules — ability to block traffic from specific countries or matching specific patterns
All of this is available on Cloudflare’s free tier. For most small business sites, the free tier is all you need.
When a CDN Actually Makes a Meaningful Difference
A CDN makes the biggest difference when:
- Your audience is geographically distributed. If most of your visitors are in the same city or region as your server, the latency reduction from a CDN is minimal. If you have significant traffic from multiple continents, a CDN makes a real difference.
- Your pages are asset-heavy. A site with lots of images, video, or large JavaScript bundles benefits more from CDN delivery than a simple text-focused site.
- You’re getting significant traffic volume. A CDN offloads requests from your origin server, which reduces load. At low traffic volumes this doesn’t matter much. At high volumes it matters a lot.
When a CDN Won’t Help Much
- Your site is slow because of WordPress execution time — if your TTFB is already high, a CDN doesn’t fix that. The dynamic WordPress execution still happens on your origin server. Fix the WordPress performance issues first (caching plugin, image optimization, plugin bloat) — a CDN stacks on top of a fast site, it doesn’t fix a slow one.
- Your audience is local. A restaurant serving a single city, a local service business, a regional organization — if your visitors are all within a few hundred miles of your server, the geographic distribution benefit of a CDN is marginal.
The Honest Recommendation
For most small business sites: add Cloudflare’s free tier. It takes about fifteen minutes to set up, costs nothing, and gives you CDN caching, DDoS protection, and SSL at no charge. There’s almost no downside for a straightforward WordPress site.
Don’t pay for Cloudflare Pro ($20/month) or Business ($200/month) unless you have a specific reason — image optimization at scale, advanced firewall rules, priority support. The free tier covers everything a typical small business site needs.
And before you add a CDN: make sure your site is already performing well at the server level. A CDN on top of a slow, uncached WordPress site will still be a slow site — just with some assets loading slightly faster. The order of operations is: fix WordPress performance first, then add CDN as the finishing layer.
If you want help setting up Cloudflare with your HostDango account, open a support ticket. The nameserver change is straightforward but the first time you do it, having someone walk you through it is worth the five minutes.