66of 100
63of 100
quirkycoolliving.com
DLevel 3 · Average
DLevel 3 · Average
WordPress⚡ xSpeed v1.4.1MCP signal present
854msTTFB
98Lighthouse desktop · graded
97Lighthouse mobile
302msLCP
0.01CLS
gzipCompression
MISSCache
Lab data: Lighthouse 13.5.0 desktop run, graded above · Reproduce this run on PageSpeed Insights ↗ · Mobile: 63 (D) —
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 63 (D) against 66 (D) 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).
854msTTFB
98Lighthouse desktop
97Lighthouse mobile · graded
2.0sLCP
0.00CLS
gzipCompression
MISSCache
Lab data: Lighthouse 13.5.0 mobile run, graded above · Reproduce this run on PageSpeed Insights ↗ · Desktop: 66 (D) —
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 66 (D) against
63 (D) 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+99
5/5 checks passed · 39.6/40 pts Jump to section ↓
Server response & cachingF35
2/5 checks passed · 9.5/27 pts Jump to section ↓
Asset optimizationD63
1/4 checks passed · 10/16 pts Jump to section ↓
Platform & xSpeed readinessF20
1/3 checks passed · 2/10 pts Jump to section ↓
Lab performance (Lighthouse)A+99
5/5 checks passed · 39.5/40 pts Jump to section ↓
Server response & cachingF35
2/5 checks passed · 9.5/27 pts Jump to section ↓
Asset optimizationF50
1/5 checks passed · 10/20 pts Jump to section ↓
Platform & xSpeed readinessF20
1/3 checks passed · 2/10 pts Jump to section ↓
Top fixes ranked by points recovered · desktop
Top fixes ranked by points recovered · mobile
MCP status reported — verify client access
- ✓WordPressDetected
- ✓xSpeed Cache installedv1.4.1
- ✓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.
10 of these checks map to an xSpeed feature. quirkycoolliving.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/quirkycoolliving-com-e651f090ad.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.Hosting is the other half — and 854ms to first byte says the origin is struggling.
xSpeed makes any host faster, but a cache is only as fast as the server behind a MISS. A TTFB this high usually means underpowered or oversold hosting.
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+
99/100
Lab performance (Lighthouse)
5/5 checks passed · 39.6/40 pts earned
Pass
Lighthouse performance score (desktop) 17.6/18 pts
98/100 (Lighthouse 13.5.0, desktop)
Guidelines: Lighthouse performance scoring
Pass
Largest Contentful Paint ≤ 2.5s 8/8 pts
LCP 302ms
Guidelines: web.dev — Largest Contentful Paint · Optimize LCP
Pass
Pass
Pass
F
35/100
Server response & caching
2/6 checks passed · 9.5/27 pts earned
Fail
Time to first byte ≤ 200ms 0/8 pts
TTFB 854ms 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 360ms from its own network — the gap between the two numbers is distance, not your server.
The server rebuilds the page on every request. A page cache answers in 5–15ms.
xSpeed Free
Page Cache
AI prompt
Using my site's xSpeed MCP connection: enable page caching and warm this page with the preloader, then re-check TTFB.Guidelines: web.dev — Time to First Byte
Fail
Page served from cache 0/7 pts
No cache evidence in headers or HTML
Serve HTML from a static cache instead of rebuilding it per visitor.
xSpeed Free
Page Cache + Preloader
AI prompt
Using my site's xSpeed MCP connection: enable page caching, start the preloader so pages are pre-warmed, and confirm get_cache_status reports hits.Guidelines: MDN — HTTP caching
Pass
HTML compression (bytes on the wire) 5/5 pts
Content-Encoding: gzip — 76KB on the wire (Brotli would be 77KB)
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: c6dd33010d8af518a5a01ac40cde1999.woff2, 392c61c7cf70c5642ad96811e6f535f0.css, 230a2c726b1c5d7316605843f3a21660.woff2…
Give CSS/JS/images long Cache-Control lifetimes so repeat views are free.
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 —
No CDN signature detected
Optional: put a CDN or Cloudflare in front for global edge delivery.
xSpeed Free
Cloudflare integration / CDN rewriter
AI prompt
Using my site's xSpeed MCP connection: connect Cloudflare (or configure the CDN rewriter) and purge, then re-scan.Guidelines: web.dev — Content delivery networks
Pass
Clean redirect chain 2/2 pts
No redirects — the URL answers directly
Guidelines: Lighthouse — Avoid redirects
D
63/100
Asset optimization
1/5 checks passed · 10/16 pts earned
Pass
No render-blocking resources 5/5 pts
Passes the Lighthouse audit
Guidelines: Lighthouse — Render-blocking resources
Partial
Minified CSS and JavaScript 2/4 pts
Lighthouse audit score 50% — 1 file: 392c61c7cf70c5642ad96811e6f535f0.css
Ship minified assets — whitespace and comments are pure transfer waste.
xSpeed Free
HTML/CSS/JS Minify
AI prompt
Using my site's xSpeed MCP connection: enable HTML, CSS and JS minification, purge the cache, and re-test.Guidelines: Lighthouse — Minify CSS · Minify JavaScript
Partial
Modern, optimized image formats 2/4 pts
Lighthouse audit score 50% — 5 files: What-Cartridge-Water-Filter-Removes-Sodium-quirkycoolliving.com_-300x300-480.jpg.bv.webp, portable-water-straw-filters.jpg-300x167.jpg, best-water-softener-with-carbon-filter-300x300.jpg.bv_resized_mobile.jpg.bv.webp…
Serve WebP/AVIF at the right compression — usually the single largest byte saving.
xSpeed Pro
Image Converter (WebP/AVIF)
AI prompt
Using my site's xSpeed MCP connection: enable WebP/AVIF conversion with URL rewriting, then re-test image audits.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
Partial
Total page weight (≤ 350KB for full marks) 1/3 pts
1054KB transferred — heavy: most WordPress pages this size fail mobile LCP
Page weight is what decides mobile LCP once the server is fast. Resize images to the size they display at, lazy-load below the fold, and drop scripts the page does not use.
xSpeed Free
Minify + Lazy Load + Image Converter (Pro)
AI prompt
Using my site's xSpeed MCP connection: enable minification and lazy loading (and image conversion on Pro), then re-check page weight.Guidelines: Lighthouse — Total byte weight
F
20/100
Platform & xSpeed readiness
1/4 checks passed · 2/10 pts earned
Info
Platform
WordPress detected (Site Kit by Google 1.189.0)
Informational.
Fail
Caching plugin active 0/4 pts
No caching plugin detected
WordPress rebuilds every page in PHP unless a caching plugin serves it statically.
xSpeed Free
xSpeed Cache (free on wordpress.org)
AI prompt
Install and activate the xSpeed plugin from wordpress.org, run its setup wizard, and enable page caching.Guidelines: WordPress.org — Optimization: caching
Fail
Powered by xSpeed 0/4 pts
xSpeed not detected
xSpeed bundles caching, minification, lazy-load, image optimization and a built-in MCP endpoint that requires an authenticated client for management actions; it also imports settings from other caching plugins in one click.
xSpeed Free
xSpeed Migration (one-click import)
AI prompt
Install xSpeed and use its Migration tool to import your current caching settings, then deactivate the old plugin.Guidelines: xSpeed — feature overview · xSpeed vs other cache plugins
Pass
xSpeed MCP route responded 2/2 pts
The public xSpeed MCP route returned its expected unauthenticated challenge. This confirms route responsiveness only; client authentication and control were not tested.
Guidelines: Model Context Protocol · xSpeed documentation
A+
99/100
Lab performance (Lighthouse)
5/5 checks passed · 39.5/40 pts earned
Pass
Lighthouse performance score (mobile) 17.5/18 pts
97/100 (Lighthouse 13.5.0, mobile)
Guidelines: Lighthouse performance scoring
Pass
Largest Contentful Paint ≤ 2.5s 8/8 pts
LCP 2.0s
Guidelines: web.dev — Largest Contentful Paint · Optimize LCP
Pass
Pass
Pass
F
35/100
Server response & caching
2/6 checks passed · 9.5/27 pts earned
Fail
Time to first byte ≤ 200ms 0/8 pts
TTFB 854ms 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 356ms from its own network — the gap between the two numbers is distance, not your server.
The server rebuilds the page on every request. A page cache answers in 5–15ms.
xSpeed Free
Page Cache
AI prompt
Using my site's xSpeed MCP connection: enable page caching and warm this page with the preloader, then re-check TTFB.Guidelines: web.dev — Time to First Byte
Fail
Page served from cache 0/7 pts
No cache evidence in headers or HTML
Serve HTML from a static cache instead of rebuilding it per visitor.
xSpeed Free
Page Cache + Preloader
AI prompt
Using my site's xSpeed MCP connection: enable page caching, start the preloader so pages are pre-warmed, and confirm get_cache_status reports hits.Guidelines: MDN — HTTP caching
Pass
HTML compression (bytes on the wire) 5/5 pts
Content-Encoding: gzip — 76KB on the wire (Brotli would be 77KB)
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: c6dd33010d8af518a5a01ac40cde1999.woff2, understanding-uv-water-purifiers-768x429.jpg, 392c61c7cf70c5642ad96811e6f535f0.css…
Give CSS/JS/images long Cache-Control lifetimes so repeat views are free.
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 —
No CDN signature detected
Optional: put a CDN or Cloudflare in front for global edge delivery.
xSpeed Free
Cloudflare integration / CDN rewriter
AI prompt
Using my site's xSpeed MCP connection: connect Cloudflare (or configure the CDN rewriter) and purge, then re-scan.Guidelines: web.dev — Content delivery networks
Pass
Clean redirect chain 2/2 pts
No redirects — the URL answers directly
Guidelines: Lighthouse — Avoid redirects
F
50/100
Asset optimization
1/5 checks passed · 10/20 pts earned
Pass
No render-blocking resources 5/5 pts
Passes the Lighthouse audit
Guidelines: Lighthouse — Render-blocking resources
Partial
Minified CSS and JavaScript 2/4 pts
Lighthouse audit score 50% — 1 file: 392c61c7cf70c5642ad96811e6f535f0.css
Ship minified assets — whitespace and comments are pure transfer waste.
xSpeed Free
HTML/CSS/JS Minify
AI prompt
Using my site's xSpeed MCP connection: enable HTML, CSS and JS minification, purge the cache, and re-test.Guidelines: Lighthouse — Minify CSS · Minify JavaScript
Partial
Modern, optimized image formats 2/4 pts
Lighthouse audit score 50% — 2 files: understanding-uv-water-purifiers-768x429.jpg, best-water-softener-with-carbon-filter-300x300.jpg.bv.webp
Serve WebP/AVIF at the right compression — usually the single largest byte saving.
xSpeed Pro
Image Converter (WebP/AVIF)
AI prompt
Using my site's xSpeed MCP connection: enable WebP/AVIF conversion with URL rewriting, then re-test image audits.Guidelines: Lighthouse — Modern image formats
Fail
LCP image discoverable early 0/4 pts
Fails the Lighthouse audit
The largest image must be in the HTML and preloaded — never lazy-loaded or script-injected.
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
Partial
Total page weight (≤ 350KB for full marks) 1/3 pts
1021KB transferred — heavy: most WordPress pages this size fail mobile LCP
Page weight is what decides mobile LCP once the server is fast. Resize images to the size they display at, lazy-load below the fold, and drop scripts the page does not use.
xSpeed Free
Minify + Lazy Load + Image Converter (Pro)
AI prompt
Using my site's xSpeed MCP connection: enable minification and lazy loading (and image conversion on Pro), then re-check page weight.Guidelines: Lighthouse — Total byte weight
F
20/100
Platform & xSpeed readiness
1/4 checks passed · 2/10 pts earned
Info
Platform
WordPress detected (Site Kit by Google 1.189.0)
Informational.
Fail
Caching plugin active 0/4 pts
No caching plugin detected
WordPress rebuilds every page in PHP unless a caching plugin serves it statically.
xSpeed Free
xSpeed Cache (free on wordpress.org)
AI prompt
Install and activate the xSpeed plugin from wordpress.org, run its setup wizard, and enable page caching.Guidelines: WordPress.org — Optimization: caching
Fail
Powered by xSpeed 0/4 pts
xSpeed not detected
xSpeed bundles caching, minification, lazy-load, image optimization and a built-in MCP endpoint that requires an authenticated client for management actions; it also imports settings from other caching plugins in one click.
xSpeed Free
xSpeed Migration (one-click import)
AI prompt
Install xSpeed and use its Migration tool to import your current caching settings, then deactivate the old plugin.Guidelines: xSpeed — feature overview · xSpeed vs other cache plugins
Pass
xSpeed MCP route responded 2/2 pts
The public xSpeed MCP route returned its expected unauthenticated challenge. This confirms route responsiveness only; client authentication and control were not tested.
Guidelines: Model Context Protocol · xSpeed documentation
Recently scanned public reports All public scans →
Click anywhere or press Esc to close![Full-size screenshot]()