A content delivery network costs $0 per month at the entry level: Cloudflare's Free plan lists CDN, Universal SSL, and unmetered DDoS protection as included, with Pro at $20 per month billed annually ($25 month-to-month), per Cloudflare's plans page as of September 2026. That price point is why "free CDN included" appears on so many hosting feature lists, and why the line tells a buyer very little. What decides whether a CDN makes a site faster is what it caches, and by Cloudflare's own documentation, its CDN does not cache HTML by default.
Disclosure: HostingDive earns a commission when you buy through our links, at no extra cost to you. Ratings come from independent testing.
The Short Answer
A CDN included with a hosting plan is worth having and almost never worth paying extra for on its own. Out of the box, it speeds up images, stylesheets, scripts, and downloads for visitors far from the origin server. It does not, by default, speed up the page itself, because the HTML is still generated by the host on every uncached request. For a site whose visitors are mostly in one country near the server, a CDN changes little. For a site with a national or international audience, or heavy image and media weight, it is the cheapest performance improvement available.
What a CDN Actually Caches
A CDN is a network of edge servers that store copies of a site's files closer to visitors. When a visitor in Chicago requests an image from a site hosted in Amsterdam, the CDN serves the stored copy from a nearby edge location instead of making the request cross the Atlantic. The origin server only sees the requests the edge cannot answer.
Static assets versus the page
The distinction that matters is between static assets and the HTML document. Cloudflare's default cache behavior documentation states that its CDN does not cache HTML or JSON by default, and caches by file extension instead: images, video, PDFs, archives, CSS, JavaScript, and fonts. On a typical WordPress page, those static files are most of the bytes, but the HTML document is the first thing the browser waits for. If the host takes 900 milliseconds to generate that HTML, a CDN that only caches images leaves the 900 milliseconds in place.
Caching the HTML itself, sometimes called full-page or edge HTML caching, is where the large speed gains come from. It requires deliberate configuration, a WordPress integration, or a higher plan tier, and it introduces the risk that makes it off by default: serving one visitor a page that was generated for someone else.
Where full-page caching breaks
Any page that changes per visitor must bypass the edge cache. On a WooCommerce store that means cart, checkout, and account pages, plus any page that shows a logged-in state. Membership sites, forums, and booking tools have the same problem across more of the site. A misconfigured HTML cache on a store can show one customer's cart contents to another, which is a data exposure, not a performance bug. This is the main reason managed hosts that offer edge caching ship pre-built bypass rules for WordPress and WooCommerce rather than a bare on switch.
How CDNs Show Up by Plan Type
"CDN included" means different things at different tiers. The pattern below describes the general shape of the market rather than any single provider's offer. The plan being purchased has to be checked at the moment of purchase.
| Plan type | What "CDN included" usually means | Caches HTML? | Verdict |
|---|---|---|---|
| Entry-level shared | A one-click Cloudflare connection, or nothing | No, unless configured | Fine for static assets; check whether the host or the buyer owns the DNS setup |
| Higher-tier shared | Host-branded CDN on selected plans | Sometimes, with limits | Confirm which tier actually includes it before paying for the upgrade |
| Managed WordPress | Edge CDN plus server-level page caching, usually bundled | Often, with WooCommerce bypass rules | The strongest default setup; verify bypass rules for cart and checkout |
| VPS or cloud | Nothing bundled; bring a third-party CDN | Only if you configure it | Most flexible, and the configuration work is yours |
| Standalone CDN (Cloudflare Free or Pro) | DNS moved to the CDN provider; works with any host | Not by default | $0 to start; the practical baseline for any host without one |
A CDN cannot fix a slow origin. If uncached pages take over a second to generate, the bottleneck is the plan's CPU, PHP workers, or database, and no amount of edge caching on images will move time to first byte. The measured differences between hosts on that metric are tracked in the HostingDive hosting speed index.
What the Numbers Mean for a Buying Decision
Three variables decide how much a CDN is worth to a specific site: where the visitors are, how heavy the pages are, and how fast the origin already is.
Audience geography. Latency grows with physical distance. A site hosted in a US data center serving a US audience already has short round trips for most visitors, and the CDN's gain is modest. The same site serving buyers in Europe and Australia gains far more, because every uncached asset otherwise travels across an ocean.
Page weight. A text-heavy blog with a few compressed images has little for a CDN to accelerate. A portfolio, photography, or product-catalog site with dozens of large images per page recovers a large share of its load time from edge delivery. This is also where a CDN relieves the hosting plan: every image served from the edge is a request the origin never handles, which matters on shared plans metered by CPU or resource limits.
Origin speed. Once the static assets are at the edge, the remaining delay is HTML generation. Two hosts with the same CDN will still differ by whatever their servers take to build the page. This is why a host with a fast origin and no bundled CDN, paired with a free standalone CDN, can outperform a slower host that advertises one.
Who Should Pay for a CDN (and Who Should Not)
- Pay attention if: a large share of visitors are on a different continent from the server. Distance is the clearest signal that a CDN will pay off.
- Pay attention if: the site is image or media heavy, or sells downloads. Edge delivery takes the largest share of bytes off the origin.
- Pay attention if: the site is a WooCommerce store on a managed plan. The bundled edge caching and its bypass rules are a real feature, not a checkbox.
- Skip the upgrade if: the only difference between two plan tiers is a CDN. A free standalone CDN covers static assets on any host.
- Skip the worry if: the site is a local business with a local audience. The server location matters more than an edge network for a plumber in one metro area.
For small business sites deciding which plan tier to buy in the first place, CDN is a secondary line item behind storage, resource limits, and renewal price, as covered in the small business hosting sizing guide.
The Fine Print
Who controls DNS. Connecting a standalone CDN usually means moving the domain's nameservers to the CDN provider. Email records, domain verification records, and any subdomains have to move with them. A careless switch is a common cause of broken email the day after a "free speed upgrade."
Cache purging. Content updates can take time to reach visitors if the edge is still serving an old copy. Check whether the host's WordPress integration purges the CDN automatically on publish, or whether it has to be done by hand.
Host-branded CDN terms. Some hosts include a CDN only on higher tiers or cap it on lower ones. Treat any "CDN included" line as a question about the specific plan, and read it alongside the plan's renewal price rather than the intro price.
Staging and caching. Caching rules applied to a live site can also affect a staging copy on a subdomain. The mechanics of keeping test environments isolated are covered in what a hosting staging environment does.
Pricing as of September 2026. Verify current pricing on the provider website before purchasing.
The Verdict
Treat "free CDN included" as a baseline, not a differentiator. Every site can get edge delivery for static assets at $0 per month, so a plan should never win a comparison on that line alone. The features that separate hosts are the ones a free standalone CDN does not provide by default: fast HTML generation at the origin, and edge caching of the page itself with safe bypass rules for carts, checkouts, and logged-in users. Buyers with an international audience or a media-heavy site should weight CDN setup heavily. Buyers with a local audience should spend the comparison time on origin speed and renewal pricing instead.
Compare managed WordPress hosting options on HostingDive, with current intro and renewal pricing on every plan.
Frequently Asked Questions
- Does a CDN make a whole website faster?
- Not by default. A standard CDN caches static files such as images, CSS, JavaScript, and fonts, and Cloudflare's documentation states it does not cache HTML or JSON by default. The page itself is still generated by the host, so time to first byte depends on the origin server unless full-page edge caching is configured.
- Is Cloudflare's free plan enough for a small business site?
- For static asset delivery, usually yes. Cloudflare's Free plan lists CDN, Universal SSL, and unmetered DDoS protection as included at $0 per month. Pro costs $20 per month billed annually or $25 month-to-month, as of September 2026. The paid tiers add features, not a basic CDN.
- Is a CDN worth it when visitors are local?
- Rarely. CDN gains come mostly from reducing the distance between visitors and the server. A local business with a local audience and a server in the same region gets a modest improvement at best, and the plan's origin speed matters more.
- Can a CDN break a WooCommerce store?
- Yes, if HTML caching is turned on without bypass rules. Cart, checkout, and account pages must never be served from the edge cache, or one customer can be shown content generated for another. Managed WordPress hosts that offer edge caching generally ship these rules pre-configured; check before enabling it manually.
- Does using a CDN reduce hosting resource usage?
- Yes. Every file served from the edge is a request the origin server does not handle. On shared plans with CPU or resource limits, moving image and asset delivery to a CDN reduces load on the plan, though it does not reduce the cost of generating uncached pages.