---
title: "Edge HTML Cache - Serpwise Documentation"
description: "Dramatically improve Time-To-First-Byte (TTFB) by caching fully modified HTML pages directly on Serpwise Edge nodes."
url: "https://serpwise.ai/docs/edge-cache/"
source: "https://serpwise.ai/docs/edge-cache/"
---
[Back to Serpwise](/)

Serpwise Documentation

Connect · Configure · Execute

Search documentation

`/`

No documentation found.

↑↓ Navigate Enter to open

Browse documentation

The Edge HTML Cache stores the final, modified output of your website’s pages on distributed Edge Gateway nodes. When a visitor requests an eligible page that is already cached, Serpwise can return that response without fetching it from the origin or re-running the Rules Engine.

This can reduce Time to First Byte (TTFB) by removing origin work from a cache hit. Actual response time depends on the visitor’s location, network path, cache state, and edge processing. The primary benefits are faster delivery, more consistent performance, and lower origin load.

## How it Works

When a visitor requests a page:

1. **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.
2. **Cache Hit:** If the page is already in the cache and hasn’t expired, Serpwise bypasses the origin entirely and returns the cached HTML.

## 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:

1. Go to the **Edge Cache** tab.
2. Click the **Purge Cache** button in the top right.
3. Your cache will be globally invalidated across all Edge nodes within 60 seconds.

## 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.