assileye.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 4.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
This is WordPress — the fixes below are one plugin away
- ✓WordPressWordPress 7.1.2
- →xSpeed Cache installedFree on wordpress.org — the setup wizard turns most of this report green.
- –MCP signal presentThe scan did not confirm MCP availability. Configure it in xSpeed → MCP Server, then verify authenticated access from an MCP client.
- –xSpeed Hub signalOptional: review Hub configuration and confirm authorized site membership at app.xspeedcache.com.
2 of these checks map to an xSpeed feature. Install the free xSpeed Cache plugin, connect its built-in MCP server, and your AI assistant can apply every fix and re-verify. If your AI already has access to the site (WP-CLI, SSH or hosting MCP), paste this:
My WordPress site assileye.com scored 98/100 on xSpeed Scan (https://xspeedcache.com/scan/r/assileye-com-507061bb04). Install and activate the free xSpeed Cache plugin from wordpress.org/plugins/xspeed, run "wp xspeed mcp connect" and give me the MCP URL to paste into my AI client. Then read the failing checks from https://xspeedcache.com/scan/r/assileye-com-507061bb04.md and apply the fixes: enable page caching, compression, minification and lazy loading, warm the cache, 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 · 40/40 pts earnedServer response & caching
6/6 checks passed · 30/30 pts earnedAsset optimization
5/5 checks passed · 20/20 pts earnedPlatform & xSpeed readiness
1/4 checks passed · 6/8 pts earnedAI prompt
Install xSpeed and use its Migration tool to import your current caching settings, then deactivate the old plugin.AI prompt
In xSpeed → MCP Server, click Connect and paste the config into your AI client — then ask it to fix this report.Past scans of assileye.com newest first · every report keeps its link
| Scanned | Score | Grade | Graded on | TTFB | Lighthouse | |
|---|---|---|---|---|---|---|
| 2026-09-26 03:40 UTC this report | 98 | A+ | desktop | 72ms | 100 | |
| 2026-09-24 09:32 UTC | 94 | A | desktop | 59ms | 100 | View report → |
| 2026-09-23 17:45 UTC | 82 | B | desktop | 69ms | 99 | View report → |