Mamba’s page cache delivers instant load times for shoppers by serving prebuilt HTML for key storefront pages, while keeping dynamic and user-specific content out of cache for safety. It is the foundation of Mamba’s performance boost and is designed to be fast, safe, and accurate by default.

---

What’s Cached

Mamba caches the high-value, static storefront pages that make up the bulk of shopper traffic:

• Homepage and Shop
• Product pages
• Category and Tag archives

Only guest users are eligible for page cache, and only GET/HEAD requests are stored. This ensures cache never interferes with authenticated sessions or actions that mutate data.

---

Variants Served Automatically

Mamba automatically serves the right version of each page depending on the visitor’s context:

• Device: desktop vs mobile
• Language: multilingual stores (Polylang, WPML, etc.)
• Currency: multi-currency setups
• Country/Tax: when geolocation affects pricing/taxes
• Tax Display: inclusive vs exclusive

These dimensions mirror the storefront your shoppers actually see, without falling back to broad cookie-based Vary headers that would cause variant explosion and reduced hit rates.

---

What’s Not Cached

To maintain correctness and privacy, the following contexts are always bypassed:

• Logged-in or admin sessions
• Cart, Checkout, and My Account pages
• Search results
• URLs performing mutating actions (add to cart, apply/remove coupon, etc)
• Responses that explicitly declare “don’t cache” (e.g. no-store/private), set cookies, are compressed at the origin, or return non-200 status codes

---

Safety and Correctness

Mamba’s page cache is designed with guardrails that prevent common pitfalls:

• Do-not-store honored: pages with no-store/private headers are never cached
• Cookie and compression safety: responses that set cookies or send compressed payloads are excluded
• Host protection: non-canonical domains are rejected to prevent cache poisoning
• Cookie-based bypass: you can configure personalization cookies that force cache bypass
• Cart detection: if a visitor has a cart, pages that depend on cart state are excluded to avoid caching dynamic totals and pricing

---

How It Feels in Practice

• The first visit to a cached page returns a fast HIT immediately.
• Prices, stock, and filters always reflect the visitor’s real context (device, language, currency, geolocation, tax).
• Dynamic flows like cart and checkout always remain real-time and uncached for correctness.

---