Edge HTML Cache
Dramatically improve Time-To-First-Byte (TTFB) by caching fully modified HTML pages directly on SerpWise Edge nodes.
The Edge HTML Cache stores the final, modified output of your website's pages directly on our globally distributed Edge Gateway nodes. When a visitor requests a page that is already cached, SerpWise returns the response instantly—without ever fetching data from your origin server or re-running the Rules Engine.
This drops your Time-To-First-Byte (TTFB) down to roughly 1-5 milliseconds, which is a powerful Google ranking signal.
How it Works
When a visitor requests a page:
- Cache Miss: If the page isn't cached, SerpWise fetches the page from your origin, applies all your SEO Rules, Code Injection, and Headers, and then saves the final generated HTML string to memory before returning it to the user.
- Cache Hit: If the page is already in the cache and hasn't expired, SerpWise bypasses the origin entirely and returns the cached HTML.
Edge Caching only applies to GET and HEAD requests for HTML documents. Requests for Javascript, CSS, Images, or POST/PUT requests are automatically passed through to your origin untouched.
Configuring the Cache
You can enable and configure Edge Caching in your Domain Dashboard under the Edge Cache tab.
Default TTL
The "Time To Live" (TTL) defines how long a page stays in the cache before it is considered stale. If you set it to 3600, pages will be fetched fresh from your origin every hour.
E-Commerce Bypasses
For dynamic websites like e-commerce stores (Shopify, WooCommerce, Custom Apps), caching HTML can be dangerous if the page contains user-specific data (like a shopping cart or account dashboard).
SerpWise allows you to explicitly bypass the cache using two methods:
1. Bypass Paths
Any request matching these paths will never be cached and will always hit your origin server.
- Use exact matches:
/cart - Use wildcards:
/checkout/*
2. Bypass Cookies
If a visitor has any of the defined cookies in their browser, they will always see the live, uncached version of the site. This is perfect for logged-in users.
- Use exact matches:
session_id - Use prefix wildcards:
wordpress_logged_in_*
Purging the Cache
If you update content on your origin server and need to clear the SerpWise Edge Cache immediately:
- Go to the Edge Cache tab.
- Click the Purge Cache button in the top right.
- Your cache will be globally invalidated across all Edge nodes within 60 seconds.
You can automate cache warming after a purge by using the Edge Crawler & Indexer.
Cache Analytics
At the top of the Edge Cache tab, you'll see a real-time dashboard of your cache performance:
- Hit Rate: The percentage of eligible requests served from the Edge instead of your origin.
- Bandwidth Saved: The total MBs/GBs of traffic offloaded from your servers.
- Avg Hit/Miss Latency: A direct comparison of your TTFB when SerpWise handles the request from memory versus fetching from your origin.