Multisite Network Dashboard (Pro)
See the cache state of every site in your WordPress Multisite network from one screen, and clear the cache per site or across the whole network.
What this does
The Multisite module adds a Network panel that lists every site in your network. For each site it shows the cache state and recent cache activity, so you can check the health of the whole network in one place.
From the same panel you can purge (clear) the cache for a single site, or purge every site in the network at once.
This module only does something on a real Multisite network. On a standalone install the panel shows a “network install only” empty state.
Why use it
On a large network, checking each site one by one is slow. This gives you a single view of cache status across all sites and a way to clear caches without switching between admin areas.
Requirements
- xSpeed Cache Pro must be active.
- WordPress must be running as a Multisite network.
Note: On a standalone (single-site) install, the Network row stays visible but the panel reports that this is not a network install.
What each site row shows
For every site in the network, the panel reports:
- Site name and URL
- Cache state — whether page caching is on or off
- Hits (24h) — cache hits in the last 24 hours
- Misses (24h) — cache misses in the last 24 hours
- Hit ratio — the share of requests served from cache
- Active modules — how many xSpeed Cache modules are configured on that site
How to view the network
- Open the xSpeed Cache dashboard in your Network Admin.
- Go to the Multisite (Network) panel.
- The panel loads the first page of sites. Additional pages load on demand as you browse.
Note: Sites are loaded in pages of 20 by default. Loading every site at once would be slow on a large network, so the panel fetches more sites as you need them.
How to purge the cache
Purge a single site
- Find the site in the list.
- Use its purge action to clear that site’s cache.
- The result tells you whether the cache was cleared.
Purge the whole network
- Use the network-wide purge action.
- Every site’s cache is cleared in turn.
- The result shows how many sites were purged successfully out of the total.
Tip: Network-wide purge is fast because it only deletes cache files. Even so, on very large networks it works through sites in batches rather than all at once.
Command line
If you prefer WP-CLI, the module adds the xspeed network command:
wp xspeed network list— list every site with its cache state, 24-hour hits, and hit ratio.wp xspeed network purge— purge every site in the network.wp xspeed network purge --blog=<id>— purge a single site by its blog ID.
Note: These commands only run on a Multisite network. On a standalone install they report that the install is not a network.
Best practices
- Use the network view to spot sites where caching is off or the hit ratio is low.
- Prefer per-site purge after updating one site, and network-wide purge only when a change affects every site.
Troubleshooting
The panel says this is a network install only. The module needs a real WordPress Multisite network. On a single-site install there is nothing for it to show.
A site shows cache off. That site does not have page caching enabled. Enable caching on the site itself.
A purge did not clear a site. The result marks that site as failed. The site may have been unreachable, or its cache could not be cleared at that moment. Try again.
FAQ
How many sites load at once? The panel loads 20 sites per page by default and fetches more as you browse.
Can I purge one site without affecting the others?
Yes. Each site has its own purge action, and the WP-CLI command accepts a --blog=<id> option.
Related
- White-Label Branding
- How to Purge the Cache