CDN marketing assumes your audience is far from your server. But a large share of WordPress sites serve mostly-local audiences — and if your origin is already in Frankfurt serving Germans, a CDN buys less than the sales page implies. We measured four CDN approaches on an EU-origin server with EU test locations, which is the honest setup for most of our clients’ B2B traffic.
The four approaches
| Approach | Mechanism | Asset latency (EU test) | Notes |
|---|---|---|---|
| Cloudflare (DNS-level) | Full proxy at DNS | Best overall | Free tier; needs DNS control |
| CDN Enabler + Cloudflare/KeyCDN | Rewrites asset URLs | Good | Simple, free plugin |
| WP Rocket CDN option | Rewrites asset URLs | Good | Convenient if already using WP Rocket |
| Jetpack CDN (Photon) | Images through Automattic’s CDN | Good for images only | Free; image-only scope |
What the numbers showed
- From EU origin to EU visitors, page-level TTFB gains were small — 8–15ms, since the edge is roughly as far as the origin. The cache layer dominates; a CDN cannot cache what the origin still generates slowly.
- Static assets (images, fonts, JS) still benefited — 20–40ms per asset, compounding across 30+ assets per page.
- Non-EU visitors (US, UK buyers of EU B2B firms) gained the most — 150–300ms per request, which matters for international lead flow described in the B2B benchmarks.
Recommendations
- Have DNS control: Cloudflare at DNS level beats every plugin approach — and the user-configured Cloudflare on this very site demonstrates the pattern.
- Cannot touch DNS (shared hosting limits): CDN Enabler with KeyCDN/Bunny — free plugin, cheap CDN, done in an hour.
- Images only, zero budget: Jetpack Photon — free, decent, scope-limited.
The honest sequencing
CDN is step four, not step one: caching, image optimization, and theme weight all move LCP more for a local audience. The free audit measures where your visitors actually are before you pay for global edge.
No — Cloudflare at DNS level proxies assets already. URL-rewriting CDN plugins are for when you cannot route DNS through Cloudflare or use a separate CDN provider. Modestly. EU-origin to EU visitors gains 8–15ms TTFB and 20–40ms per asset — real but smaller than caching or image optimization gains. International visitors gain far more. CDN Enabler with a low-cost provider like Bunny, or Jetpack Photon for images-only. Both free approaches delivered the assets effectively in our tests. CDNs accelerate delivery, not generation: slow uncached TTFB, heavy themes, and missing page cache persist behind any CDN. Fix origin performance first.Do I need a CDN plugin if I use Cloudflare?
Does a CDN help if my audience is local?
Which free WordPress CDN option is best?
Why is my site slow despite a CDN?
