52of 100
xcloud.host
526msTTFB
63Lighthouse
70LH desktop
10.9sLCP
0.00CLS
brCompression
MISSCache
Core Web Vitals & lab metricsF53
2/5 checks passed · 21.3/40 pts Jump to section ↓
Server response & cachingF50
2/4 checks passed · 11/22 pts Jump to section ↓
Asset optimizationF50
0/2 checks passed · 3.5/7 pts Jump to section ↓
Astro what actually works on this platform
Astro ships no JavaScript unless you ask for it, so a slow Astro site is almost always one of two things: islands hydrating when they do not need to, or the HTML being built per request when it could have been built once.
- Nothing indicated the HTML came from a cache on this request, which is worth confirming: a static Astro build should be served straight off a CDN.
- No CDN detected in front of the site — for a static Astro build that is the cheapest win available.
- Check your client: directives before anything else. client:load hydrates an island immediately and costs the visitor JavaScript on first paint. client:visible defers it until the component scrolls into view and client:idle until the browser is free; most islands want one of those. A page full of client:load is the usual reason an Astro site feels heavy.
- Know whether each route is static or server-rendered. Astro can output a static file, render per request, or mix the two per route. A page with no per-visitor content that is rendered per request pays for it on every visit. Prerender the ones that can be, and let the CDN serve them.
- Use astro:assets for images. It emits modern formats at the sizes actually used and reserves the space so the layout does not shift. Raw <img> tags are usually the largest remaining payload on an otherwise lean Astro site.
- Watch what a shared layout pulls in. An import in a layout is charged to every page that uses it. One heavy component or icon set there outweighs anything you will save on an individual route.
The full instruction set, and a machine-readable copy of this report, live at xcloud.host.md — paste that URL into your AI builder's chat and it can work straight from these measurements.
Top fixes ranked by points recovered
This is a Astro site — act on the report with your AI assistant
- ✓Platform detectedAstro — 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 Astro 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 (11 checks name a concrete remediation):
Read the speed report at https://xspeedcache.com/scan/r/xcloud-host-b0b0327e6b.md — it lists every failing check with evidence and the official guideline for the fix. Produce a prioritized fix plan for my Astro site, apply what you can, then re-test by POSTing {"url":"https://xcloud.host/"} to https://xspeedcache.com/api/scan and compare the scores.Hosting is half of every score.
Whatever the stack — Astro 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 →
F
53/100
Core Web Vitals & lab metrics
2/5 checks passed · 21.3/40 pts earned
Partial
Lighthouse performance score (mobile) 11.3/18 pts
63/100 (Lighthouse 13.4.1, mobile)
The composite Lighthouse score — every fix below moves it.
xSpeed Free
AI Optimize
AI prompt
Using my site's xSpeed MCP connection: run optimize_site, then run_benchmark to verify the score improved.Guidelines: Lighthouse performance scoring
Fail
Largest Contentful Paint ≤ 2.5s 0/8 pts
LCP 10.9s
Serve the hero content faster: cache the page, preload the LCP image, and ship critical CSS.
xSpeed Free
Page Cache + Preloader (Critical CSS in Pro)
AI prompt
Using 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.Guidelines: web.dev — Largest Contentful Paint · Optimize LCP
Pass
Pass
Fail
First Contentful Paint ≤ 1.8s 0/4 pts
FCP 3.6s
First paint is gated on server response and render-blocking CSS.
xSpeed Free
Page Cache + CSS Minify
AI prompt
Using my site's xSpeed MCP connection: enable page caching and CSS minification, then re-test First Contentful Paint.Guidelines: web.dev — First Contentful Paint
F
50/100
Server response & caching
2/6 checks passed · 11/22 pts earned
Partial
Time to first byte ≤ 200ms 4/8 pts
TTFB 526ms (best of 2 requests from our scanner)
The server rebuilds the page on every request. A page cache answers in 5–15ms.
xSpeed Free
Page Cache
AI prompt
Using my site's xSpeed MCP connection: enable page caching and warm this page with the preloader, then re-check TTFB.Guidelines: web.dev — Time to First Byte
Fail
Page served from cache 0/7 pts
No cache evidence in headers or HTML
Serve HTML from a static cache instead of rebuilding it per visitor.
xSpeed Free
Page Cache + Preloader
AI prompt
Using my site's xSpeed MCP connection: enable page caching, start the preloader so pages are pre-warmed, and confirm get_cache_status reports hits.Guidelines: MDN — HTTP caching
Pass
HTML compression (Brotli/GZIP) 5/5 pts
Content-Encoding: br
Guidelines: MDN — Content-Encoding · RFC 7932 — Brotli
Info
Efficient cache policy on static assets 0/5 pts
Needs the Lighthouse audit
Re-run when Lighthouse is available.
Guidelines: Lighthouse — Efficient cache policy
Info
CDN / edge network 0/3 pts
No CDN signature detected
Optional: put a CDN or Cloudflare in front for global edge delivery.
xSpeed Free
Cloudflare integration / CDN rewriter
AI prompt
Using my site's xSpeed MCP connection: connect Cloudflare (or configure the CDN rewriter) and purge, then re-scan.Guidelines: web.dev — Content delivery networks
Pass
Clean redirect chain 2/2 pts
No redirects — the URL answers directly
Guidelines: Lighthouse — Avoid redirects
F
50/100
Asset optimization
0/5 checks passed · 3.5/7 pts earned
Info
No render-blocking resources 0/5 pts
Audit not reported for this page
Re-run when Lighthouse is available.
xSpeed Pro
Critical CSS + Unused CSS removal
AI prompt
Using my site's xSpeed MCP connection: generate critical CSS for the top pages and enable unused-CSS removal, then re-test.Guidelines: Lighthouse — Render-blocking resources
Partial
Minified CSS and JavaScript 2/4 pts
Lighthouse audit score 50%
Ship minified assets — whitespace and comments are pure transfer waste.
xSpeed Free
HTML/CSS/JS Minify
AI prompt
Using my site's xSpeed MCP connection: enable HTML, CSS and JS minification, purge the cache, and re-test.Guidelines: Lighthouse — Minify CSS · Minify JavaScript
Info
Modern, optimized image formats 0/4 pts
Audit not reported for this page
Re-run when Lighthouse is available.
xSpeed Pro
Image Converter (WebP/AVIF)
AI prompt
Using my site's xSpeed MCP connection: enable WebP/AVIF conversion with URL rewriting, then re-test image audits.Guidelines: Lighthouse — Modern image formats
Info
Offscreen images lazy-loaded 0/4 pts
Audit not reported for this page
Re-run when Lighthouse is available.
xSpeed Free
Lazy Load
AI prompt
Using my site's xSpeed MCP connection: enable lazy loading for images and iframes, then re-test.Guidelines: Lighthouse — Defer offscreen images
Partial
Total page weight ≤ 1.5MB 1.5/3 pts
1.8MB transferred
Heavy pages are slow on every connection — compress, lazy-load, and trim.
xSpeed Free
Minify + Lazy Load + Image Converter (Pro)
AI prompt
Using my site's xSpeed MCP connection: enable minification and lazy loading (and image conversion on Pro), then re-check page weight.Guidelines: Lighthouse — Total byte weight
Past scans of xcloud.host newest first · every report keeps its link
| Scanned | Score | Grade | TTFB | Lighthouse | |
|---|---|---|---|---|---|
| 2026-08-31 08:48 UTC this report | 52 | F | 526ms | 63 | |
| 2026-08-30 15:29 UTC | 54 | F | 191ms | 61 | View report → |
| 2026-08-30 14:17 UTC | 50 | F | 186ms | 48 | View report → |
| 2026-08-29 14:11 UTC | 57 | D | — | — | View report → |
| 2026-08-29 13:09 UTC | 68 | D | — | — | View report → |
| 2026-08-29 12:53 UTC | 68 | D | — | — | View report → |
Recently scanned public reports All public scans →
Click anywhere or press Esc to close![Full-size screenshot]()