34of 100
www.divinef8.com
610msTTFB
52Lighthouse mobile · graded
5.3sLCP
0.08CLS
brCompression
MISSCache
Lab data: Lighthouse 13.5.0 mobile run, graded above · Reproduce this run on PageSpeed Insights ↗
Real visitors · Chrome UX Report · mobile · this page ·
passes Core Web Vitals
1.6sLCP (p75)
0.01CLS (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).
Shopify what actually works on this platform
On Shopify the server is not yours to tune — Shopify runs it, and its TTFB is what it is. What you control is the theme and the apps, and on most stores the apps are the problem.
- Time to first byte measured 610ms, which is Shopify's to control rather than yours — do not spend effort there.
- A crawler reads about 15,675 characters of text from your HTML.
- Audit the apps before touching the theme. Every installed app that injects a script costs every page, including the ones it has nothing to do with. Uninstalled apps often leave their snippets behind in the theme. This is the largest and least glamorous win on most stores — count the third-party scripts on a product page and ask which are earning their place.
- Prefer theme app extensions to injected script tags. Extensions load through Shopify's own pipeline and can be removed cleanly; script tags injected into the theme cannot, and are what accumulates over years of installing and uninstalling.
- Serve images at the size they are displayed. Liquid can request an exact width from Shopify's CDN. A 2000px hero scaled down in CSS is paid for at full size by every visitor on a phone.
- Defer what does not paint the page. Reviews, chat widgets, popups and analytics rarely need to run before the product is visible. Loading them after interaction keeps the main thread free when it matters.
- Do not chase TTFB. It is Shopify's number. Measure what a visitor waits for — when the product image and price appear — and optimise that instead.
The full instruction set, and a machine-readable copy of this report, live at www.divinef8.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
This is a Shopify site — act on the report with your AI assistant
- ✓Platform detectedShopify — 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 Shopify 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 (12 checks name a concrete remediation):
Read the speed report at https://xspeedcache.com/scan/r/www-divinef8-com-5e3ed417c8.md — it lists every failing check with evidence and the official guideline for the fix. Produce a prioritized fix plan for my Shopify site, apply what you can, then re-test by POSTing {"url":"https://www.divinef8.com/products/elaborate-name-steel-sign"} to https://xspeedcache.com/api/scan and compare the scores.Hosting is half of every score.
Shopify manages the servers here, so hosting isn't yours to tune. If this site ever moves to its own stack, that choice becomes the biggest lever — xCloud (from the team behind xSpeed) hosts anything, with agent/MCP access built in and bring-your-own-server pricing.
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.
F
41/100
Lab performance (Lighthouse)
1/5 checks passed · 16.4/40 pts earned
Partial
Lighthouse performance score (mobile) 9.4/18 pts
52/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
Fail
Total Blocking Time ≤ 200ms 0/5 pts
TBT 775ms
Less JavaScript on the main thread: defer scripts and drop unused bundles.
xSpeed Free
JS Minify + Defer
AI prompt
Using my site's xSpeed MCP connection: enable JS minification and deferred loading, then re-test Total Blocking Time.Guidelines: web.dev — Total Blocking Time
Partial
First Contentful Paint ≤ 1.8s 2/4 pts
FCP 2.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
43/100
Server response & caching
1/6 checks passed · 8.5/20 pts earned
Fail
Time to first byte ≤ 200ms 0/8 pts
TTFB 610ms measured from Vilnius, Lithuania (EU) — your server reported 761.6ms of that (Server-Timing); the rest is network distance to our prober.
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
N/A
Page served from cache —
Correctly per-visitor — this response is marked `private, max-age=0, must-revalidate`, 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.
Guidelines: MDN — HTTP caching
Pass
HTML compression (bytes on the wire) 5/5 pts
Content-Encoding: br — 117KB on the wire (gzip would be 151KB)
Guidelines: MDN — Content-Encoding · RFC 7932 — Brotli
Partial
Efficient cache policy on static assets 2.5/5 pts
Lighthouse cache-policy audit score 50% — 8 files: reamaze.js (cdn.reamaze.com), agg.1791726184608.js (loox.io), script.js (cdn.506.io)…
Every asset with a short cache lifetime here is served by another host (cdn.reamaze.com, loox.io, cdn.506.io). 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
Partial
Clean redirect chain 1/2 pts
1 redirect(s) before the final URL: 302→https://www.divinef8.com/products/elaborate-name-steel-sign
Each redirect adds a full round-trip before the page can even start.
Guidelines: Lighthouse — Avoid redirects
F
10/100
Asset optimization
0/5 checks passed · 2/20 pts earned
Fail
No render-blocking resources 0/5 pts
Fails the Lighthouse audit — 4 files: base.css, component-localization-form.css, accelerated-checkout-backwards-compat.css… · ~100ms of first paint
Inline the critical CSS and defer the rest. Note that one of these comes from another host, so deferring it is the only lever you have.
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
Fail
Minified CSS and JavaScript 0/4 pts
Fails the Lighthouse audit — 4 files: base.css, giftkartStyle.css (cdn.shopify.com), ()…
Ship minified assets. Note that 3 of these come from another host and are not yours to minify — that part of the audit will not clear.
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
Partial
Modern, optimized image formats 2/4 pts
Lighthouse audit score 50% — 8 files: V0wxVPiUH.jpg (images.loox.io), DivineMetalArtGif.gif (cdn.shopify.com), uur5pQN-J.jpg (images.loox.io)…
Every image flagged here is served from another host (images.loox.io, cdn.shopify.com), so converting them is not yours to do — the fix is to host them yourself, or load fewer.
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
Fail
LCP image discoverable early 0/4 pts
Fails the Lighthouse audit
The largest image must be in the HTML and preloaded — never lazy-loaded or script-injected.
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
Fail
Total page weight (≤ 350KB for full marks) 0/3 pts
4.7MB 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 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 www.divinef8.com newest first · every report keeps its link
| Scanned | Score | Grade | Graded on | TTFB | Lighthouse | |
|---|---|---|---|---|---|---|
| 2026-10-11 22:43 UTC | 61 | D | desktop | 381ms | 67 | View report → |
| 2026-10-11 21:49 UTC | 41 | F | mobile | 185ms | 48 | View report → |
| 2026-10-11 21:35 UTC | 33 | F | mobile | 203ms | 43 | View report → |
| 2026-10-11 21:32 UTC this report | 34 | F | mobile | 610ms | 52 | |
| 2026-10-11 21:32 UTC | 40 | F | mobile | 533ms | 52 | 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.
Recently scanned public reports All public scans →
Click anywhere or press Esc to close![Full-size screenshot]()