A genuinely free CDN with unmetered bandwidth, plus a firewall, rate limiting and bot filtering, which is an unusual combination and the reason it is the default recommendation for most WordPress sites.

No egress charge at all on the free plan removes the entire cost model that shapes the rest of this comparison, which is why it is difficult to argue against for a content site. It caches assets by default and can be configured to cache HTML with care. It also gives you the security layer described elsewhere in this pillar, so a single free change improves both speed and protection. Its limitations show at the margins: less control over cache behaviour than a dedicated CDN, and full-page caching that requires either careful configuration or a paid add-on to work well with WordPress.

• Price: Free, with unmetered bandwidth
• Egress: None on the free plan
• Best for: Almost every site, as the first thing to try
• Watch out for: HTML caching needs care or a paid add-on

The best value among paid CDNs and the clearest pricing in this article. The Standard network of 119 points of presence charges $0.01 per GB in Europe and North America, $0.03 in Asia and Oceania, $0.045 in South America and $0.06 in the Middle East and Africa, with a $1 monthly minimum and no request fees.

Two details make it particularly suitable for WordPress. You can toggle regions, so a site with no African audience need not pay African rates, and a Volume network is available at $0.005 per GB for the first 500TB across 10 points of presence if breadth matters less than cost. For a typical site serving 100GB a month to European visitors, that is a dollar. Against a free Cloudflare plan it competes on control and cache behaviour rather than on price, and it wins for people who want to configure things precisely.

• Price: From $0.005 to $0.06 per GB by region and network
• Egress: Charged per GB, no request fees, $1 minimum
• Best for: Sites wanting control with predictable low cost
• Watch out for: Region rates vary sixfold; toggle what you need

Built by the LiteSpeed team and integrated with LiteSpeed Cache, which makes it the natural choice if your host runs LiteSpeed and you are already using the free plugin.

The integration is the point. Full-page caching at the edge is difficult precisely because of invalidation, and a CDN that understands the caching plugin can purge intelligently when you update a post rather than requiring you to configure rules or clear everything. It also handles image optimisation and critical CSS generation from the same account, which consolidates several line items. A free tier exists with monthly allowances, and paid usage is metered. If you are not on LiteSpeed, this loses most of its advantage and the general-purpose options above are better.

• Price: Free tier with allowances; metered beyond
• Egress: Metered usage, check current rates
• Best for: LiteSpeed sites already running LiteSpeed Cache
• Watch out for: Little advantage on non-LiteSpeed stacks

A straightforward pay-as-you-go CDN with regional per-gigabyte pricing and no monthly commitment, positioned similarly to Bunny and worth pricing against it on your own traffic distribution.

Its appeal is simplicity: you pay for what you transfer, the rates are published by region, and there is no tier to outgrow. For a site with predictable traffic in one or two regions, comparing it directly with Bunny on your actual monthly transfer is a ten-minute exercise that settles the question. Where either beats Cloudflare’s free plan is control, cache rules, and the ability to reason about exactly what is cached where. Where neither beats it is price, since free is difficult to undercut.

• Price: Pay as you go, regional per-GB rates
• Egress: Charged per GB; confirm current rates
• Best for: Predictable traffic in one or two regions
• Watch out for: Price against Bunny on your own numbers

The category where egress pricing bites hardest, and the reason this article opens with it. Enterprise networks charge more per gigabyte than the independents and frequently add per-request charges on top of transfer.

Per-request charges matter more than people expect on a WordPress site, because a single page view fetches dozens of files: images, stylesheets, scripts, fonts. Forty requests per page view across a hundred thousand page views is four million requests a month, billed separately from the data those requests carried. Set against Bunny’s explicit “no request fees” and Cloudflare’s free unmetered plan, the enterprise option needs a specific justification, and for a WordPress content site it usually does not have one. Where it does: complex origin configurations, existing infrastructure on the same cloud, or contractual requirements.

• Price: Higher per-GB rates plus per-request charges
• Egress: The dominant cost, and easy to underestimate
• Best for: Sites already inside that cloud ecosystem
• Watch out for: Request charges on top of bandwidth

Free, and correct for a surprising share of sites. If your audience is in one country and your server is in that country, the distance a CDN removes is already close to zero.

Check your analytics for where visitors actually are before buying anything. A local business, a national publisher, or a membership site serving one market gains very little from edge delivery, and the money is better spent on hosting that is faster at the origin or on removing the JavaScript that is actually slowing the page. If your server is in the wrong country entirely, which happens more often than it should, moving hosting is a one-off change that beats layering a CDN over a badly placed origin. Cloudflare’s free plan remains worth enabling regardless, for the firewall rather than for the delivery.

• Price: Free, or the cost of better-placed hosting
• Egress: None
• Best for: Single-country audiences
• Watch out for: Check your analytics rather than assuming