Real visitors · Chrome UX Report · mobile · this page or its site ·
fails Core Web Vitals
5.9sLCP (p75)
0.02CLS (p75)
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).
408msTTFB
51Lighthouse mobile
brCompression
HITCache
Lighthouse was unavailable for the desktop run · Mobile: 51 (F) —
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 33 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 LiteSpeed Cache. 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
✓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.
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 www.rtdiamonds.jp scored 51/100 on xSpeed Scan (https://xspeedcache.com/scan/r/rtdiamonds-jp-e6b64df790). 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/rtdiamonds-jp-e6b64df790.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.xSpeed makes any host faster, but a cache is only as fast as the server behind a MISS.
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 408ms 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 621ms 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.
Fails the Lighthouse audit — 8 files: styles.css, poppins.css, frontend.min.css… · ~3.0s 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 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 408ms 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 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 rtdiamonds-jp-e6b64df790 · rubric v2026.09.5 · 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 www.rtdiamonds.jp and would rather this report were not public? Email
support@wpdeveloper.com and we will remove it.