Real visitors · Chrome UX Report · desktop · this page or its site ·
passes Core Web Vitals
1.7sLCP (p75)
145msINP (p75)
0.04CLS (p75)
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).
379msTTFB
60Lighthouse desktop
brCompression
MISSCache
Lighthouse was unavailable for the mobile run · Desktop: 67 (D) —
Partial scan — Lighthouse data unavailable for the mobile run
(PSI timed out, 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 18 of ~100 rubric points and is NOT comparable with a full scan. The desktop run did complete — .
This is a GravCMS site — act on the report with your AI assistant
✓Platform detectedGravCMS — every check below links the official guideline for the fix in this stack.
→Act on it with your AIThe machine-readable twin of this report gives an agent every failing check with its evidence, remediation and guideline link.
→Check the originHosting sets the floor on TTFB. xCloud hosts any stack — agent/MCP access built in, bring-your-own-server pricing.
xSpeed is a WordPress plugin, so it can't automate GravCMS fixes — and that's fine. Every check below links its official guideline, and the machine-readable twin of this report gives an AI everything it needs to plan the work (7 checks name a concrete remediation):
Read the speed report at https://xspeedcache.com/scan/r/getgrav-org-774dc55f14.md — it lists every failing check with evidence and the official guideline for the fix. Produce a prioritized fix plan for my GravCMS site, apply what you can, then re-test by POSTing {"url":"https://getgrav.org/"} to https://xspeedcache.com/api/scan and compare the scores.
Hosting is half of every score.Whatever the stack — GravCMS included, the server behind it sets the floor on TTFB. xCloud — from the team behind xSpeed — hosts any platform (this site's own scanner runs on 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 379ms 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 4ms 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 — 2 files: a60f7a4f94fd4d912a0e0def94d38fb7.css, colors_and_type.css · ~300ms 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.
TTFB 379ms 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.
Scan getgrav-org-774dc55f14 · rubric v2026.09.5 · 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 getgrav.org and would rather this report were not public? Email
support@wpdeveloper.com and we will remove it.