# Website Speed Report, www.themystical-you.com

> **What this document is.** A point-in-time speed audit of https://www.themystical-you.com/,
> 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, desktop).
> **Two graded runs.** The score below is graded on the **desktop** run — the one a reader can reproduce
> in their own browser. The mobile run is graded on the same rubric further down (64/100,
> grade D). Google ranks on mobile, so when the two differ, report both and act on the mobile failures too.
>
> **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://themystical-you.com/","visibility":"listed","strategy":"both","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: 73/100. Grade C · Level 3 (Average) — graded on the desktop run**

- Scanned: 2026-10-06T13:26:01.298Z
- Requested URL: https://themystical-you.com/
- Final URL: https://www.themystical-you.com/
- Requested strategy: both
- Visibility: listed; an unlisted report is still accessible to anyone holding its link
- Lighthouse analysis (desktop): 2026-10-06T13:24:03.782Z
- Report (HTML): https://xspeedcache.com/scan/r/themystical-you-com-9820df0e89
- Report (JSON): https://xspeedcache.com/api/scan/themystical-you-com-9820df0e89
- 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 189ms, which is Shopify's to control rather than yours — do not spend effort there.
- A crawler reads about 28,627 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 | 189ms |
| Lighthouse performance (desktop) — graded | 93/100 |
| Reproduce the desktop run | https://pagespeed.web.dev/analysis?url=https%3A%2F%2Fwww.themystical-you.com%2F&form_factor=desktop |
| Largest Contentful Paint | 911ms |
| Cumulative Layout Shift | 0.040 |
| Total Blocking Time | 112ms |
| HTML compression | br (on the wire: gzip 148KB, br 113KB) |
| Served from cache | no (MISS) |
| CDN edge | passed this page through to the origin |
| Redirects before final URL | 1 |

## Real visitors (Chrome UX Report)

Not enough Chrome traffic for field data on this page or its site. The grade above is lab data only.

## Dimension scores

| Dimension | Score | Grade | Points |
|---|---|---|---|
| Lab performance (Lighthouse) | 97/100 | A+ | 38.7/40 |
| Server response & caching | 61/100 | D | 16.5/27 |
| Asset optimization | 40/100 | F | 8/20 |

## Lab performance (Lighthouse): 97/100 (A+) · 38.7/40 pts

### [PASS] S1 · Lighthouse performance score (desktop) (16.7/18 pts)

- Evidence: 93/100 (Lighthouse 13.5.0, desktop)
- Guidelines: [Lighthouse performance scoring](https://developer.chrome.com/docs/lighthouse/performance/performance-scoring)

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

- Evidence: LCP 911ms
- 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.040
- Guidelines: [web.dev — Cumulative Layout Shift](https://web.dev/articles/cls)

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

- Evidence: TBT 112ms
- Guidelines: [web.dev — Total Blocking Time](https://web.dev/articles/tbt)

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

- Evidence: FCP 627ms
- Guidelines: [web.dev — First Contentful Paint](https://web.dev/articles/fcp)

## Server response & caching: 61/100 (D) · 16.5/27 pts

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

- Evidence: TTFB 189ms measured from Vilnius, Lithuania (EU) — your server reported 65.2ms of that (Server-Timing); the rest is network distance to our prober.
- Guidelines: [web.dev — Time to First Byte](https://web.dev/articles/ttfb)

### [FAIL] D2 · Page served from cache (0/7 pts)

- Evidence: No cache evidence in headers or HTML
- Suggested investigation: Serve HTML from a static cache instead of rebuilding it per visitor.
- 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 — 113KB on the wire (gzip would be 148KB)
- 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% — 7 files: accelerated-checkout-backwards-compat.css, loox.1696263328910.js (loox.io), klaviyo.js (static.klaviyo.com)…
- Suggested investigation: Give your CSS/JS/images long Cache-Control lifetimes. 6 of these are served by another host, so that part will not clear.
- 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: 301→https://www.themystical-you.com/
- 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: 40/100 (F) · 8/20 pts

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

- Evidence: Fails the Lighthouse audit — 5 files: main.css, vendor.css, header.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)

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

- Evidence: Passes the Lighthouse audit
- Guidelines: [Lighthouse — Minify CSS](https://developer.chrome.com/docs/lighthouse/performance/unminified-css) · [Minify JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unminified-javascript)

### [FAIL] A3 · Modern, optimized image formats (0/4 pts)

- Evidence: Fails the Lighthouse audit — 8 files: pexels-alina-vilchenko-7024685_Custom.jpg, pexels-nataliya-vaitkevich-7078083_Custom.jpg, brace.jpg… · ~50ms of first paint
- Suggested investigation: Serve WebP/AVIF at the right compression — usually the single largest byte saving.
- Guidelines: [Lighthouse — Modern image formats](https://developer.chrome.com/docs/lighthouse/performance/uses-webp-images)

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

- Evidence: Passes the Lighthouse audit
- 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.4MB 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)

## The mobile run: 64/100 (D) · Level 3 (Average)

Lighthouse was unavailable for this run (PSI answered 500); it graded 22 of ~100 rubric points.

Lighthouse analysis: not provided; replayed: unknown.

| Dimension | Score | Grade | Points |
|---|---|---|---|
| Server response & caching | 64/100 | D | 14/22 |

### Checks that differ from the desktop run

- [INFO] S1 · Lighthouse performance score (mobile) (not graded) — Lighthouse unavailable — PSI answered 500 (desktop: PASS)
- [INFO] S2 · Largest Contentful Paint ≤ 2.5s (not graded) — Lighthouse unavailable — PSI answered 500 (desktop: PASS)
- [INFO] S3 · Cumulative Layout Shift ≤ 0.1 (not graded) — Lighthouse unavailable — PSI answered 500 (desktop: PASS)
- [INFO] S4 · Total Blocking Time ≤ 200ms (not graded) — Lighthouse unavailable — PSI answered 500 (desktop: PASS)
- [INFO] S5 · First Contentful Paint ≤ 1.8s (not graded) — Lighthouse unavailable — PSI answered 500 (desktop: PASS)
- [INFO] D4 · Efficient cache policy on static assets (not graded) — Needs the Lighthouse audit (desktop: PARTIAL)
- [INFO] A1 · No render-blocking resources (not graded) — Needs Lighthouse (desktop: FAIL)
- [INFO] A2 · Minified CSS and JavaScript (not graded) — Needs Lighthouse (desktop: PASS)
- [INFO] A3 · Modern, optimized image formats (not graded) — Needs Lighthouse (desktop: FAIL)
- [INFO] A6 · LCP image discoverable early (not graded) — Needs Lighthouse (desktop: PASS)
- [INFO] A5 · Total page weight (≤ 350KB for full marks) (not graded) — Needs Lighthouse (desktop: FAIL)

## 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/themystical-you-com-9820df0e89.md for requested URL https://themystical-you.com/ and final URL https://www.themystical-you.com/, selected desktop device, scanned 2026-10-06T13:26:01.298Z, 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://themystical-you.com/","visibility":"listed","strategy":"both","fresh":true}`

## 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 themystical-you-com-9820df0e89 · rubric v2026.10.1 · xSpeed Scan, https://xspeedcache.com/scan