xsdev.1wp.site
Lab data: Lighthouse 13.5.0 desktop run, graded above · Reproduce this run on PageSpeed Insights ↗
Why is this different from the score in my browser?
The graded score is the desktop run. Lighthouse 13.5.0 runs at Google through the PageSpeed Insights API on a desktop profile with no CPU or network throttling — close to what Chrome DevTools on a laptop, GTmetrix's default test and the PageSpeed API (which defaults to desktop) all measure, so this is the number you should be able to reproduce: run it yourself on PageSpeed Insights.
Google ranks on mobile. That run happens too, on an emulated mid-range Android with a 4× CPU slowdown and a throttled connection, and the same page routinely scores 30–50 points lower there. Neither number is wrong — they are different tests.
Lighthouse also varies a few points run to run on the same URL. Treat a trend across several scans as the signal, never a single digit.
Lab data: Google PageSpeed Insights (Lighthouse, desktop). Server probes (TTFB, compression, cache, headers) are measured separately from Vilnius, Lithuania (EU).
Top fixes ranked by points recovered
MCP status reported — verify client access
- ✓WordPressWordPress 7.1.2
- ✓xSpeed Cache installedv1.3.6 + Pro v1.1.3
- ✓MCP signal presentThe report indicates MCP availability. This does not verify client authentication or control.
- →xSpeed Hub signalOptional: review Hub configuration and confirm authorized site membership at app.xspeedcache.com (this xSpeed version does not report Hub status).
5 of these checks map to an xSpeed feature. xsdev.1wp.site's report indicates that xSpeed MCP is available. This scan did not verify client credentials; if your client is configured and authenticated, use this prompt:
If you are authenticated to my site's xSpeed MCP server, read the failing checks from https://xspeedcache.com/scan/r/xsdev-1wp-site-c5a4670012.md, apply the fixes: enable page caching, compression, minification and lazy loading, warm the cache, then run a benchmark and re-scan at https://xspeedcache.com/scan to confirm the score improved.Run this scan without the form
Plug xSpeed Scan into your agent stack, or test any site from a chat.
Connect this scanner to your AI assistant
Free. No API key, no sign-up. Scan any public site and get the same graded report as this one, with the fix for every failing check.
Endpoint
https://xspeedcache.com/scan/mcpClaude Code — one command
claude mcp add --transport http xspeed-scan https://xspeedcache.com/scan/mcpClaude Desktop, Cursor, or any MCP client — add to your config
{
"mcpServers": {
"xspeed-scan": {
"type": "http",
"url": "https://xspeedcache.com/scan/mcp"
}
}
}run_speed_scanScan any public URL and return this whole graded report.get_speed_scanRead a scan already run, by its id.
Lab performance (Lighthouse)
3/5 checks passed · 30/40 pts earnedAI prompt
Using my site's xSpeed MCP connection: run optimize_site, then run_benchmark to verify the score improved.AI prompt
Using my site's xSpeed MCP connection: enable lazy loading with the CLS fix so images reserve their space, then re-test CLS.Server response & caching
5/6 checks passed · 25/30 pts earnedAI prompt
Using my site's xSpeed MCP connection: enable browser-cache headers for static assets, then re-run the audit.Asset optimization
3/5 checks passed · 11/20 pts earnedAI prompt
Using my site's xSpeed MCP connection: generate critical CSS for the top pages and enable unused-CSS removal, then re-test.AI prompt
Using my site's xSpeed MCP connection: preload the LCP image for this page and exclude it from lazy loading, then re-test LCP.Platform & xSpeed readiness
3/4 checks passed · 10/10 pts earnedPast scans of xsdev.1wp.site newest first · every report keeps its link
| Scanned | Score | Grade | Graded on | TTFB | Lighthouse | |
|---|---|---|---|---|---|---|
| 2026-09-29 05:07 UTC | 65 | D | mobile | 127ms | 53 | View report → |
| 2026-09-29 05:07 UTC | 75 | C | desktop | 135ms | 69 | View report → |
| 2026-09-29 05:03 UTC this report | 76 | C | desktop | 136ms | 72 | |
| 2026-09-29 04:56 UTC | 76 | C | desktop | 108ms | 73 | View report → |
| 2026-09-29 04:55 UTC | 76 | C | desktop | 135ms | 73 | View report → |
| 2026-09-03 17:40 UTC | 75 | C | mobile | 151ms | 57 | View report → |
Reports graded on different runs are not a trend: mobile-graded rows are the older rubric's headline, desktop-graded rows the current one. Compare like with like.