Real visitors · Chrome UX Report · mobile · this page ·
fails Core Web Vitals
1.1sLCP (p75)
362msINP (p75)
0.03CLS (p75)
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. 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).
333msTTFB
32Lighthouse mobile
noneCompression
MISSCache
Lighthouse was unavailable for the desktop run · Mobile: 37 (F) —
Partial scan — Lighthouse data unavailable for the desktop 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 15 of ~100 rubric points and is NOT comparable with a full scan. The mobile run did complete — .
Graded on the mobile run this time. The desktop run lost
Lighthouse (PSI timed out), so the
headline is the mobile grade. Re-scan for the desktop-graded report.
✓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 (11 checks name a concrete remediation):
Read the speed report at https://xspeedcache.com/scan/r/www-gabrielny-com-cfa5dd31a5.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://www.gabrielny.com/wedding-rings"} to https://xspeedcache.com/api/scan and compare the scores.
Hosting is half of every score.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.
Serve the hero content faster: cache the page, preload the LCP image, and ship critical CSS.
xSpeed FreePage Cache + Preloader (Critical CSS in Pro)AI promptUsing 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.
TTFB 333ms 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 189ms 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.
Compress HTML responses. gzip and Brotli both pass; what matters is the bytes on the wire.
xSpeed FreeGZIP (Brotli in Pro)AI promptUsing my site's xSpeed MCP connection: check how the HTML is compressed, make sure the served encoding is the smaller of gzip and Brotli, then confirm the response size.
Fails the Lighthouse audit — 1 file: styles.min.css · ~450ms 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.
Fails the Lighthouse audit — 8 files: Stackables-Desktop-Laptop-Tablet-v2.jpg, Wedding-Bands-Desktop-Laptop-Tablet-v2.jpg, Vionne---14K-Yellow-Gold-Flush-Set-Cluster-Diamond-Cigar-Band~AN16876Y44JJ-5.jpg… · ~2.3s 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.
Total page weight (≤ 350KB for full marks) 0/3 pts
5.9MB transferred — over 1,500KB
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 FreeMinify + Lazy Load + Image Converter (Pro)AI promptUsing my site's xSpeed MCP connection: enable minification and lazy loading (and image conversion on Pro), then re-check page weight.
TTFB 333ms 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.
Compress HTML responses. gzip and Brotli both pass; what matters is the bytes on the wire.
xSpeed FreeGZIP (Brotli in Pro)AI promptUsing my site's xSpeed MCP connection: check how the HTML is compressed, make sure the served encoding is the smaller of gzip and Brotli, then confirm the response size.
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.
Share your score a card for X, LinkedIn, Slack — anywhere
Every check here has a one-click fix in xSpeed Cache
Page caching, compression, image optimization and a built-in MCP server,
so your AI assistant can run this playbook for you.
Scan www-gabrielny-com-cfa5dd31a5 · rubric v2026.10.1 · Lab data: Google PageSpeed Insights (Lighthouse 13.5.0), graded on the mobile run; the desktop 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 www.gabrielny.com and would rather this report were not public? Email
support@wpdeveloper.com and we will remove it.