35of 100
20of 100
2unboss.today
FLevel 1 · Critical
FLevel 1 · Critical
WordPress 7.1.3⚡ xSpeed detected
18.1sTTFB
35Lighthouse desktop · graded
18Lighthouse mobile
2.7sLCP
0.89CLS
gzipCompression
MISSCache
Lab data: Lighthouse 13.5.0 desktop run, graded above · Reproduce this run on PageSpeed Insights ↗ · Mobile: 20 (F) —
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 20 (F) against 35 (F) 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).
18.1sTTFB
35Lighthouse desktop
18Lighthouse mobile · graded
12.1sLCP
1.01CLS
gzipCompression
MISSCache
Lab data: Lighthouse 13.5.0 mobile run, graded above · Reproduce this run on PageSpeed Insights ↗ · Desktop: 35 (F) —
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 35 (F) against
20 (F) 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)F42
1/5 checks passed · 16.8/40 pts Jump to section ↓
Server response & cachingF30
1/5 checks passed · 8/27 pts Jump to section ↓
Asset optimizationF0
0/5 checks passed · 0/20 pts Jump to section ↓
Platform & xSpeed readinessA+100
2/2 checks passed · 8/8 pts Jump to section ↓
Lab performance (Lighthouse)F8
0/5 checks passed · 3.2/40 pts Jump to section ↓
Server response & cachingF30
1/5 checks passed · 8/27 pts Jump to section ↓
Asset optimizationF0
0/5 checks passed · 0/20 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.3
- ✓xSpeed Cache installedDetected — update xSpeed to report its version here
- →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 (this xSpeed version does not report Hub status).
2unboss.today already runs xSpeed Cache, 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 2unboss.today runs xSpeed Cache and scored 35/100 (https://xspeedcache.com/scan/r/2unboss-today-27acb8df89). Once I've configured and authenticated your MCP connection, read the failing checks from https://xspeedcache.com/scan/r/2unboss-today-27acb8df89.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 — and 18.1s 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.
F
42/100
Lab performance (Lighthouse)
1/5 checks passed · 16.8/40 pts earned
Fail
Lighthouse performance score (desktop) 6.3/18 pts
35/100 (Lighthouse 13.5.0, desktop)
The composite Lighthouse score — every fix below moves it.
xSpeed Free
AI Optimize
AI prompt
Using my site's xSpeed MCP connection: run optimize_site, then run_benchmark to verify the score improved.Guidelines: Lighthouse performance scoring
Partial
Largest Contentful Paint ≤ 2.5s 4/8 pts
LCP 2.7s
Serve the hero content faster: cache the page, preload the LCP image, and ship critical CSS.
xSpeed Free
Page Cache + Preloader (Critical CSS in Pro)
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.Guidelines: web.dev — Largest Contentful Paint · Optimize LCP
Fail
Cumulative Layout Shift ≤ 0.1 0/5 pts
CLS 0.895
Reserve space for images/embeds so the page does not jump as it loads.
xSpeed Free
Lazy Load — CLS fix (adds width/height)
AI prompt
Using my site's xSpeed MCP connection: enable lazy loading with the CLS fix so images reserve their space, then re-test CLS.Guidelines: web.dev — Cumulative Layout Shift
Partial
Total Blocking Time ≤ 200ms 2.5/5 pts
TBT 363ms
Less JavaScript on the main thread: defer scripts and drop unused bundles.
xSpeed Free
JS Minify + Defer
AI prompt
Using my site's xSpeed MCP connection: enable JS minification and deferred loading, then re-test Total Blocking Time.Guidelines: web.dev — Total Blocking Time
Pass
F
30/100
Server response & caching
1/6 checks passed · 8/27 pts earned
Fail
Time to first byte ≤ 200ms 0/8 pts
TTFB 18.1s measured from Vilnius, Lithuania (EU) (best of 1 requests). This includes the network round trips between us and your origin, not just server time. Google measured your server responding in 8ms 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
Partial
Page served from cache 3.5/7 pts
Caching layer present (xSpeed Cache) but this response was not a cache hit
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
Partial
HTML compression (bytes on the wire) 2.5/5 pts
Served as gzip: 31KB. The same page as Brotli is 27KB — 3.4KB smaller on every uncached view.
Your server can produce a much smaller Brotli response but serves gzip. Prefer Brotli for HTML.
xSpeed Free
GZIP (Brotli in Pro)
AI prompt
Using my site's xSpeed MCP connection: check how the HTML is compressed, make sure the served encoding is the smaller of gzip and Brotli, then confirm the response size.Guidelines: MDN — Content-Encoding · RFC 7932 — Brotli
Fail
Efficient cache policy on static assets 0/5 pts
Fails the Lighthouse cache-policy audit — 8 files: fontawesome.min.js, mkb.jpg, featured-image-3.jpg…
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
0/100
Asset optimization
0/5 checks passed · 0/20 pts earned
Fail
No render-blocking resources 0/5 pts
Fails the Lighthouse audit — 8 files: jquery-ui.css, cms-navigation-base.css, pum-site-styles.css… · ~600ms of first paint
CSS/JS in <head> blocks first paint. Inline the critical CSS and defer the rest.
xSpeed Pro
Critical CSS + Unused CSS removal
AI prompt
Using my site's xSpeed MCP connection: generate critical CSS for the top pages and enable unused-CSS removal, then re-test.Guidelines: Lighthouse — Render-blocking resources
Fail
Minified CSS and JavaScript 0/4 pts
Fails the Lighthouse audit — 8 files: linoor-main.css, style.css, jquery.fancybox.js…
Ship minified assets. Note that 2 of these come from another host and are not yours to minify — that part of the audit will not clear.
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
Fail
Modern, optimized image formats 0/4 pts
Fails the Lighthouse audit — 5 files: mkb.jpg, featured-image-2.jpg, featured-image-6.jpg… · ~150ms of first paint
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
Fail
Total page weight (≤ 350KB for full marks) 0/3 pts
3.6MB transferred — over 1,500KB
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
A+
100/100
Platform & xSpeed readiness
2/4 checks passed · 8/8 pts earned
Info
Platform
WordPress detected (WordPress 7.1.3)
Informational.
Pass
Caching plugin active 4/4 pts
xSpeed Cache (X-XSpeed-Cache: BYPASS)
Guidelines: WordPress.org — Optimization: caching
Pass
Powered by xSpeed 4/4 pts
X-XSpeed-Cache: BYPASS
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
F
8/100
Lab performance (Lighthouse)
0/5 checks passed · 3.2/40 pts earned
Fail
Lighthouse performance score (mobile) 3.2/18 pts
18/100 (Lighthouse 13.5.0, mobile)
The composite Lighthouse score — every fix below moves it.
xSpeed Free
AI Optimize
AI prompt
Using my site's xSpeed MCP connection: run optimize_site, then run_benchmark to verify the score improved.Guidelines: Lighthouse performance scoring
Fail
Largest Contentful Paint ≤ 2.5s 0/8 pts
LCP 12.1s
Serve the hero content faster: cache the page, preload the LCP image, and ship critical CSS.
xSpeed Free
Page Cache + Preloader (Critical CSS in Pro)
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.Guidelines: web.dev — Largest Contentful Paint · Optimize LCP
Fail
Cumulative Layout Shift ≤ 0.1 0/5 pts
CLS 1.008
Reserve space for images/embeds so the page does not jump as it loads.
xSpeed Free
Lazy Load — CLS fix (adds width/height)
AI prompt
Using my site's xSpeed MCP connection: enable lazy loading with the CLS fix so images reserve their space, then re-test CLS.Guidelines: web.dev — Cumulative Layout Shift
Fail
Total Blocking Time ≤ 200ms 0/5 pts
TBT 623ms
Less JavaScript on the main thread: defer scripts and drop unused bundles.
xSpeed Free
JS Minify + Defer
AI prompt
Using my site's xSpeed MCP connection: enable JS minification and deferred loading, then re-test Total Blocking Time.Guidelines: web.dev — Total Blocking Time
Fail
First Contentful Paint ≤ 1.8s 0/4 pts
FCP 3.5s
First paint is gated on server response and render-blocking CSS.
xSpeed Free
Page Cache + CSS Minify
AI prompt
Using my site's xSpeed MCP connection: enable page caching and CSS minification, then re-test First Contentful Paint.Guidelines: web.dev — First Contentful Paint
F
30/100
Server response & caching
1/6 checks passed · 8/27 pts earned
Fail
Time to first byte ≤ 200ms 0/8 pts
TTFB 18.1s measured from Vilnius, Lithuania (EU) (best of 1 requests). This includes the network round trips between us and your origin, not just server time. Google measured your server responding in 9ms 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
Partial
Page served from cache 3.5/7 pts
Caching layer present (xSpeed Cache) but this response was not a cache hit
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
Partial
HTML compression (bytes on the wire) 2.5/5 pts
Served as gzip: 31KB. The same page as Brotli is 27KB — 3.4KB smaller on every uncached view.
Your server can produce a much smaller Brotli response but serves gzip. Prefer Brotli for HTML.
xSpeed Free
GZIP (Brotli in Pro)
AI prompt
Using my site's xSpeed MCP connection: check how the HTML is compressed, make sure the served encoding is the smaller of gzip and Brotli, then confirm the response size.Guidelines: MDN — Content-Encoding · RFC 7932 — Brotli
Fail
Efficient cache policy on static assets 0/5 pts
Fails the Lighthouse cache-policy audit — 8 files: fontawesome.min.js, mkb.jpg, featured-image-3.jpg…
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
0/100
Asset optimization
0/5 checks passed · 0/20 pts earned
Fail
No render-blocking resources 0/5 pts
Fails the Lighthouse audit — 8 files: jquery.min.js, pum-site-styles.css, cms-navigation-base.css… · ~3.0s of first paint
CSS/JS in <head> blocks first paint. Inline the critical CSS and defer the rest.
xSpeed Pro
Critical CSS + Unused CSS removal
AI prompt
Using my site's xSpeed MCP connection: generate critical CSS for the top pages and enable unused-CSS removal, then re-test.Guidelines: Lighthouse — Render-blocking resources
Fail
Minified CSS and JavaScript 0/4 pts
Fails the Lighthouse audit — 8 files: linoor-main.css, style.css, jquery.fancybox.js…
Ship minified assets. Note that 2 of these come from another host and are not yours to minify — that part of the audit will not clear.
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
Fail
Modern, optimized image formats 0/4 pts
Fails the Lighthouse audit — 3 files: mkb.jpg, featured-image-2.jpg, image-20230220-110652.png · ~300ms of first paint
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
Fail
Total page weight (≤ 350KB for full marks) 0/3 pts
3.6MB transferred — over 1,500KB
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
A+
100/100
Platform & xSpeed readiness
2/4 checks passed · 8/8 pts earned
Info
Platform
WordPress detected (WordPress 7.1.3)
Informational.
Pass
Caching plugin active 4/4 pts
xSpeed Cache (X-XSpeed-Cache: BYPASS)
Guidelines: WordPress.org — Optimization: caching
Pass
Powered by xSpeed 4/4 pts
X-XSpeed-Cache: BYPASS
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
Recently scanned public reports All public scans →
Click anywhere or press Esc to close![Full-size screenshot]()