traumaterapiakeskus.com
Lab data: Lighthouse 13.5.0 desktop run, graded above · Reproduce this run on PageSpeed Insights ↗
This Lighthouse run passes LCP, but real desktop Chrome users wait 3.0s for the largest paint. Google ranks on the real-user number.
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
- ✓WordPressDetected
- ✓xSpeed Cache installedv1.3.5 + Pro v1.2.5
- ✓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.
4 of these checks map to an xSpeed feature. traumaterapiakeskus.com'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/traumaterapiakeskus-com-7a54f147cb.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)
5/5 checks passed · 38.9/40 pts earnedServer 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
2/5 checks passed · 9.5/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: enable WebP/AVIF conversion with URL rewriting, then re-test image audits.AI prompt
Using my site's xSpeed MCP connection: enable minification and lazy loading (and image conversion on Pro), then re-check page weight.Platform & xSpeed readiness
3/4 checks passed · 10/10 pts earnedPast scans of traumaterapiakeskus.com newest first · every report keeps its link
| Scanned | Score | Grade | Graded on | TTFB | Lighthouse | |
|---|---|---|---|---|---|---|
| 2026-09-30 08:11 UTC | 85 | B | desktop | 101ms | 99 | View report → |
| 2026-09-26 03:17 UTC | 83 | B | desktop | 92ms | 94 | View report → |
| 2026-09-26 03:16 UTC this report | 83 | B | desktop | 101ms | 94 | |
| 2026-09-25 08:01 UTC | 84 | B | desktop | 93ms | 91 | View report → |
| 2026-09-25 08:00 UTC | 89 | B | desktop | 108ms | 98 | View report → |
| 2026-09-25 07:56 UTC | 79 | C | desktop | 98ms | 94 | View report → |
| 2026-09-25 07:54 UTC | 85 | B | desktop | 178ms | 100 | View report → |
| 2026-09-25 07:49 UTC | 85 | B | desktop | 95ms | 97 | View report → |
| 2026-09-25 07:45 UTC | 85 | B | desktop | 178ms | 98 | View report → |
| 2026-09-25 07:39 UTC | 76 | C | desktop | 107ms | 75 | View report → |