Caching
MagicWP gives each site two cache layers you control from your site → Caching. Turn them on for speed, and flush them whenever you need fresh output.
Object cache (Redis)
Caches database queries and PHP objects in Redis so repeated work isn't redone on every request — a big win for dynamic, database-heavy sites.
- Enable Object Cache — toggle it on. The first time, MagicWP installs the Redis cache plugin and wires it up for you.
- Flush Cache — clear the object cache (available once it's enabled).
Page cache (nginx)
Stores fully-rendered HTML pages at the server (nginx). Cached pages are served instantly, without running PHP or touching the database.
- Enable Page Cache — toggle it on.
- Flush Cache — clear all cached pages.
- Change Caching Expiration — set how long pages stay cached (the TTL). Presets range from 1 hour (default) to 1 year (1h, 2h, 4h, 8h, 24h, 7 days, 30 days, 1 year). Saving a new expiration also flushes the cache.
Flushing from anywhere
You can also flush both caches from the site's Tools → Flush cache. Each cache can only be flushed while it's enabled.
Tips
- Enable the page cache for sites that are mostly static — it's the biggest speed win.
- Enable the object cache to cut database load on dynamic sites.
- Flush after big changes — a theme/plugin update, a bulk content edit, or a search & replace — so visitors see the new version. (Search & replace flushes both caches for you.)
- Use a longer expiration for content that rarely changes; a shorter one if you publish often.
Cached pages can hide recent edits
If a change isn't showing on the live site, flush the page cache (or wait for the expiration). Logged-in/admin views bypass the page cache, so what you see in wp-admin can differ from a logged-out visitor until you flush.