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).
Lighthouse numbers are from an earlier run.
PageSpeed Insights served an analysis it had already done (measured 2026-09-17 09:35 UTC),
so if you changed something just now it is not reflected here yet. The server probes below
(TTFB, compression, cache, headers) DID re-run. Scan again in a few minutes for fresh
Core Web Vitals.
This site runs xSpeed v1.3.3. The checks below include xSpeed-compatible fixes; an authenticated MCP connection is required before an assistant can apply them. The report indicates MCP availability, but authentication was not tested.
✓MCP signal presentThe report indicates MCP availability. This does not verify client authentication or control.
→xSpeed Hub signalOptional: review Hub configuration and confirm authorized site membership at app.xspeedcache.com.
10 of these checks map to an xSpeed feature. ganancio.com's report indicates that xSpeed MCP is available. This scan did not verify client credentials; if your client is configured and authenticated, use this prompt:
If you are authenticated to my site's xSpeed MCP server, read the failing checks from https://xspeedcache.com/scan/r/ganancio-com-cec0a47af7.md, 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.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 205ms 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 18ms 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: fadeInUp.min.css, fadeIn.min.css, main.min.css… · ~2.3s 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.
The public xSpeed MCP route returned its expected unauthenticated challenge. This confirms route responsiveness only; client authentication and control were not tested.
Scan ganancio-com-cec0a47af7 · rubric v2026.09.2 · Lab data: Google PageSpeed Insights (Lighthouse 13.4.1), graded on the mobile run · Server probes from xspeedcache.com.
Scores vary run to run; treat trends, not single digits, as the signal.
Markdown for AI agents · JSON Own ganancio.com and would rather this report were not public? Email
support@wpdeveloper.com and we will remove it.