Overview
A publication and an online shop have different caching needs. When planning delivery with WAFGO, consider both efficient public content delivery and isolation of signed-in user data.
Align cache boundaries with application behavior
Start with theme assets and media before evaluating public HTML caching. Requests involving identity, checkout or live inventory need explicit bypass rules.
| Content | Suggested policy | What to verify |
|---|---|---|
| Theme and plugin assets | Version-based caching | Asset URLs after updates |
| Public articles and categories | Cache and purge around publishing | Comments, languages and previews |
| Login, account, cart and checkout | Bypass shared caching | User isolation and order consistency |
Tidy up media, fonts and theme assets
Oversized images, duplicate theme scripts and excessive fonts can undermine delivery improvements. Include them in the same integration review.
- Check image sizes and crops instead of using originals in small display areas.
- Review resource URLs to prevent HTTPS pages from loading legacy HTTP assets.
- Avoid overlapping plugin features and review how new cache or image plugins interact with existing rules.
Coordinate publishing, access and protection
Security policies should distinguish administration from the public site. Tighten sensitive entry points while preserving editing, previews and legitimate business notifications.
- For paid courses and member videos, verify media segments, captions and playback authorization separately; signing into a page does not protect its media files.
Purge after publishing
Define the article, homepage, listing and related assets that need purging to prevent stale content from surviving elsewhere.
Administration protection
Evaluate access controls, rate limits and challenges around real editor workflows rather than blocking administration indiscriminately.
Plugin compatibility
Test payment, membership, search and multilingual plugins. This guide does not claim an unverified official one-click plugin.
Implementation & checks
- 01
Record the current setup
Record the site URLs, DNS records and plugin configuration.
- 02
Test representative journeys
Check caching as a visitor, editor and customer.
- 03
Launch gradually
Move static assets first, then evaluate appropriate page caching.