Cache Website
This page explains the Cache Website screen in the GoAdmio Admin Panel. It lets you configure full-page HTML caching per domain, so frequently requested pages are served from a cached copy instead of being regenerated by PHP on every request.
Location: Admin Panel → Domains → Cache Website
Location (User Panel): Domains → Cache Website
Overview
Full-page caching stores the rendered HTML of a page and serves it directly to visitors for a configurable period (the Cache TTL). This dramatically reduces PHP and MySQL load and is one of the most effective ways to speed up a website without changing application code.
The Cache Website page lists every domain on the server and lets you:
- Enable or disable caching per domain
- Set a Cache TTL (how long a cached page is served before it is regenerated)
- Set a Length (cache size or page length limit — 0 = no limit)
- Configure URL Exclude rules for paths that must never be cached
- Purge Cache for a domain to force regeneration
What the Page Shows
| Column | Description |
|---|---|
| Domain | The domain whose cache is being configured |
| Cache TTL | Seconds a cached page is served before regeneration (e.g., 86400 = 24 hours) |
| Length | Cache length limit (0 = no limit) |
| URL Exclude | Paths excluded from caching (e.g., admin, cart, login, checkout) |
| Active | Whether caching is enabled for the domain (checkbox or toggle) |
| Purge Cache | Button to clear all cached pages for the domain |
Fields Explained
Cache TTL
Time-to-live for a cached page, in seconds.
| Value | Meaning |
|---|---|
| 0 | Caching disabled for the domain (or always regenerate) |
| 3600 | 1 hour |
| 86400 | 24 hours (default) |
| 604800 | 7 days |
> Tip: Start with 3600 (1 hour) for sites with frequent content updates. Use 86400 or higher for static sites where content rarely changes. Lower the TTL if visitors report stale content.
Length
A size or length limit for the cache (0 = no limit).
> Note: The exact meaning depends on the cache backend (e.g., maximum cached page size, or number of cached entries). Leave at 0 unless you have a specific reason to cap it.
URL Exclude
A comma-separated or newline-separated list of URL patterns that must not be cached.
Common exclusions:
| Path | Why exclude |
|---|---|
| admin | Admin panel must always be fresh and user-specific |
| wp-admin | WordPress admin area |
| wp-login.php | Login pages must never be cached |
| login, signin | Authentication pages |
| cart, checkout | Per-user shopping cart |
| my-account | Logged-in customer area |
| api | API endpoints must return live data |
| * (or specific query strings) | Pages with query parameters that change content |
> Warning: Excluding too little can cause logged-in users to see another user's cached page — a serious privacy and security issue. Always exclude authentication, account, cart, and admin paths.
Active
Enables or disables caching for the domain without deleting its cache configuration.
> Tip: You can temporarily disable caching to debug a content issue, then re-enable it once resolved.
Purge Cache
Clears all cached pages for the domain. The next visitor triggers a fresh generation.
> Tip: Purge after publishing major content changes, changing the theme, or updating plugins that affect page output.
How to Enable Caching for a Domain
- Log in to the GoAdmio Admin Panel (or User Panel).
- Navigate to Domains → Cache Website.
- Locate the domain in the list.
- Set Cache TTL (e.g.,
86400for 24 hours,3600for 1 hour). - Set Length (leave
0unless required). - Enter URL Exclude paths (
admin, login, cart, checkout, my-account, api). - Check Active.
- Click Save (or the save icon).
How to Purge the Cache
- Open Domains → Cache Website.
- Locate the domain.
- Click Purge Cache.
- Confirm if prompted.
> Tip: Consider purging after deploying code changes, changing the theme, or installing/updating plugins — otherwise visitors may see old HTML for up to one TTL period.
Recommended Settings by Site Type
| Site type | Cache TTL | URL Exclude |
|---|---|---|
| Static brochure site | 86400 (24 h) | admin |
| Blog / news | 3600 (1 h) | admin, login, preview |
| WordPress | 3600 – 86400 | wp-admin, wp-login.php, cart, checkout, my-account |
| WooCommerce | 1800 – 3600 | wp-admin, wp-login.php, cart, checkout, my-account, api |
| Documentation | 86400 | admin, search |
| API backend | 0 (disabled) | — |
| Logged-in dashboard | 0 (disabled) | — |
> Note: Always combine full-page caching with application-level cache invalidation (e.g., a WordPress cache plugin that purges the full-page cache when content changes). Otherwise visitors may see stale content until the TTL expires.
Interoperability
Full-page caching works best when combined with:
| Layer | Purpose |
|---|---|
| Browser caching | Static assets (CSS, JS, images) cached client-side via .htaccess headers |
| Object caching | Redis or Memcached for database query results — see /go/dynacache |
| OPcache | PHP bytecode cache — enabled at the PHP level |
| CDN | Edge caching for static and dynamic content — see Cloudflare Proxy |
> Tip: GoAdmio's /go/dynacache command configures Redis object caching for domains, which complements full-page caching.
Related Pages
- DNS Manager — DNS records for the domain
- Install Free SSL Certificate — HTTPS for cached pages
- Change Document Root — where the site is served from
- Cloudflare Proxy — edge caching and CDN
- Apache Configuration — web server caching headers
- PHP Configuration — PHP-level caching directives
- Website Time — timezone shown to visitors
Troubleshooting
| Problem | Likely cause | Solution |
|---|---|---|
| Logged-in users see another user's page | Authentication/account paths not excluded | Add login, my-account, cart, checkout, wp-admin to URL Exclude |
| Content changes not appearing | Cached page still within TTL | Click Purge Cache; lower TTL for frequently updated sites |
| Admin panel is broken or outdated | Admin path cached | Exclude admin and wp-admin from caching |
| Cart empties or items disappear | Cart pages cached | Exclude cart, checkout, my-account |
| Caching has no performance effect | PHP or database is not the bottleneck | Check Apache Status and Process Monitor; consider CDN or Redis |
| Site shows old theme after update | Theme assets and HTML cached | Purge cache; also clear browser and CDN caches |
| API returns stale data | API endpoint cached | Add api (or specific endpoints) to URL Exclude |
| Cache grows very large | No Length limit | Set a reasonable Length, or lower TTL |
Last updated: 2026-11-08