CDN Configuration and Tuning
A CDN put in front of your existing origin and actually tuned: cache rules per path, TLS at the edge, compression, asset handling, and origin shielding so that a cache miss does not turn into a stampede. It is a one-time configuration job, measured against your real traffic rather than switched on and left alone.
What you get
- A CDN in front of one origin, with TLS terminated at the edge and plain HTTP redirected
- Cache rules written per path, including what must never be cached — sessions, carts, anything with a logged-in person behind it
- Compression, asset handling and origin shielding configured and tested
- Before-and-after figures from your own traffic: cache hit ratio and origin load, measured rather than asserted
- The configuration documented, including how to purge the cache when you ship a change
What this does not cover
- The provider's own bill — the CDN account stays yours, and what you are buying is the work of configuring it
- Making a slow application fast: an edge cannot cache what is personal to each visitor, so if the first byte is slow the origin is the problem — that is Performance Optimization Audit
- WAF rule tuning and DDoS escalation, which run on the same edge but are separate services: Managed WAF Ruleset and DDoS Mitigation Standby
- Ongoing tuning as the site changes; this is a one-time pass, not a subscription
Who it fits
A site with real traffic, one origin and nothing in front of it. If you are already on Growth Managed Hosting, CDN management is part of that plan; and if the goal is security rather than speed, buy Managed WAF Ruleset instead, because a CDN on its own is not a security control.