69of 100
60of 100
studio51.co.za
DLevel 3 · Average
DLevel 3 · Average
WordPress⚡ xSpeed detected
1.9sTTFB
92Lighthouse desktop · graded
84Lighthouse mobile
602msLCP
0.01CLS
gzipCompression
MISSCache
Lab data: Lighthouse 13.5.0 desktop run, graded above · Reproduce this run on PageSpeed Insights ↗ · Mobile: 60 (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 60 (D) against 69 (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).
1.9sTTFB
92Lighthouse desktop
84Lighthouse mobile · graded
3.2sLCP
0.05CLS
gzipCompression
MISSCache
Lab data: Lighthouse 13.5.0 mobile run, graded above · Reproduce this run on PageSpeed Insights ↗ · Desktop: 69 (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 69 (D) against
60 (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+97
5/5 checks passed · 38.6/40 pts Jump to section ↓
Server response & cachingD60
3/4 checks passed · 12/20 pts Jump to section ↓
Asset optimizationF10
0/5 checks passed · 2/20 pts Jump to section ↓
Platform & xSpeed readinessA+100
2/2 checks passed · 8/8 pts Jump to section ↓
Lab performance (Lighthouse)C78
2/5 checks passed · 31.1/40 pts Jump to section ↓
Server response & cachingD60
3/4 checks passed · 12/20 pts Jump to section ↓
Asset optimizationF10
0/5 checks passed · 2/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
- ✓WordPressDetected
- ✓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).
studio51.co.za 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 studio51.co.za runs xSpeed Cache and scored 69/100 (https://xspeedcache.com/scan/r/studio51-co-za-07584f1c24). Once I've configured and authenticated your MCP connection, read the failing checks from https://xspeedcache.com/scan/r/studio51-co-za-07584f1c24.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 1.9s 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+
97/100
Lab performance (Lighthouse)
5/5 checks passed · 38.6/40 pts earned
Pass
Lighthouse performance score (desktop) 16.6/18 pts
92/100 (Lighthouse 13.5.0, desktop)
Guidelines: Lighthouse performance scoring
Pass
Largest Contentful Paint ≤ 2.5s 8/8 pts
LCP 602ms
Guidelines: web.dev — Largest Contentful Paint · Optimize LCP
Pass
Pass
Pass
D
60/100
Server response & caching
3/6 checks passed · 12/20 pts earned
Fail
Time to first byte ≤ 200ms 0/8 pts
TTFB 1.9s 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 1ms 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
N/A
Page served from cache —
Correctly per-visitor — this response is marked `no-cache, must-revalidate, max-age=0, no-store, private`, so it must not be held in a shared cache.
Nothing to fix. If parts of this page are the same for everyone, they can still be cached separately — but the page as a whole is right to opt out.
Guidelines: MDN — HTTP caching
Pass
HTML compression (bytes on the wire) 5/5 pts
Content-Encoding: gzip — 2.2KB on the wire (Brotli would be 2.0KB)
Guidelines: MDN — Content-Encoding · RFC 7932 — Brotli
Pass
Efficient cache policy on static assets 5/5 pts
Passes the Lighthouse cache-policy 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
10/100
Asset optimization
0/5 checks passed · 2/20 pts earned
Fail
No render-blocking resources 0/5 pts
Fails the Lighthouse audit — 5 files: jquery.js, style.css, frontend.js… · ~1.0s of first paint
Inline the critical CSS and defer the rest. Note that one of these comes from another host, so deferring it is the only lever you have.
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 — 1 file: jquery.js
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
Fail
Modern, optimized image formats 0/4 pts
Fails the Lighthouse audit — 1 file: NEW-LOGO-26-300x300-1.png · ~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
Partial
Total page weight (≤ 350KB for full marks) 2/3 pts
533KB transferred — above 350KB, where most WordPress pages 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
A+
100/100
Platform & xSpeed readiness
2/4 checks passed · 8/8 pts earned
Info
Platform
WordPress detected
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
C
78/100
Lab performance (Lighthouse)
2/5 checks passed · 31.1/40 pts earned
Partial
Lighthouse performance score (mobile) 15.1/18 pts
84/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
Partial
Largest Contentful Paint ≤ 2.5s 4/8 pts
LCP 3.2s
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
Pass
Pass
Partial
First Contentful Paint ≤ 1.8s 2/4 pts
FCP 2.4s
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
D
60/100
Server response & caching
3/6 checks passed · 12/20 pts earned
Fail
Time to first byte ≤ 200ms 0/8 pts
TTFB 1.9s 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 1ms 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
N/A
Page served from cache —
Correctly per-visitor — this response is marked `no-cache, must-revalidate, max-age=0, no-store, private`, so it must not be held in a shared cache.
Nothing to fix. If parts of this page are the same for everyone, they can still be cached separately — but the page as a whole is right to opt out.
Guidelines: MDN — HTTP caching
Pass
HTML compression (bytes on the wire) 5/5 pts
Content-Encoding: gzip — 2.2KB on the wire (Brotli would be 2.0KB)
Guidelines: MDN — Content-Encoding · RFC 7932 — Brotli
Pass
Efficient cache policy on static assets 5/5 pts
Passes the Lighthouse cache-policy 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
10/100
Asset optimization
0/5 checks passed · 2/20 pts earned
Fail
No render-blocking resources 0/5 pts
Fails the Lighthouse audit — 5 files: dashicons.min.css, style.css, jquery.js… · ~2.1s of first paint
Inline the critical CSS and defer the rest. Note that one of these comes from another host, so deferring it is the only lever you have.
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 — 1 file: jquery.js
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
Fail
Modern, optimized image formats 0/4 pts
Fails the Lighthouse audit — 1 file: NEW-LOGO-26-300x300-1.png · ~600ms 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
Partial
Total page weight (≤ 350KB for full marks) 2/3 pts
533KB transferred — above 350KB, where most WordPress pages 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
A+
100/100
Platform & xSpeed readiness
2/4 checks passed · 8/8 pts earned
Info
Platform
WordPress detected
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]()