CACHING

Edge-Fast Response Times

Three-layer caching architecture keeps every response blazing fast. KV cache for AI-optimized content, CDN edge cache for static assets, browser cache for returning visitors -- all automatic.

Enable CachingSee all features

Cache Layers

KV CacheCDN Edge CacheBrowser CacheCookie BypassCache Warming

Intelligent caching at every layer

Configure precisely how content is cached, warmed, and invalidated across the entire edge network.

Feature 01

CDN Cache Rules -- MIME-Type & Path Matching

Define granular caching rules based on MIME types with wildcard support and path patterns with glob matching. Each rule controls edge TTL, browser TTL, cache key configuration, and priority ordering. Toggle rules on and off without deleting them.

  • MIME-type wildcards: image/*, font/*, application/*
  • Path pattern globs: /static/*, /assets/**, /api/*
  • Per-rule edge TTL and browser Cache-Control
  • Priority ordering for overlapping rules
  • Cookie-based cache bypass for authenticated users

Edge cache rule

{
  edge_ttl:              2592000,  // 30 days
  cache_everything:      true,
  cache_key_ignore_qs:   true,
  bypass_on_cookie:      ['session', 'cart_id']
}

Default cache rules

MIME TypeEdge TTLBrowser TTL
image/*30 days7 days
text/css7 days1 day
application/javascript7 days1 day
font/*30 days30 days
application/json (/api/*)1 min0

Response headers

X-Cache-Rule: Images
X-Edge-TTL: 2592000
Cache-Control: public, max-age=604800
Vary: Accept-Encoding
cf-cache-status: HIT

Feature 02

Cache Population -- Sitemap-Based Warming

Proactively warm your cache by pointing Wrenda at your sitemap. Every URL gets pre-processed and cached before the first crawler even arrives. Schedule warming jobs to run on your cadence -- hourly, daily, or weekly.

  • Sitemap Discovery -- Automatically parse sitemap.xml and nested sitemap indexes
  • Scheduled Runs -- Configure warming cadence -- hourly, daily, or weekly cycles
  • Run History -- Track every warming job with URL counts, timing, and success rates
  • Priority Warming -- Warm high-traffic pages first based on analytics data

Three cache layers

Edge KV Cache

AI-optimized and pre-rendered content stored at the edge. Default 1-hour TTL, configurable per content rule. Fastest retrieval for transformed content.

CDN Edge Cache

Static assets cached at 300+ edge locations via cache rules. MIME-type rules control TTLs. Pass-through requests benefit from edge caching.

Browser Cache

Cache-Control headers instruct visitor browsers to cache locally. Reduces repeat requests entirely. Configurable per cache rule with separate browser TTL.

HOW IT WORKS

Cache lookup in milliseconds

Every request follows the same path. Cache hits return instantly. Misses are processed and cached for next time.

Step 01

Request hits the edge

Incoming requests are received at the nearest edge node. The URL path, MIME type, and user-agent are extracted for cache rule matching.

Step 02

Cache layer lookup

KV cache is checked for AI-optimized and pre-rendered content. CDN edge cache is checked for static assets. Priority-ordered rules determine which layer applies.

Step 03

Cache hit = instant response

On a hit, the cached content is served directly from the edge -- single-digit millisecond response times. Headers like X-Cache-Rule and cf-cache-status confirm the hit.

Step 04

Miss = process, cache, respond

On a miss, the origin is fetched, content is transformed (if AI/pre-render), stored in the appropriate cache layer, and response headers are set for browser caching.

USE CASES

Caching for every workload

From high-traffic media sites to API-heavy applications, multi-layer caching adapts to your needs.

High-Traffic Sites

Edge caching at 300+ locations means your content is always served from the node closest to the crawler. Global performance without global infrastructure.

  • Sub-10ms response times from edge cache
  • Automatic geographic distribution
  • No origin load during cache hits

E-Commerce & Media

Product images, CSS bundles, and font files cached for 30 days at the edge. Visitors and crawlers experience instant page loads on every visit.

  • Image/font caching with 30-day edge TTL
  • CSS/JS assets cached for 7 days
  • Cookie bypass for authenticated sessions

API Responses

Short-TTL caching for dynamic JSON endpoints. API responses cached for 1 minute at the edge reduce origin load while staying fresh for real-time data.

  • 1-minute edge TTL for /api/* paths
  • Cache key control with query string options
  • Vary header support for content negotiation
LIVE EXAMPLE

Cache headers you can verify

Every cached response includes diagnostic headers. Confirm cache hits, TTLs, and rule matches instantly.

cache-verification.sh
# Verify cache headers on a static asset
$ curl -I https://yoursite.com/images/hero.webp

# Response headers show cache status
HTTP/2 200
content-type: image/webp
x-cache-rule: Images
x-edge-ttl: 2592000
cache-control: public, max-age=604800
vary: Accept-Encoding
cf-cache-status: HIT
age: 14523

# Check AI-optimized content cache
$ curl -I -H "User-Agent: GPTBot/1.0" https://yoursite.com/

HTTP/2 200
x-ai-optimized: true
x-cache: HIT
x-cache-ttl: 3600

<5ms

Edge cache response

300+

Global edge nodes

99.9%

Cache hit ratio

FAQ

Edge Caching FAQs

How caching interacts with AI optimisation, pre-rendering and personalised content.

A regular CDN caches static files. Wrenda caches at the edge AND understands your traffic — it caches optimised AI-crawler HTML separately from pre-rendered Googlebot HTML separately from pass-through human traffic. Cache rules trigger on MIME type and path, with cookie-based bypass for personalised content.

Get Started

Stop serving cold cache misses

Enable multi-layer caching in minutes. Warm your cache proactively. Serve every request at edge speed.

Enable Caching

14-day free trial -- No credit card required