Real visitors · Chrome UX Report · desktop · this page or its site ·
fails Core Web Vitals
4.7sLCP (p75)
0.02CLS (p75)
This Lighthouse run passes LCP, but real desktop Chrome users wait 4.7s for the largest paint. Google ranks on the real-user number.
Why is this different from the score in my browser?
The graded score is the desktop run. Lighthouse 13.4.1 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).
489msTTFB
98Lighthouse desktop
gzipCompression
MISSCache
Lighthouse was unavailable for the mobile run · Desktop: 77 (C) —
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 32 of ~100 rubric points and is NOT comparable with a full scan. The desktop run did complete — .
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.
7 of these checks map to an xSpeed feature. texasnerveandspine.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/texasnerveandspine-com-1e8c5f3d46.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.
TTFB 489ms 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 136ms 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: wpo-minify-header-font-awesome-5-all1789371322.min.css, wpo-minify-header-font-awesome-4-shim1789371322.min.css, wpo-minify-header-elementor-post-311789888721.min.css… · ~550ms 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.
The largest image must be in the HTML and preloaded — never lazy-loaded or script-injected.
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.
TTFB 489ms 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.
The public xSpeed MCP route returned its expected unauthenticated challenge. This confirms route responsiveness only; client authentication and control were not tested.
Scan texasnerveandspine-com-1e8c5f3d46 · rubric v2026.09.4 · Lab data: Google PageSpeed Insights (Lighthouse 13.4.1), 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 texasnerveandspine.com and would rather this report were not public? Email
support@wpdeveloper.com and we will remove it.