CDN basics: when edge caching helps NZ visitors
Short answer: A CDN caches static assets closer to visitors—useful for global audiences and traffic spikes; less transformative if 100% of visitors are local and your origin is already fast.
NZ businesses still benefit when assets are large, when you use overseas origins, or when you want WAF features bundled with some providers.
What CDNs cache well
- Images, CSS, JavaScript, fonts.
- Some HTML on highly static pages—if configured carefully.
What still hits your origin
Logged-in admin, highly dynamic cart flows, and poorly configured cache headers can bypass edge benefits.
Pitfalls for WordPress
Over-aggressive page caching with cart fragments can break WooCommerce—use provider recipes or experienced setup.
Frequently asked questions
Will a CDN fix a slow database?
No—it masks some symptoms. Fix query and plugin issues at the source.
Do we need a CDN for a five-page site?
Optional—measure first. Good hosting and image discipline may suffice.