Managing Your Fleet with xSpeed Hub
Once your sites are attached to xSpeed Hub, the dashboard becomes mission control for the whole fleet: see every site’s cache health at a glance, drill into any of them, change settings remotely, and compare speed reports over time.
The fleet overview
The overview table lists every attached site, ranked worst-first. The site most in need of attention is always at the top. Each row carries health chips summarizing cache status, hit ratio, and any problems the daily check found.
Site drill-down
Click a site to open its drill-down:
- Live cache status: whether caching is on, pages cached, hit ratio, with an inline sparkline against the 80% hit-ratio target.
- Modules, every xSpeed Cache module on the site and its state.
- Settings, edit the site’s xSpeed Cache settings remotely. Edits are validated against the site’s own live settings schema, so the Hub can never write a value the plugin would reject.
- Reports, the site’s PageSpeed Insights and GTmetrix history. Pick any two runs and compare them side by side across score, LCP, TTFB, FCP, TBT, Speed Index, and CLS, with per-metric direction arrows. The run-history table has its own device filter, so you can look at desktop rows alone without changing what a new audit will measure.
Measuring a site
Analyze runs a real PageSpeed test on demand: mobile and desktop from one press, queued so the button answers immediately and the measuring continues in the background. A newly attached site is measured on arrival, so its first score is already on the dashboard. See Running Speed Tests in xSpeed Hub.
Note: Nothing on a schedule spends your audit quota. The daily pass reads the history your site already measured; an audit runs only when you press Analyze, or once when a site is first attached.
Recommendations
The recommendations center is a ranked next-best-action queue derived from the telemetry your sites already report: the changes most likely to improve each site, ordered by impact, many with one-click remote fixes.
Monitoring and alerts
The Hub takes a daily monitoring snapshot of every site and can alert you by Slack or email when something regresses: caching switched off, a hit ratio falling, a site unreachable. Site health checks are re-verified automatically every day.
Work you start yourself reports in the app rather than by email: a bell in the header collects results addressed to whoever started the job, a snackbar reports the start and the finish with a link to the result, and while the tab is in the background its title carries an unread count and its favicon a dot.
Purging from anywhere
Purge all sits in the top bar on every screen, not only Overview and Sites: clearing the cache is usually something you decide after doing something else, so it does not disappear when you navigate. It confirms before it runs, works through the fleet a few sites at a time so it never becomes a thundering herd at your origins, and reports per site: a fleet where one site is unreachable is a partial success, not a blanket “done”. Individual site rows keep their own Purge.
The activity log
Every tool call made through the Hub, by a person or by an AI, is recorded per account: what was run, on which site, by which connection, and whether it changed anything. When you manage many sites with many people and agents, this is how you answer “who changed that?”