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. 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).
633msTTFB
92Lighthouse mobile
brCompression
MISSCache
Lighthouse was unavailable for the desktop run · Mobile: 68 (D) —
Partial scan — Lighthouse data unavailable for the desktop 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 mobile run did complete — .
Graded on the mobile run this time. The desktop run lost
Lighthouse (PSI answered 400), so the
headline is the mobile grade. Re-scan for the desktop-graded report.
Running Cache Enabler. xSpeed replaces it plus five other plugins — and imports its settings in one click. See the comparison →
This is WordPress — the fixes below are one plugin away
✓WordPressDetected
→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.
12 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 justice-denied.org scored 68/100 on xSpeed Scan (https://xspeedcache.com/scan/r/justice-denied-org-adbc4e5feb). 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/justice-denied-org-adbc4e5feb.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 633ms 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.
Serve the hero content faster: cache the page, preload the LCP image, and ship critical CSS.
xSpeed FreePage Cache + Preloader (Critical CSS in Pro)AI promptUsing 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.
TTFB 633ms 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 113ms 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.
Every asset with a short cache lifetime here is served by another host (statcounter.com). Their Cache-Control is not yours to set — this check will not clear while you load them.
xSpeed FreeBrowser CacheAI promptUsing my site's xSpeed MCP connection: enable browser-cache headers for static assets, then re-run the audit.
Everything blocking first paint here is loaded from another host (eadn-wc02-18301506.nxedge.io). You cannot inline or minify those — the fix is to defer them, or load fewer of them.
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.
Total page weight (≤ 350KB for full marks) 2/3 pts
645KB 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 FreeMinify + Lazy Load + Image Converter (Pro)AI promptUsing my site's xSpeed MCP connection: enable minification and lazy loading (and image conversion on Pro), then re-check page weight.
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 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 633ms 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.
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 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.
Reports graded on different runs are not a trend: mobile-graded rows are the older rubric's headline, desktop-graded rows the current one. Compare like with like.
Share your score a card for X, LinkedIn, Slack — anywhere
Every check here has a one-click fix in xSpeed Cache
Page caching, compression, image optimization and a built-in MCP server,
so your AI assistant can run this playbook for you.
Scan justice-denied-org-adbc4e5feb · rubric v2026.10.1 · Lab data: Google PageSpeed Insights (Lighthouse 13.5.0), graded on the mobile run; the desktop 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 justice-denied.org and would rather this report were not public? Email
support@wpdeveloper.com and we will remove it.