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).
3.2sTTFB
73Lighthouse desktop
brCompression
MISSCache
Lighthouse was unavailable for the mobile run · Desktop: 59 (D) —
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 25 of ~100 rubric points and is NOT comparable with a full scan. The desktop run did complete — .
This site runs xSpeed v1.4.2. 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. spinpointgolf.1wp.site'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/spinpointgolf-1wp-site-27c6c04be5.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 — and 3.2s 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 3.2s 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 829ms 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.
Cloudflare forwarded this request upstream (`cf-cache-status: DYNAMIC`).
Let Cloudflare cache HTML for visitors who are not logged in: a Cache Rule set to "Eligible for cache" that bypasses the logged-in, cart and comment cookies. The edge then answers pages near the visitor instead of sending each one to your server.
xSpeed FreeCloudflare integrationAI promptUsing my site's xSpeed MCP connection: check whether Cloudflare is caching HTML for this site, and if it is not, tell me the Cache Rule to add and purge Cloudflare once it is in place.
Fails the Lighthouse audit — 8 files: jquery-migrate.min.js, jquery.min.js, woocommerce-blocktheme.css… · ~200ms 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.
Total page weight (≤ 350KB for full marks) 0/3 pts
12.5MB transferred — over 1,500KB
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.
The public xSpeed MCP route returned its expected unauthenticated challenge. This confirms route responsiveness only; client authentication and control were not tested.
TTFB 3.2s 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.
Cloudflare forwarded this request upstream (`cf-cache-status: DYNAMIC`).
Let Cloudflare cache HTML for visitors who are not logged in: a Cache Rule set to "Eligible for cache" that bypasses the logged-in, cart and comment cookies. The edge then answers pages near the visitor instead of sending each one to your server.
xSpeed FreeCloudflare integrationAI promptUsing my site's xSpeed MCP connection: check whether Cloudflare is caching HTML for this site, and if it is not, tell me the Cache Rule to add and purge Cloudflare once it is in place.
The public xSpeed MCP route returned its expected unauthenticated challenge. This confirms route responsiveness only; client authentication and control were not tested.
Scan spinpointgolf-1wp-site-27c6c04be5 · rubric v2026.10.1 · 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 spinpointgolf.1wp.site and would rather this report were not public? Email
support@wpdeveloper.com and we will remove it.