Overview
WAFGO brings delivery and security into the same request path. Start by finding where visitors wait, then use separate policies for cacheable assets, dynamic pages and business-critical requests.
Match caching to each request
A page contains HTML, scripts, fonts, images and personalized data. Their update cycles and access boundaries differ, so a single cache policy rarely fits them all.
Versioned assets
Give versioned scripts, styles and images longer cache lifetimes, then publish updates at new URLs to reduce repeated origin requests.
Public pages
Set caching and purge rules around publishing frequency, accounting for language, query parameters and device variations where needed.
Personalized requests
Keep account pages, carts and authenticated responses out of shared caches, with explicit handling of cookies and authorization.
Reduce payloads before tuning delivery
A CDN improves the delivery path, while the page still needs sensible payloads. Prioritize oversized hero images, blocking scripts and unused fonts to improve the experience visitors actually receive.
- Serve images sized for the screen and reserve their layout space.
- Render critical content first and defer offscreen media and optional interactions.
- Use HTTPS consistently and check cross-origin fonts, cache headers and redirect chains.
Keep protection and a rollback path
Observe traffic before tightening security rules. Use normal visitor journeys as a baseline and check that WAF policies, rate limits and access controls preserve crawling, payment callbacks and form submissions.
Protect the origin
Review historical DNS records and bypass routes, then restrict direct origin access as appropriate for the deployment.
Measure the result
Compare load time, hit ratio, errors and origin traffic across the same regions and devices rather than relying on one speed test.
Controlled rollout
Keep the original DNS and cache policies, validate a test hostname, and roll out gradually with a documented recovery path.
Implementation & checks
- 01
Inventory resources
Identify public, private, frequently updated and large resources.
- 02
Configure a pilot
Configure a test hostname, origin, TLS and cache policies.
- 03
Verify and switch
Test core journeys before updating DNS and monitoring errors and cache behavior.