Running Speed Tests in xSpeed Hub
Analyze runs a real PageSpeed test on a site from inside the Hub — mobile and desktop from one press — and tells you when the result is ready, wherever you happen to be in the app by then.
What this does
Press Analyze on a site row, on a site’s own page, or on its Reports tab, and the Hub queues a PageSpeed audit against that site. The press answers immediately; the measuring happens in the background.
One press covers both devices. They run one after the other rather than at once — firing two audits at one origin from a single address is exactly the burst Google’s shared rate limit exists to prevent. A real WordPress page takes roughly 45 seconds per device, so expect a couple of minutes for the pair.
If one device succeeds and the other fails, the Hub keeps the score it got and reports the failure beside it. You get the half that worked rather than a clean failure for both.
Results land in the site’s Reports history like any other run, so a fresh audit can be compared against any earlier one across score, LCP, TTFB, FCP, TBT, Speed Index, and CLS.
Why use it
The button used to be called Test, and it did not run a speed test. On a site row it read the site’s configuration — “cache on · 87% hit ratio” — beside a score ring, which is a different thing wearing the name of a measurement; on a site’s own page it repeated what the Live status panel below it was already showing. Both now measure. Cache state is still on screen where it always was.
Being told when it finishes
Because the work outlives the press that started it, the Hub now says so in three places:
- The bell in the header — audit results land there, addressed to whoever pressed the button, and are readable from anywhere in the app.
- A snackbar — one when the audit starts, one when it finishes, with a link straight to the report. If you have moved to another tab, the finish message is held rather than spent on a tab nobody is looking at, so coming back still shows you what happened.
- The browser tab itself — the title carries an unread count and the favicon gets a dot. Both appear only while the tab is in the background, and both clear the moment you come back to it.
A new site is measured on arrival
When you attach a site, the Hub audits it straight away, so its first score is already on the dashboard rather than waiting for someone to find the Analyze button.
Local and development sites are skipped — PageSpeed runs on Google’s infrastructure and cannot reach an address that only exists on your machine. Attach one and it appears with no score until you measure it from somewhere reachable.
Filtering the run history
The Reports tab’s run-history table has its own device filter. Choosing Desktop there shows desktop rows and hides mobile ones, which is what a control sitting above a table is expected to do.
Troubleshooting
Analyze is disabled or says a run is already in progress. One audit per site at a time. If the Hub restarted mid-run, the leftover is cleared within five minutes and the button frees itself — you do not need to do anything.
A site shows a score for one device and an error for the other. That is the intended reporting: the measurement that succeeded is kept. Run Analyze again for another attempt at the one that failed.
A local site never gets a score. Expected — see above. Nothing is wrong with the attachment.