How to clear cache (CDN & Cache Reserve)
Purge edge cache from my.swiftpress.io—entire domain or a path—and when to clear Redis Cache Reserve vs memory cache.
SwiftPress caches your WordPress site at the edge (CDN) so repeat visitors get fast responses and your origin does less work. By default, cached objects typically stay valid for about 24 hours unless they’re refreshed automatically, purged by you, or invalidated by the platform when content changes (exact behaviour can vary by content type and headers).
Sometimes you need to clear cache on purpose—for example after a major design change, fixing something that still looks “old,” or testing without stale assets.
Where to clear cache
- Sign in to my.swiftpress.io.
- Open your site.
- Find Clear cache (exact placement may be under Performance, CDN, or Advanced—labels can vary).
You’ll see options similar to:
Purge type
Entire domain
What it does: Purges all cached responses for your hostname (e.g. staging.yoursite.com or your live domain)—HTML, assets, the lot.
When to use: Global changes—new theme, site-wide rollout, or you’re unsure which path is stale.
Trade-off: Everyone gets cold cache for a while; first page loads can be slower until the edge rebuilds popularity.
Specific path
What it does: Clears cache only for a URL path you specify (e.g. /blog/my-post/ or a single asset path).
When to use: You changed one page or one CSS/JS file and don’t need to flush the whole site.
Trade-off: Narrower purge = less global slowdown; wrong path = you may need to purge again or widen to entire domain.
Also clear Cache Reserve (Redis)
You may see a control: Also clear Cache Reserve (Redis).
| Option | Effect |
|---|---|
| Checked | Clears persistent cache stored in Redis at the edge (Cache Reserve)—strongest “start fresh” for edge persistence. |
| Unchecked | Clears memory / non-Redis layers only—lighter touch; Redis-backed reserve data may remain until it expires naturally. |
Note: Some UIs note that clearing will also clear Cache Reserve (Redis) when that option applies—read the on-screen text at click time.
What the “slow until rebuild” message means
Purging immediately removes hot cached copies. For a short period:
- TTFB and asset loads may be higher while the CDN repopulates cache.
- This is normal—not a failure. Traffic warms the cache back up.
Avoid repeated full-site purges in a row unless you’re debugging—you’ll keep resetting performance.
Why we keep cache ~24 hours by default
- Speed — Most pages don’t change every second; long-lived cache = faster sites and lower load.
- Stability — Fewer origin hits during traffic spikes.
- Cost/efficiency — Edge bandwidth and PHP work stay predictable.
When you publish updates, many setups invalidate or shorten TTL for changed content automatically—but not every scenario is perfect. If you still see old content after a publish, a path or full purge is the right tool.
Good practice
- Try Specific path first if you know the URL.
- Use Entire domain when many paths look wrong or after migrations.
- Use Cache Reserve (Redis) clear when you’re sure edge persistence is holding something stale (aggressive).
- Don’t purge before every tiny edit—let normal cache and invalidation do most of the work.
Need help?
Use — same as the Support link in the site footer (opens the chat widget). You can also sign in at my.swiftpress.io. We don’t offer email support — see How to contact customer support. If something in this article doesn’t match your dashboard, and we’ll point you to the right screen.