uxatom.com
Lab data: Lighthouse 13.5.0 desktop run, graded above · Reproduce this run on PageSpeed Insights ↗ · Mobile: 89 (B) —
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 89 (B) against 99 (A+) 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).
Lab data: Lighthouse 13.5.0 mobile run, graded above · Reproduce this run on PageSpeed Insights ↗ · Desktop: 99 (A+) —
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 99 (A+) against
89 (B) 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.
- The HTML came back from a cache on this request, so the render is already being reused.
- A crawler reads about 10,619 characters of text from your HTML.
- Time to first byte measured 155ms 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 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 (2 checks name a concrete remediation):
Read the speed report at https://xspeedcache.com/scan/r/uxatom-com-32ab6bee43.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://uxatom.com/"} to https://xspeedcache.com/api/scan and compare the scores.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.
Lab performance (Lighthouse)
5/5 checks passed · 40/40 pts earnedServer response & caching
6/6 checks passed · 30/30 pts earnedAsset optimization
3/5 checks passed · 15/16 pts earnedAI 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.AI prompt
Using my site's xSpeed MCP connection: enable minification and lazy loading (and image conversion on Pro), then re-check page weight.Lab performance (Lighthouse)
2/5 checks passed · 31.7/40 pts earnedAI prompt
Using my site's xSpeed MCP connection: run optimize_site, then run_benchmark to verify the score improved.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.AI prompt
Using my site's xSpeed MCP connection: enable page caching and CSS minification, then re-test First Contentful Paint.Server response & caching
6/6 checks passed · 30/30 pts earnedAsset optimization
3/5 checks passed · 15/16 pts earnedAI 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.AI prompt
Using my site's xSpeed MCP connection: enable minification and lazy loading (and image conversion on Pro), then re-check page weight.Past scans of uxatom.com newest first · every report keeps its link
| Scanned | Score | Grade | Graded on | TTFB | Lighthouse | |
|---|---|---|---|---|---|---|
| 2026-10-11 07:32 UTC this report | 99 | A+ | desktop | 155ms | 100 | |
| 2026-10-11 05:32 UTC | 99 | A+ | desktop | 116ms | 99 | View report → |
| 2026-10-05 13:31 UTC | 98 | A+ | desktop | 124ms | 100 | View report → |
| 2026-10-04 15:56 UTC | 91 | A | desktop | 39ms | 81 | View report → |
| 2026-08-30 18:39 UTC | 82 | B | mobile | 59ms | 82 | View report → |
| 2026-08-30 18:36 UTC | 82 | B | mobile | 63ms | 81 | View report → |
Reports graded on different runs are not a trend: mobile-graded rows are the older rubric's headline, desktop-graded rows the current one. Compare like with like.