97of 100
97of 100
demo.clonewith.ai
A+Level 5 · Instant
A+Level 5 · Instant
WordPress 7.1.2⚡ xSpeed v1.3.3Cloudflare
142msTTFB
100Lighthouse desktop · graded
100Lighthouse mobile
287msLCP
0.00CLS
brCompression
HITCache
Lab data: Lighthouse 13.5.0 desktop run, graded above · Reproduce this run on PageSpeed Insights ↗ · Mobile: 97 (A+) —
Real visitors (Chrome UX Report)
Not enough Chrome traffic for field data on this page or its site, so only the lab run above is available.
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 97 (A+) against 97 (A+) 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).
142msTTFB
100Lighthouse desktop
100Lighthouse mobile · graded
971msLCP
0.00CLS
brCompression
HITCache
Lab data: Lighthouse 13.5.0 mobile run, graded above · Reproduce this run on PageSpeed Insights ↗ · Desktop: 97 (A+) —
Real visitors (Chrome UX Report)
Not enough Chrome traffic for field data on this page or its site, so only the lab run above is available.
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 97 (A+) against
97 (A+) 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).
Lab performance (Lighthouse)A+100
5/5 checks passed · 40/40 pts Jump to section ↓
Server response & cachingA91
4/5 checks passed · 24.5/27 pts Jump to section ↓
Asset optimizationA+100
4/4 checks passed · 16/16 pts Jump to section ↓
Platform & xSpeed readinessA+100
2/2 checks passed · 8/8 pts Jump to section ↓
Lab performance (Lighthouse)A+100
5/5 checks passed · 40/40 pts Jump to section ↓
Server response & cachingA91
4/5 checks passed · 24.5/27 pts Jump to section ↓
Asset optimizationA+100
4/4 checks passed · 16/16 pts Jump to section ↓
Platform & xSpeed readinessA+100
2/2 checks passed · 8/8 pts Jump to section ↓
Top fixes ranked by points recovered · desktop
Top fixes ranked by points recovered · mobile
xSpeed is installed — verify its MCP endpoint before automating
- ✓WordPressWordPress 7.1.2
- ✓xSpeed Cache installedv1.3.3
- →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.
demo.clonewith.ai already runs xSpeed Cache v1.3.3, but the report did not confirm its MCP availability. In wp-admin open xSpeed → MCP Server → Connect (or run `wp xspeed mcp connect`), then verify the endpoint and authenticated client access before using this prompt:
My WordPress site demo.clonewith.ai runs xSpeed Cache and scored 97/100 (https://xspeedcache.com/scan/r/demo-clonewith-ai-c3e181bc11). Once I've configured and authenticated your MCP connection, read the failing checks from https://xspeedcache.com/scan/r/demo-clonewith-ai-c3e181bc11.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.Hosting is the other half.
xSpeed makes any host faster, but a cache is only as fast as the server behind a MISS.
xCloud — managed hosting from the team behind xSpeed — gives the cache an origin tuned for it, with agent/MCP access built in and bring-your-own-server pricing.
Explore xCloud.host →
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.
A+
100/100
Lab performance (Lighthouse)
5/5 checks passed · 40/40 pts earned
Pass
Lighthouse performance score (desktop) 18/18 pts
100/100 (Lighthouse 13.5.0, desktop)
Guidelines: Lighthouse performance scoring
Pass
Largest Contentful Paint ≤ 2.5s 8/8 pts
LCP 287ms
Guidelines: web.dev — Largest Contentful Paint · Optimize LCP
Pass
Pass
Pass
A
91/100
Server response & caching
4/6 checks passed · 24.5/27 pts earned
Pass
Time to first byte ≤ 200ms 8/8 pts
TTFB 142ms measured from Vilnius, Lithuania (EU) (best of 2 requests). This includes the network round trips between us and your origin, not just server time. Google measured your server responding in 6ms from its own network — the gap between the two numbers is distance, not your server.
Guidelines: web.dev — Time to First Byte
Pass
Page served from cache 7/7 pts
Cache HIT evidence in response headers
Guidelines: MDN — HTTP caching
Pass
HTML compression (bytes on the wire) 5/5 pts
Content-Encoding: br — 36KB on the wire (gzip would be 38KB)
Guidelines: MDN — Content-Encoding · RFC 7932 — Brotli
Partial
Efficient cache policy on static assets 2.5/5 pts
Lighthouse cache-policy audit score 50% — 8 files: faviconV2 (t2.gstatic.com), faviconV2 (t0.gstatic.com), faviconV2 (t2.gstatic.com)…
Every asset with a short cache lifetime here is served by another host (t2.gstatic.com, t0.gstatic.com, t3.gstatic.com). Their Cache-Control is not yours to set — this check will not clear while you load them.
xSpeed Free
Browser Cache
AI prompt
Using my site's xSpeed MCP connection: enable browser-cache headers for static assets, then re-run the audit.Guidelines: Lighthouse — Efficient cache policy
Info
CDN edge serves the page —
Cloudflare forwarded this request upstream (`cf-cache-status: DYNAMIC`).
Let Cloudflare cache HTML for visitors who are not logged in: a Cache Rule set to "Eligible for cache" that bypasses the logged-in, cart and comment cookies. The edge then answers pages near the visitor instead of sending each one to your server.
xSpeed Free
Cloudflare integration
AI prompt
Using my site's xSpeed MCP connection: check whether Cloudflare is caching HTML for this site, and if it is not, tell me the Cache Rule to add and purge Cloudflare once it is in place.Guidelines: web.dev — Content delivery networks
Pass
Clean redirect chain 2/2 pts
No redirects — the URL answers directly
Guidelines: Lighthouse — Avoid redirects
A+
100/100
Asset optimization
4/5 checks passed · 16/16 pts earned
Pass
No render-blocking resources 5/5 pts
Passes the Lighthouse audit
Guidelines: Lighthouse — Render-blocking resources
Pass
Minified CSS and JavaScript 4/4 pts
Passes the Lighthouse audit
Guidelines: Lighthouse — Minify CSS · Minify JavaScript
Pass
Modern, optimized image formats 4/4 pts
Passes the Lighthouse audit
Guidelines: Lighthouse — Modern image formats
Info
LCP image discoverable early —
Audit not reported for this page
Re-run when Lighthouse is available.
xSpeed Free
Resource Hints (preload) + Lazy Load exclusions
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.Guidelines: web.dev — Optimize LCP · Lighthouse — LCP request discovery
Pass
Total page weight (≤ 350KB for full marks) 3/3 pts
93KB transferred — light enough that weight is unlikely to be what slows mobile LCP
Guidelines: Lighthouse — Total byte weight
A+
100/100
Platform & xSpeed readiness
2/4 checks passed · 8/8 pts earned
Info
Platform
WordPress detected (WordPress 7.1.2)
Informational.
Pass
Caching plugin active 4/4 pts
xSpeed Cache (xSpeed signature: v1.3.3)
Guidelines: WordPress.org — Optimization: caching
Pass
Powered by xSpeed 4/4 pts
xSpeed signature: v1.3.3
Guidelines: xSpeed — feature overview · xSpeed vs other cache plugins
Info
xSpeed MCP route response not confirmed —
This scan did not confirm an xSpeed MCP route response. Client authentication and control were not tested.
Configure an MCP client for this endpoint and verify authenticated access before relying on it to inspect or change the site.
xSpeed Free
MCP Server (built into xSpeed Free)
AI prompt
In xSpeed → MCP Server, click Connect and paste the config into your AI client — then ask it to fix this report.Guidelines: Model Context Protocol · xSpeed documentation
A+
100/100
Lab performance (Lighthouse)
5/5 checks passed · 40/40 pts earned
Pass
Lighthouse performance score (mobile) 18/18 pts
100/100 (Lighthouse 13.5.0, mobile)
Guidelines: Lighthouse performance scoring
Pass
Largest Contentful Paint ≤ 2.5s 8/8 pts
LCP 971ms
Guidelines: web.dev — Largest Contentful Paint · Optimize LCP
Pass
Pass
Pass
A
91/100
Server response & caching
4/6 checks passed · 24.5/27 pts earned
Pass
Time to first byte ≤ 200ms 8/8 pts
TTFB 142ms measured from Vilnius, Lithuania (EU) (best of 2 requests). This includes the network round trips between us and your origin, not just server time. Google measured your server responding in 5ms from its own network — the gap between the two numbers is distance, not your server.
Guidelines: web.dev — Time to First Byte
Pass
Page served from cache 7/7 pts
Cache HIT evidence in response headers
Guidelines: MDN — HTTP caching
Pass
HTML compression (bytes on the wire) 5/5 pts
Content-Encoding: br — 36KB on the wire (gzip would be 38KB)
Guidelines: MDN — Content-Encoding · RFC 7932 — Brotli
Partial
Efficient cache policy on static assets 2.5/5 pts
Lighthouse cache-policy audit score 50% — 8 files: faviconV2 (t3.gstatic.com), faviconV2 (t2.gstatic.com), faviconV2 (t1.gstatic.com)…
Every asset with a short cache lifetime here is served by another host (t3.gstatic.com, t2.gstatic.com, t1.gstatic.com). Their Cache-Control is not yours to set — this check will not clear while you load them.
xSpeed Free
Browser Cache
AI prompt
Using my site's xSpeed MCP connection: enable browser-cache headers for static assets, then re-run the audit.Guidelines: Lighthouse — Efficient cache policy
Info
CDN edge serves the page —
Cloudflare forwarded this request upstream (`cf-cache-status: DYNAMIC`).
Let Cloudflare cache HTML for visitors who are not logged in: a Cache Rule set to "Eligible for cache" that bypasses the logged-in, cart and comment cookies. The edge then answers pages near the visitor instead of sending each one to your server.
xSpeed Free
Cloudflare integration
AI prompt
Using my site's xSpeed MCP connection: check whether Cloudflare is caching HTML for this site, and if it is not, tell me the Cache Rule to add and purge Cloudflare once it is in place.Guidelines: web.dev — Content delivery networks
Pass
Clean redirect chain 2/2 pts
No redirects — the URL answers directly
Guidelines: Lighthouse — Avoid redirects
A+
100/100
Asset optimization
4/5 checks passed · 16/16 pts earned
Pass
No render-blocking resources 5/5 pts
Passes the Lighthouse audit
Guidelines: Lighthouse — Render-blocking resources
Pass
Minified CSS and JavaScript 4/4 pts
Passes the Lighthouse audit
Guidelines: Lighthouse — Minify CSS · Minify JavaScript
Pass
Modern, optimized image formats 4/4 pts
Passes the Lighthouse audit
Guidelines: Lighthouse — Modern image formats
Info
LCP image discoverable early —
Audit not reported for this page
Re-run when Lighthouse is available.
xSpeed Free
Resource Hints (preload) + Lazy Load exclusions
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.Guidelines: web.dev — Optimize LCP · Lighthouse — LCP request discovery
Pass
Total page weight (≤ 350KB for full marks) 3/3 pts
93KB transferred — light enough that weight is unlikely to be what slows mobile LCP
Guidelines: Lighthouse — Total byte weight
A+
100/100
Platform & xSpeed readiness
2/4 checks passed · 8/8 pts earned
Info
Platform
WordPress detected (WordPress 7.1.2)
Informational.
Pass
Caching plugin active 4/4 pts
xSpeed Cache (xSpeed signature: v1.3.3)
Guidelines: WordPress.org — Optimization: caching
Pass
Powered by xSpeed 4/4 pts
xSpeed signature: v1.3.3
Guidelines: xSpeed — feature overview · xSpeed vs other cache plugins
Info
xSpeed MCP route response not confirmed —
This scan did not confirm an xSpeed MCP route response. Client authentication and control were not tested.
Configure an MCP client for this endpoint and verify authenticated access before relying on it to inspect or change the site.
xSpeed Free
MCP Server (built into xSpeed Free)
AI prompt
In xSpeed → MCP Server, click Connect and paste the config into your AI client — then ask it to fix this report.Guidelines: Model Context Protocol · xSpeed documentation
Past scans of demo.clonewith.ai newest first · every report keeps its link
| Scanned | Score | Grade | Graded on | TTFB | Lighthouse | |
|---|---|---|---|---|---|---|
| 2026-10-10 19:43 UTC | 72 | C | desktop | 151ms | 78 | View report → |
| 2026-10-10 19:41 UTC | 83 | B | desktop | 142ms | 98 | View report → |
| 2026-10-10 19:40 UTC | 97 | A+ | desktop | 159ms | 100 | View report → |
| 2026-10-10 19:38 UTC this report | 97 | A+ | desktop | 142ms | 100 | |
| 2026-10-10 19:37 UTC | 97 | A+ | desktop | 136ms | 100 | View report → |
| 2026-10-10 19:36 UTC | 94 | A | desktop | 136ms | 99 | View report → |
| 2026-10-10 19:35 UTC | 95 | A | desktop | 141ms | 100 | View report → |
| 2026-10-10 19:34 UTC | 95 | A | desktop | 157ms | 100 | View report → |
| 2026-10-10 19:33 UTC | 89 | B | desktop | 135ms | 100 | View report → |
| 2026-10-10 19:32 UTC | 95 | A | desktop | 189ms | 100 | View report → |
Recently scanned public reports All public scans →
Click anywhere or press Esc to close![Full-size screenshot]()