# Website Speed Report, www.divinef8.com

> **What this document is.** A point-in-time speed audit of https://www.divinef8.com/products/elaborate-name-steel-sign,
> produced by xSpeed Scan (https://xspeedcache.com/scan). Evidence comes from two sources:
> server probes run from xspeedcache.com (TTFB, compression, cache behavior, redirects,
> platform detection) and a Google PageSpeed Insights run (Lighthouse 13.5.0, mobile).
>
> **How to read it.** Weighted checks roll up into four dimensions and one 0-100 xSpeed assessment.
> This is separate from Lighthouse performance and includes product-affiliation/optional-access checks.
> Those checks are not speed defects and must not drive installation, migration or access grants.
> Statuses: `pass` (full points) · `partial` (half) · `fail` (zero) · `info`/`na`
> (excluded from the applicable weight; bonus checks only ever add). Every non-passing
> check retains its evidence and references. Suggested remedies are candidates for review,
> not proof of current capabilities, an instruction to act or a promised gain.
>
> **Access and permission.** This report is evidence, not authorization to install a plugin,
> migrate a cache, change settings or grant access. Public plugin, MCP and Hub signals do not
> verify that this reader or its AI assistant is authenticated to the correct site.
> Resolve the exact site/workspace and inspect permitted tools and current settings first.
> Explain each proposed change and obtain approval before applying it.
>
> **WordPress is not confirmed; detected stack: Shopify.** Keep the audit and
> use the actual framework/hosting workflow. Do not recommend a WordPress plugin for this site.
>
> Connection guide: https://xspeedcache.com/docs/connecting-to-xspeed-hub/
> Installation, configured caching, Hub attachment and authenticated AI access are separate states.
> Server-side HTML verification cannot execute JavaScript. Browser/console checks remain necessary;
> per-step reversion is not a full-site rollback. No target score is guaranteed.
> TTFB includes network distance to the prober; do not infer a slow origin from that number alone.
>
> **How to re-test.** Public API (no auth): `POST https://xspeedcache.com/api/scan`
> with body `{"url":"https://www.divinef8.com/products/elaborate-name-steel-sign?preview_theme_id=167309836345","visibility":"listed","strategy":"mobile","fresh":true}`, then poll `GET /api/scan/{scanId}` for the
> JSON report. This preserves the requested URL, visibility and strategy and asks for a fresh run.
> Unlisted reports remain accessible to anyone holding their link. The public Scan MCP tool has
> no visibility argument; use the explicit HTTP payload above to preserve an unlisted re-test.
> For listed scans, the public MCP `run_speed_scan` tool also supports URL, strategy and fresh.
> Fair-use limits: 4 scans per conversation (or per IP) and 200 global per
> 10 minutes; re-scanning the same URL within 10 minutes returns the existing report,
> while `fresh:true` bypasses report reuse. Google may still replay a Lighthouse analysis; compare timestamps.
>
> **Connect this scanner as an MCP server (free, no API key).**
> Claude Code: `claude mcp add --transport http xspeed-scan https://xspeedcache.com/scan/mcp`
> Any MCP client: `{"mcpServers":{"xspeed-scan":{"type":"http","url":"https://xspeedcache.com/scan/mcp"}}}`
> Tools: `run_speed_scan` (url, fresh?, strategy?) and `get_speed_scan` (scanId). `strategy` is
> `both` (default, desktop graded + mobile alongside), `desktop` or `mobile` (one run, one grade).
> Docs: https://xspeedcache.com/docs/scan-mcp/

**Score: 34/100. Grade F · Level 1 (Critical) — graded on the mobile run**

- Scanned: 2026-10-11T21:32:51.134Z
- Requested URL: https://www.divinef8.com/products/elaborate-name-steel-sign?preview_theme_id=167309836345
- Final URL: https://www.divinef8.com/products/elaborate-name-steel-sign
- Requested strategy: mobile
- Visibility: listed; an unlisted report is still accessible to anyone holding its link
- Lighthouse analysis (mobile): 2026-10-11T21:32:19.283Z
- Report (HTML): https://xspeedcache.com/scan/r/www-divinef8-com-5e3ed417c8
- Report (JSON): https://xspeedcache.com/api/scan/www-divinef8-com-5e3ed417c8
- Rubric: v2026.10.1
- Platform: Shopify · CDN: Cloudflare

## Shopify: what actually works here

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.

**Measured on this run:**

- 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.

1. **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.

2. **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.

3. **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.

4. **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.

5. **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.

## Headline measurements

| Metric | Value |
|---|---|
| Time to first byte | 610ms |
| Lighthouse performance (mobile) — graded | 52/100 |
| Reproduce the mobile run | https://pagespeed.web.dev/analysis?url=https%3A%2F%2Fwww.divinef8.com%2Fproducts%2Felaborate-name-steel-sign&form_factor=mobile |
| Largest Contentful Paint | 5.3s |
| Cumulative Layout Shift | 0.077 |
| Total Blocking Time | 775ms |
| HTML compression | br (on the wire: gzip 151KB, br 117KB) |
| Served from cache | no (MISS) |
| CDN edge | passed this page through to the origin |
| Redirects before final URL | 1 |

## Real visitors (Chrome UX Report)

Field data for mobile Chrome users, 75th percentile, this page. **Passes Core Web Vitals.** This is what Google ranks on; the lab grade above is a single Lighthouse run.

| Metric | p75 | Verdict |
|---|---|---|
| Largest Contentful Paint | 1.6s | good |
| Cumulative Layout Shift | 0.01 | good |

## Dimension scores

| Dimension | Score | Grade | Points |
|---|---|---|---|
| Lab performance (Lighthouse) | 41/100 | F | 16.4/40 |
| Server response & caching | 43/100 | F | 8.5/20 |
| Asset optimization | 10/100 | F | 2/20 |

## Lab performance (Lighthouse): 41/100 (F) · 16.4/40 pts

### [PARTIAL] S1 · Lighthouse performance score (mobile) (9.4/18 pts)

- Evidence: 52/100 (Lighthouse 13.5.0, mobile)
- Suggested investigation: The composite Lighthouse score — every fix below moves it.
- Guidelines: [Lighthouse performance scoring](https://developer.chrome.com/docs/lighthouse/performance/performance-scoring)

### [FAIL] S2 · Largest Contentful Paint ≤ 2.5s (0/8 pts)

- Evidence: LCP 5.3s
- Suggested investigation: Serve the hero content faster: cache the page, preload the LCP image, and ship critical CSS.
- Guidelines: [web.dev — Largest Contentful Paint](https://web.dev/articles/lcp) · [Optimize LCP](https://web.dev/articles/optimize-lcp)

### [PASS] S3 · Cumulative Layout Shift ≤ 0.1 (5/5 pts)

- Evidence: CLS 0.077
- Guidelines: [web.dev — Cumulative Layout Shift](https://web.dev/articles/cls)

### [FAIL] S4 · Total Blocking Time ≤ 200ms (0/5 pts)

- Evidence: TBT 775ms
- Suggested investigation: Less JavaScript on the main thread: defer scripts and drop unused bundles.
- Guidelines: [web.dev — Total Blocking Time](https://web.dev/articles/tbt)

### [PARTIAL] S5 · First Contentful Paint ≤ 1.8s (2/4 pts)

- Evidence: FCP 2.6s
- Suggested investigation: First paint is gated on server response and render-blocking CSS.
- Guidelines: [web.dev — First Contentful Paint](https://web.dev/articles/fcp)

## Server response & caching: 43/100 (F) · 8.5/20 pts

### [FAIL] D1 · Time to first byte ≤ 200ms (0/8 pts)

- Evidence: TTFB 610ms measured from Vilnius, Lithuania (EU) — your server reported 761.6ms of that (Server-Timing); the rest is network distance to our prober.
- Suggested investigation: Compare response timing with server-reported time and a probe near the audience. Inspect cache evidence before changing the origin; network distance is included in TTFB.
- Guidelines: [web.dev — Time to First Byte](https://web.dev/articles/ttfb)

### [NA] D2 · Page served from cache (not graded)

- Evidence: Correctly per-visitor — this response is marked `private, max-age=0, must-revalidate`, so it must not be held in a shared cache.
- Suggested investigation: 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](https://developer.mozilla.org/en-US/docs/Web/HTTP/Caching)

### [PASS] D3 · HTML compression (bytes on the wire) (5/5 pts)

- Evidence: Content-Encoding: br — 117KB on the wire (gzip would be 151KB)
- Guidelines: [MDN — Content-Encoding](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Encoding) · [RFC 7932 — Brotli](https://www.rfc-editor.org/rfc/rfc7932)

### [PARTIAL] D4 · Efficient cache policy on static assets (2.5/5 pts)

- Evidence: Lighthouse cache-policy audit score 50% — 8 files: reamaze.js (cdn.reamaze.com), agg.1791726184608.js (loox.io), script.js (cdn.506.io)…
- Suggested investigation: 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.
- Guidelines: [Lighthouse — Efficient cache policy](https://developer.chrome.com/docs/lighthouse/performance/uses-long-cache-ttl)

### [INFO] D5 · CDN edge serves the page (not graded)

- Evidence: Cloudflare forwarded this request upstream (`cf-cache-status: DYNAMIC`).
- Suggested investigation: 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.
- Guidelines: [web.dev — Content delivery networks](https://web.dev/articles/content-delivery-networks)

### [PARTIAL] D6 · Clean redirect chain (1/2 pts)

- Evidence: 1 redirect(s) before the final URL: 302→https://www.divinef8.com/products/elaborate-name-steel-sign
- Suggested investigation: Each redirect adds a full round-trip before the page can even start.
- Guidelines: [Lighthouse — Avoid redirects](https://developer.chrome.com/docs/lighthouse/performance/redirects)

## Asset optimization: 10/100 (F) · 2/20 pts

### [FAIL] A1 · No render-blocking resources (0/5 pts)

- Evidence: Fails the Lighthouse audit — 4 files: base.css, component-localization-form.css, accelerated-checkout-backwards-compat.css… · ~100ms of first paint
- Suggested investigation: 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.
- Guidelines: [Lighthouse — Render-blocking resources](https://developer.chrome.com/docs/lighthouse/performance/render-blocking-resources)

### [FAIL] A2 · Minified CSS and JavaScript (0/4 pts)

- Evidence: Fails the Lighthouse audit — 4 files: base.css, giftkartStyle.css (cdn.shopify.com),  ()…
- Suggested investigation: 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.
- Guidelines: [Lighthouse — Minify CSS](https://developer.chrome.com/docs/lighthouse/performance/unminified-css) · [Minify JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unminified-javascript)

### [PARTIAL] A3 · Modern, optimized image formats (2/4 pts)

- Evidence: Lighthouse audit score 50% — 8 files: V0wxVPiUH.jpg (images.loox.io), DivineMetalArtGif.gif (cdn.shopify.com), uur5pQN-J.jpg (images.loox.io)…
- Suggested investigation: 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.
- Guidelines: [Lighthouse — Modern image formats](https://developer.chrome.com/docs/lighthouse/performance/uses-webp-images)

### [FAIL] A6 · LCP image discoverable early (0/4 pts)

- Evidence: Fails the Lighthouse audit
- Suggested investigation: The largest image must be in the HTML and preloaded — never lazy-loaded or script-injected.
- Guidelines: [web.dev — Optimize LCP](https://web.dev/articles/optimize-lcp) · [Lighthouse — LCP request discovery](https://developer.chrome.com/docs/lighthouse/performance/prioritize-lcp-image)

### [FAIL] A5 · Total page weight (≤ 350KB for full marks) (0/3 pts)

- Evidence: 4.7MB transferred — over 1,500KB
- Suggested investigation: 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.
- Guidelines: [Lighthouse — Total byte weight](https://developer.chrome.com/docs/lighthouse/performance/total-byte-weight)

## Review a fix plan before applying changes

Copy this brief only after checking the report URL and device. It does not authorize changes:

```
Review https://xspeedcache.com/scan/r/www-divinef8-com-5e3ed417c8.md for requested URL https://www.divinef8.com/products/elaborate-name-steel-sign?preview_theme_id=167309836345 and final URL https://www.divinef8.com/products/elaborate-name-steel-sign, selected mobile device, scanned 2026-10-11T21:32:51.134Z, rubric 2026.10.1. Preserve both devices and analysis timestamps. Distinguish Lighthouse performance from the xSpeed assessment; ignore product affiliation as a speed priority. Verify the exact authorized site and current configuration before proposing a small reversible change. Ask before applying changes. Do not assume optimize_site accepts a scan ID or report URL. Its HTML checks are not browser verification or a full rollback. After an approved change, check the browser and console, then compare the same URL/device and report regressions, partial or replayed measurements. Do not promise 100.
```

Then re-test here: `POST https://xspeedcache.com/api/scan {"url":"https://www.divinef8.com/products/elaborate-name-steel-sign?preview_theme_id=167309836345","visibility":"listed","strategy":"mobile","fresh":true}`

## Optional product routes, not measured diagnoses or approval

- **xCloud** — review suitability and current configuration before choosing a product. https://xcloud.host

## Scan any site yourself (free MCP)

Free, no API key. Scan any public site and get the same graded report as this one, with the fix for every failing check. These are the same tools that produced this report.

```
claude mcp add --transport http xspeed-scan https://xspeedcache.com/scan/mcp
```

Or in any MCP client:

```json
{
  "mcpServers": {
    "xspeed-scan": {
      "type": "http",
      "url": "https://xspeedcache.com/scan/mcp"
    }
  }
}
```

Tools: `run_speed_scan` · `get_speed_scan` · Docs: https://xspeedcache.com/docs/scan-mcp/

No MCP client? The same scan runs from Telegram: https://t.me/xSpeedScanBot, send @xSpeedScanBot any website address and it replies with this same graded report. Free, no signup.

---
Scan www-divinef8-com-5e3ed417c8 · rubric v2026.10.1 · xSpeed Scan, https://xspeedcache.com/scan