1. Static assets
CSS, JavaScript, icons, fallback images, and theme images should use long browser cache rules and CDN delivery because they rarely change.
RX GLOBAL DELIVERY
Plan how RX medical knowledge should travel faster from server to CDN edge to patient device, while keeping admin, login, previews, comments, and dynamic actions safe.
CSS, JavaScript, icons, fallback images, and theme images should use long browser cache rules and CDN delivery because they rarely change.
Homepage, article pages, guides, hubs, and archives can use page cache for visitors. Logged-in users should usually bypass full-page cache.
Never cache WordPress admin, login, preview links, comment actions, cart/checkout pages, or pages with private user-specific content.
| Area | Suggested delivery | Important safety note |
|---|---|---|
| Theme CSS/JS/images | CDN + long browser cache | Use versioned file names or query version after update. |
| Article pages | Page cache + CDN edge cache | Purge cache after article update or review change. |
| Medical hub pages | Page cache with short-to-medium TTL | Refresh after publishing many new posts. |
| Search pages | Usually bypass full page cache | Search results can be dynamic and query-specific. |
| Admin/login/preview | No cache | Protect editing, security, and private sessions. |
Cache public HTML for anonymous visitors only. Bypass cache when WordPress cookies are present, when URL contains preview, or when the path starts with /wp-admin/, /wp-login.php, or checkout/cart paths.
Use Gzip/Brotli compression, HTTP/2 or HTTP/3 when available, object cache for database pressure, and image optimization for slow mobile connections.