73of 100
51of 100
apps.uxatom.com
280msTTFB
99Lighthouse desktop · graded
79Lighthouse mobile
1.0sLCP
0.00CLS
brCompression
MISSCache
Lab data: Lighthouse 13.5.0 desktop run, graded above · Reproduce this run on PageSpeed Insights ↗ · Mobile: 51 (F) —
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. On this page the mobile run scored 51 (F) against 73 (C) here — to see every check graded on that run.
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).
280msTTFB
99Lighthouse desktop
79Lighthouse mobile · graded
5.3sLCP
0.00CLS
brCompression
MISSCache
Lab data: Lighthouse 13.5.0 mobile run, graded above · Reproduce this run on PageSpeed Insights ↗ · Desktop: 73 (C) —
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?
This view grades the mobile run. Lighthouse 13.5.0 runs at Google through the PageSpeed Insights API on an emulated mid-range Android with a 4× CPU slowdown and a throttled connection. Chrome DevTools on your own machine, on the Desktop preset, applies almost none of that, and the same page routinely scores 30–50 points higher there. Neither number is wrong — they are different tests.
Mobile is what Google ranks on, so this is the number that affects your
search performance. On this page the desktop run scored 73 (C) against
51 (F) here —
to see every check graded on that run. To reproduce it, open the same run on PageSpeed Insights,
or pass strategy=mobile to the PageSpeed API — it defaults to desktop.
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, mobile). Server probes (TTFB, compression, cache, headers) are measured separately from Vilnius, Lithuania (EU).
Nuxt what actually works on this platform
Nuxt decides per route whether a page is prerendered, cached for a while, or rendered fresh every time — and that decision, not server tuning, is where most of the time goes.
- Nothing indicated the HTML came from a cache on this request — every visit appears to pay for a fresh render.
- A crawler reads about 1,085 characters of text from your HTML.
- Time to first byte measured 280ms on this run — one sample; re-run it before treating it as the number.
- Set route rules for the pages that do not change per visitor. Nuxt lets you mark a route prerendered, cached with revalidation, or rendered per request, in one config block. Marketing pages, docs and posts are almost always in the first two categories and are usually left in the third by default.
- Check what the payload carries. Nuxt serialises the data a page fetched into the HTML so the client does not refetch it. A route that pulls a large collection ships all of it twice — once as markup, once as payload. Fetch only the fields the page renders.
- Prefetch links, but only what is likely. NuxtLink prefetches by default, which is right for a small nav and wasteful on a long list. Turn it off where a page links to hundreds of routes.
- Use the image component and lazy-load below the fold. Nuxt Image emits modern formats at the right size; explicit dimensions stop layout shift. On most Nuxt sites this is the largest single win after the route rules.
The full instruction set, and a machine-readable copy of this report, live at apps.uxatom.com.md — paste that URL into your AI builder's chat and it can work straight from these measurements.
Top fixes ranked by points recovered · desktop
Top fixes ranked by points recovered · mobile
This is a Nuxt site — act on the report with your AI assistant
- ✓Platform detectedNuxt — 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 Nuxt 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 (8 checks name a concrete remediation):
Read the speed report at https://xspeedcache.com/scan/r/apps-uxatom-com-59ea98d471.md — it lists every failing check with evidence and the official guideline for the fix. Produce a prioritized fix plan for my Nuxt site, apply what you can, then re-test by POSTing {"url":"https://apps.uxatom.com/"} to https://xspeedcache.com/api/scan and compare the scores.Hosting is half of every score.
Whatever the stack — Nuxt 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.
Connect this scanner to your AI assistant
Free. No API key, no sign-up. Scan any public site and get the same graded report as this one, with the fix for every failing check.
Endpoint
https://xspeedcache.com/scan/mcpClaude Code — one command
claude mcp add --transport http xspeed-scan https://xspeedcache.com/scan/mcpClaude Desktop, Cursor, or any MCP client — add to your config
{
"mcpServers": {
"xspeed-scan": {
"type": "http",
"url": "https://xspeedcache.com/scan/mcp"
}
}
}run_speed_scanScan any public URL and return this whole graded report.get_speed_scanRead a scan already run, by its id.
A+
99/100
Lab performance (Lighthouse)
5/5 checks passed · 39.8/40 pts earned
Pass
Lighthouse performance score (desktop) 17.8/18 pts
99/100 (Lighthouse 13.5.0, desktop)
Guidelines: Lighthouse performance scoring
Pass
Largest Contentful Paint ≤ 2.5s 8/8 pts
LCP 1.0s
Guidelines: web.dev — Largest Contentful Paint · Optimize LCP
Pass
Pass
Pass
F
50/100
Server response & caching
2/6 checks passed · 13.5/27 pts earned
Partial
Time to first byte ≤ 200ms 4/8 pts
TTFB 280ms 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 1ms 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 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 (bytes on the wire) 5/5 pts
Content-Encoding: br — 4.0KB on the wire (gzip would be 4.1KB)
Guidelines: MDN — Content-Encoding · RFC 7932 — Brotli
Partial
Efficient cache policy on static assets 2.5/5 pts
Lighthouse cache-policy audit score 50% — 1 file: beacon.min.js (static.cloudflareinsights.com)
Every asset with a short cache lifetime here is served by another host (static.cloudflareinsights.com). Their Cache-Control is not yours to set — this check will not clear while you load them.
xSpeed Free
Browser Cache
AI prompt
Using my site's xSpeed MCP connection: enable browser-cache headers for static assets, then re-run the audit.Guidelines: Lighthouse — Efficient cache policy
Info
CDN edge serves the page —
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 Free
Cloudflare integration
AI prompt
Using 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.Guidelines: web.dev — Content delivery networks
Pass
Clean redirect chain 2/2 pts
No redirects — the URL answers directly
Guidelines: Lighthouse — Avoid redirects
F
44/100
Asset optimization
1/5 checks passed · 7/16 pts earned
Fail
No render-blocking resources 0/5 pts
Fails the Lighthouse audit — 1 file: entry.LqdsGyOj.css · ~50ms of first paint
CSS/JS in <head> blocks first paint. Inline the critical CSS and defer the rest.
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
Pass
Minified CSS and JavaScript 4/4 pts
Passes the Lighthouse audit
Guidelines: Lighthouse — Minify CSS · Minify JavaScript
Partial
Modern, optimized image formats 2/4 pts
Lighthouse audit score 50% — 5 files: rapid-pass.png, pdflex.png, takatrack.png…
Serve WebP/AVIF at the right compression — usually the single largest byte saving.
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
LCP image discoverable early —
Audit not reported for this page
Re-run when Lighthouse is available.
xSpeed Free
Resource Hints (preload) + Lazy Load exclusions
AI prompt
Using my site's xSpeed MCP connection: preload the LCP image for this page and exclude it from lazy loading, then re-test LCP.Guidelines: web.dev — Optimize LCP · Lighthouse — LCP request discovery
Partial
Total page weight (≤ 350KB for full marks) 1/3 pts
1097KB transferred — heavy: most WordPress pages this size fail mobile LCP
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 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
D
66/100
Lab performance (Lighthouse)
2/5 checks passed · 26.2/40 pts earned
Partial
Lighthouse performance score (mobile) 14.2/18 pts
79/100 (Lighthouse 13.5.0, 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 5.3s
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
Partial
First Contentful Paint ≤ 1.8s 2/4 pts
FCP 2.0s
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
41/100
Server response & caching
2/6 checks passed · 11/27 pts earned
Partial
Time to first byte ≤ 200ms 4/8 pts
TTFB 280ms 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 2ms 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 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 (bytes on the wire) 5/5 pts
Content-Encoding: br — 4.0KB on the wire (gzip would be 4.1KB)
Guidelines: MDN — Content-Encoding · RFC 7932 — Brotli
Fail
Efficient cache policy on static assets 0/5 pts
Fails the Lighthouse cache-policy audit — 1 file: beacon.min.js (static.cloudflareinsights.com)
Every asset with a short cache lifetime here is served by another host (static.cloudflareinsights.com). Their Cache-Control is not yours to set — this check will not clear while you load them.
xSpeed Free
Browser Cache
AI prompt
Using my site's xSpeed MCP connection: enable browser-cache headers for static assets, then re-run the audit.Guidelines: Lighthouse — Efficient cache policy
Info
CDN edge serves the page —
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 Free
Cloudflare integration
AI prompt
Using 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.Guidelines: web.dev — Content delivery networks
Pass
Clean redirect chain 2/2 pts
No redirects — the URL answers directly
Guidelines: Lighthouse — Avoid redirects
F
31/100
Asset optimization
1/5 checks passed · 5/16 pts earned
Fail
No render-blocking resources 0/5 pts
Fails the Lighthouse audit — 1 file: entry.LqdsGyOj.css · ~500ms of first paint
CSS/JS in <head> blocks first paint. Inline the critical CSS and defer the rest.
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
Pass
Minified CSS and JavaScript 4/4 pts
Passes the Lighthouse audit
Guidelines: Lighthouse — Minify CSS · Minify JavaScript
Fail
Modern, optimized image formats 0/4 pts
Fails the Lighthouse audit — 5 files: rapid-pass.png, pdflex.png, takatrack.png… · ~100ms of first paint
Serve WebP/AVIF at the right compression — usually the single largest byte saving.
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
LCP image discoverable early —
Audit not reported for this page
Re-run when Lighthouse is available.
xSpeed Free
Resource Hints (preload) + Lazy Load exclusions
AI prompt
Using my site's xSpeed MCP connection: preload the LCP image for this page and exclude it from lazy loading, then re-test LCP.Guidelines: web.dev — Optimize LCP · Lighthouse — LCP request discovery
Partial
Total page weight (≤ 350KB for full marks) 1/3 pts
1095KB transferred — heavy: most WordPress pages this size fail mobile LCP
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 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 apps.uxatom.com newest first · every report keeps its link
| Scanned | Score | Grade | Graded on | TTFB | Lighthouse | |
|---|---|---|---|---|---|---|
| 2026-10-11 07:45 UTC | 77 | C | desktop | 159ms | 99 | View report → |
| 2026-10-11 07:45 UTC this report | 73 | C | desktop | 280ms | 99 |
Recently scanned public reports All public scans →
Click anywhere or press Esc to close![Full-size screenshot]()