TL;DR Edge Cache
Edge caching is the practice of storing copies of your web pages and assets on servers that are physically close to your visitors, so that when someone requests a page, they receive it from a nearby cache rather than from your origin server on the other side of the world. This dramatically reduces load times because the data travels a much shorter distance, and it reduces the load on your origin server because most requests never reach it at all. CloudSonic's edge cache is configured to serve full cached pages to logged-out visitors while automatically bypassing the cache for logged-in users, WooCommerce cart pages, and other dynamic content. It works in combination with our CDN and anycast network to deliver the fastest possible experience globally.
How Edge Cache Works
When a visitor requests a page from your website, the request first arrives at the nearest edge node on the network. The edge cache checks whether it has a stored copy of that page. If it does, it serves the cached copy immediately without contacting your origin server at all. This is called a cache hit and it is the fastest possible response because no PHP processing, no database queries, and no origin server round trip are involved. If the edge cache does not have a copy, it forwards the request to your origin server, receives the response, serves it to the visitor, and stores a copy in cache for future requests. This first request is called a cache miss. After that, the same page is served from cache for every subsequent visitor near that edge node until the cache expires or is purged.
Cache rules determine which pages are cached and for how long. Static assets like images, CSS, and JavaScript are cached aggressively because they rarely change. Full HTML pages are more nuanced. Pages that are the same for every visitor, like a blog post or a homepage, are excellent candidates for full page caching. Pages that are personalised, like a logged-in user's dashboard or a WooCommerce cart, must bypass the cache entirely. CloudSonic's edge cache is pre-configured to handle these rules correctly for WordPress and WooCommerce out of the box, so you get the performance benefits of aggressive caching without serving the wrong content to the wrong visitor.
Why Edge Caching Matters for Your Website
The performance gap between a cached and uncached page response is not marginal, it is transformational. An uncached WordPress page requires PHP execution, multiple database queries, plugin processing, and template rendering before a response can be sent. This process typically takes between 200 milliseconds and several seconds depending on the complexity of the page and the server's current load. A cached page served from the edge cache requires none of that. The response is served from memory on a server close to the visitor in single-digit milliseconds. For high-traffic sites this difference also extends to server load. A site receiving ten thousand visitors per hour without edge caching requires the origin server to process ten thousand PHP requests per hour. With edge caching serving 90 percent of those from cache, the origin server only processes one thousand. This reduction in server load means better performance during traffic spikes and lower resource consumption overall, which directly affects hosting costs and reliability.
