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).
19.7sTTFB
85Lighthouse desktop
noneCompression
MISSCache
Lighthouse was unavailable for the mobile run · Desktop: 68 (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 18 of ~100 rubric points and is NOT comparable with a full scan. The desktop run did complete — .
✓Platform detectedNot conclusively identified — every check below links the official guideline for its fix, valid on any 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.
This does not look like a WordPress site, so xSpeed cannot automate the fixes directly — but 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/cornerstoneboulderwalls-com-au-74e78d2250.md — it lists every failing check with evidence and the official guideline for the fix. Produce a prioritized fix plan for my stack, apply what you can, then re-test by POSTing {"url":"https://cornerstoneboulderwalls.com.au/"} to https://xspeedcache.com/api/scan and compare the scores.
Hosting is half of every score — and 19.7s to first byte says the origin is struggling.Whatever the stack, 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 19.7s 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 355ms 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.
Correctly per-visitor — this response is marked `private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0`, so it must not be held in a shared cache.
Nothing to fix. If parts of this page are the same for everyone, they can still be cached separately — but the page as a whole is right to opt out.
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.
Every asset with a short cache lifetime here is served by another host (lh3.googleusercontent.com, s.pinimg.com). Their Cache-Control is not yours to set — this check will not clear while you load them.
xSpeed FreeBrowser CacheAI promptUsing my site's xSpeed MCP connection: enable browser-cache headers for static assets, then re-run the audit.
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.
Fails the Lighthouse audit — 6 files: sandstone-boulder-walls-7-edited-800.avif, random-sandstone-wall-home-page-hero-image-desktop.avif, ogimage-pinjarra-hills-project-768x401.jpg… · ~400ms of first paint
Serve WebP/AVIF at the right compression — usually the single largest byte saving.
xSpeed ProImage Converter (WebP/AVIF)AI promptUsing my site's xSpeed MCP connection: enable WebP/AVIF conversion with URL rewriting, then re-test image audits.
TTFB 19.7s 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.
Correctly per-visitor — this response is marked `private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0`, so it must not be held in a shared cache.
Nothing to fix. If parts of this page are the same for everyone, they can still be cached separately — but the page as a whole is right to opt out.
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.
Scan cornerstoneboulderwalls-com-au-74e78d2250 · 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 cornerstoneboulderwalls.com.au and would rather this report were not public? Email
support@wpdeveloper.com and we will remove it.