45of 100
partnerplus.dev
FLevel 2 · Slow
Graded on mobileWordPress 7.1⚡ xSpeed v1.3.2Cloudflare
1.1sTTFB
0Lighthouse desktop
0Lighthouse mobile · graded
0.00CLS
brCompression
HITCache
Lab data: Lighthouse 13.4.1 mobile run, graded above · Reproduce this run on PageSpeed Insights ↗
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.4.1 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. This report predates the desktop-graded headline: only the mobile run was graded. 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)F23
2/5 checks passed · 9/40 pts Jump to section ↓
Server response & cachingC73
5/6 checks passed · 22/30 pts Jump to section ↓
Asset optimizationF13
0/3 checks passed · 1.5/12 pts Jump to section ↓
Platform & xSpeed readinessA+100
2/2 checks passed · 8/8 pts Jump to section ↓
Top fixes ranked by points recovered
xSpeed is installed — verify its MCP endpoint before automating
- ✓WordPressWordPress 7.1
- ✓xSpeed Cache installedv1.3.2
- →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).
partnerplus.dev already runs xSpeed Cache v1.3.2, 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 partnerplus.dev runs xSpeed Cache and scored 45/100 (https://xspeedcache.com/scan/r/partnerplus-dev-c4f0831ae1). Once I've configured and authenticated your MCP connection, read the failing checks from https://xspeedcache.com/scan/r/partnerplus-dev-c4f0831ae1.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.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
23/100
Lab performance (Lighthouse)
2/5 checks passed · 9/40 pts earned
Fail
Lighthouse performance score (mobile) 0/18 pts
0/100 (Lighthouse 13.4.1, 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 —
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
Fail
Total Blocking Time ≤ 200ms 0/5 pts
TBT —
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
C
73/100
Server response & caching
5/6 checks passed · 22/30 pts earned
Fail
Time to first byte ≤ 200ms 0/8 pts
TTFB 1.1s 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
Pass
Page served from cache 7/7 pts
Cache HIT evidence in response headers
Guidelines: MDN — HTTP caching
Pass
HTML compression (Brotli/GZIP) 5/5 pts
Content-Encoding: br
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
Pass
Pass
Clean redirect chain 2/2 pts
No redirects — the URL answers directly
Guidelines: Lighthouse — Avoid redirects
F
13/100
Asset optimization
0/5 checks passed · 1.5/12 pts earned
Fail
No render-blocking resources 0/5 pts
Fails the Lighthouse audit — 8 files: jquery.min.js, 38abd6f374fa2800b6c7095c27084da9.css, custom-frontend.min.css…
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
Info
Minified CSS and JavaScript —
Audit not reported for this page
Re-run when Lighthouse is available.
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 — 4 files: Race-04-EV02-24-MH2_9350-e1754628939202-1.jpg, Melbourne-stadium-1.jpg, MetLife-for-inner-wall-NAB-scaled-1-1.jpg…
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 ≤ 1.5MB 1.5/3 pts
1.6MB transferred
Heavy pages are slow on every connection — compress, lazy-load, and trim.
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)
Informational.
Pass
Caching plugin active 4/4 pts
xSpeed Cache (xSpeed signature: v1.3.2)
Guidelines: WordPress.org — Optimization: caching
Pass
Powered by xSpeed 4/4 pts
xSpeed signature: v1.3.2
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]()