embedpress.com
Lab data: Lighthouse 13.5.0 desktop run, graded above · Reproduce this run on PageSpeed Insights ↗ · Mobile: 71 (C) —
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. On this page the mobile run scored 71 (C) against 88 (B) here — to see every check graded on that run.
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).
Lab data: Lighthouse 13.5.0 mobile run, graded above · Reproduce this run on PageSpeed Insights ↗ · Desktop: 88 (B) —
Why is this different from the score in my browser?
This view grades the mobile run. Lighthouse 13.5.0 runs at Google through the PageSpeed Insights API on an emulated mid-range Android with a 4× CPU slowdown and a throttled connection. Chrome DevTools on your own machine, on the Desktop preset, applies almost none of that, and the same page routinely scores 30–50 points higher there. Neither number is wrong — they are different tests.
Mobile is what Google ranks on, so this is the number that affects your
search performance. On this page the desktop run scored 88 (B) against
71 (C) here —
to see every check graded on that run. To reproduce it, open the same run on PageSpeed Insights,
or pass strategy=mobile to the PageSpeed API — it defaults to desktop.
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, mobile). Server probes (TTFB, compression, cache, headers) are measured separately from Vilnius, Lithuania (EU).
Top fixes ranked by points recovered · desktop
Top fixes ranked by points recovered · mobile
Fix this report with one prompt
- ✓WordPressDetected
- ✓xSpeed Cache installedv1.3.5 + Pro v1.2.5
- ✓MCP server connectedLive — your AI assistant can control the cache
- ✓xSpeed Hub attachedAttached — one AI connection manages this and every other site
4 of these checks map to an xSpeed feature. embedpress.com's xSpeed MCP server is live — paste this into Claude (or any MCP client) connected to it:
Connect to my site's xSpeed MCP server, read the failing checks from https://xspeedcache.com/scan/r/embedpress-com-d1d758afe7.md, and 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.
Core Web Vitals & lab metrics
5/5 checks passed · 39.3/40 pts earnedServer response & caching
4/6 checks passed · 23/27 pts earnedAI prompt
Using my site's xSpeed MCP connection: enable page caching and warm this page with the preloader, then re-check TTFB.AI prompt
Using my site's xSpeed MCP connection: connect Cloudflare (or configure the CDN rewriter) and purge, then re-scan.Asset optimization
3/5 checks passed · 13/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.Platform & xSpeed readiness
3/4 checks passed · 10/10 pts earnedCore Web Vitals & lab metrics
2/5 checks passed · 20.8/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 page caching, start the preloader, and (on Pro) generate critical CSS for this page; then re-test LCP.AI prompt
Using my site's xSpeed MCP connection: enable page caching and CSS minification, then re-test First Contentful Paint.Server response & caching
4/6 checks passed · 23/27 pts earnedAI prompt
Using my site's xSpeed MCP connection: enable page caching and warm this page with the preloader, then re-check TTFB.AI prompt
Using my site's xSpeed MCP connection: connect Cloudflare (or configure the CDN rewriter) and purge, then re-scan.Asset optimization
4/5 checks passed · 15/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.Platform & xSpeed readiness
3/4 checks passed · 10/10 pts earnedPast scans of embedpress.com newest first · every report keeps its link
| Scanned | Score | Grade | Graded on | TTFB | Lighthouse | |
|---|---|---|---|---|---|---|
| 2026-09-23 07:43 UTC this report | 88 | B | desktop | 318ms | 96 | |
| 2026-09-19 12:45 UTC | 84 | B | desktop | 338ms | 96 | View report → |
| 2026-09-19 03:57 UTC | 69 | D | mobile | 331ms | 71 | View report → |
| 2026-09-19 01:37 UTC | 61 | D | mobile | 325ms | 56 | View report → |
| 2026-09-18 18:34 UTC | 62 | D | mobile | 428ms | 60 | View report → |
| 2026-09-18 18:32 UTC | 64 | D | mobile | 447ms | 57 | View report → |
| 2026-09-18 18:13 UTC | 67 | D | mobile | 322ms | 61 | View report → |
| 2026-09-18 17:29 UTC | 69 | D | mobile | 381ms | 70 | View report → |
| 2026-09-18 17:17 UTC | 67 | D | mobile | 420ms | 61 | View report → |
| 2026-09-18 16:34 UTC | 60 | D | mobile | 386ms | 53 | 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.