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.
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).
2.0sTTFB
81Lighthouse desktop
gzipCompression
MISSCache
Lighthouse was unavailable for the mobile run · Desktop: 48 (F) —
Partial scan — Lighthouse data unavailable for the mobile run
(PSI answered 400, usually a transient Google API error). This score reflects
server probes only; Core Web Vitals and asset audits are excluded from the grading, so it was graded on 30 of ~100 rubric points and is NOT comparable with a full scan. The desktop run did complete — .
No caching plugin detected. Most of the failing checks below are what xSpeed fixes automatically. See how →
This is WordPress — the fixes below are one plugin away
✓WordPressWordPress 7.1.2
→xSpeed Cache installedFree on wordpress.org — the setup wizard turns most of this report green.
–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.
14 of these checks map to an xSpeed feature. Install the free xSpeed Cache plugin, connect its built-in MCP server, and your AI assistant can apply every fix and re-verify. If your AI already has access to the site (WP-CLI, SSH or hosting MCP), paste this:
My WordPress site tribalcstores.org scored 48/100 on xSpeed Scan (https://xspeedcache.com/scan/r/tribalcstores-org-4bb15566a1). Install and activate the free xSpeed Cache plugin from wordpress.org/plugins/xspeed, run "wp xspeed mcp connect" and give me the MCP URL to paste into my AI client. Then read the failing checks from https://xspeedcache.com/scan/r/tribalcstores-org-4bb15566a1.md and apply the fixes: enable page caching, compression, minification and lazy loading, warm the cache, and re-scan at https://xspeedcache.com/scan to confirm the score improved.
Hosting is the other half — and 2.0s 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.
TTFB 2.0s 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 296ms 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 FreePage CacheAI promptUsing my site's xSpeed MCP connection: enable page caching and warm this page with the preloader, then re-check TTFB.
Compress text responses — Brotli typically saves ~15–20% over GZIP.
xSpeed FreeGZIP (Brotli in Pro)AI promptUsing my site's xSpeed MCP connection: enable GZIP compression (and Brotli if Pro), then confirm the HTML response is compressed.
Fails the Lighthouse audit — 8 files: header-footer-elementor.css, local-34311-frontend-desktop.css, cf7.css… · ~3.1s of first paint
CSS/JS in <head> blocks first paint. Inline the critical CSS and defer the rest.
xSpeed ProCritical CSS + Unused CSS removalAI promptUsing my site's xSpeed MCP connection: generate critical CSS for the top pages and enable unused-CSS removal, then re-test.
xSpeed FreeResource Hints (preload) + Lazy Load exclusionsAI promptUsing my site's xSpeed MCP connection: preload the LCP image for this page and exclude it from lazy loading, then re-test LCP.
WordPress rebuilds every page in PHP unless a caching plugin serves it statically.
xSpeed FreexSpeed Cache (free on wordpress.org)AI promptInstall and activate the xSpeed plugin from wordpress.org, run its setup wizard, and enable page caching.
xSpeed bundles caching, minification, lazy-load, image optimization and an AI-controllable MCP server in one plugin — and imports settings from other caching plugins in one click.
xSpeed FreexSpeed Migration (one-click import)AI promptInstall xSpeed and use its Migration tool to import your current caching settings, then deactivate the old plugin.
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 FreeMCP Server (built into xSpeed Free)AI promptIn xSpeed → MCP Server, click Connect and paste the config into your AI client — then ask it to fix this report.
TTFB 2.0s measured from Vilnius, Lithuania (EU) (best of 2 requests). This includes the network round trips between us and your origin, not just server time.
The server rebuilds the page on every request. A page cache answers in 5–15ms.
xSpeed FreePage CacheAI promptUsing my site's xSpeed MCP connection: enable page caching and warm this page with the preloader, then re-check TTFB.
Compress text responses — Brotli typically saves ~15–20% over GZIP.
xSpeed FreeGZIP (Brotli in Pro)AI promptUsing my site's xSpeed MCP connection: enable GZIP compression (and Brotli if Pro), then confirm the HTML response is compressed.
WordPress rebuilds every page in PHP unless a caching plugin serves it statically.
xSpeed FreexSpeed Cache (free on wordpress.org)AI promptInstall and activate the xSpeed plugin from wordpress.org, run its setup wizard, and enable page caching.
xSpeed bundles caching, minification, lazy-load, image optimization and an AI-controllable MCP server in one plugin — and imports settings from other caching plugins in one click.
xSpeed FreexSpeed Migration (one-click import)AI promptInstall xSpeed and use its Migration tool to import your current caching settings, then deactivate the old plugin.
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 FreeMCP Server (built into xSpeed Free)AI promptIn xSpeed → MCP Server, click Connect and paste the config into your AI client — then ask it to fix this report.
Scan tribalcstores-org-4bb15566a1 · rubric v2026.09.5 · Lab data: Google PageSpeed Insights (Lighthouse 13.5.0), graded on the desktop run; the mobile run is graded on its tab · Server probes from xspeedcache.com.
Scores vary run to run; treat trends, not single digits, as the signal.
Markdown for AI agents · JSON Own tribalcstores.org and would rather this report were not public? Email
support@wpdeveloper.com and we will remove it.