www.shopify.com
Lab data: Lighthouse 13.4.1 mobile run, graded above · Reproduce this run on PageSpeed Insights ↗
Why is this different from the score in my browser?
This view grades the mobile run. Lighthouse 13.4.1 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. This report predates the desktop-graded headline: only the mobile run was graded. 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 our own prober.
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 50ms, which is Shopify's to control rather than yours — do not spend effort there.
- A crawler reads about 7,970 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.shopify.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 (8 checks name a concrete remediation):
Read the speed report at https://xspeedcache.com/scan/r/shopify-com-a8c7bfe5e5.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.shopify.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)
1/5 checks passed · 20.8/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 JS minification and deferred loading, then re-test Total Blocking Time.AI prompt
Using my site's xSpeed MCP connection: enable page caching and CSS minification, then re-test First Contentful Paint.Server response & caching
4/6 checks passed · 24/25 pts earnedAsset optimization
1/5 checks passed · 5.5/7 pts earnedAI prompt
Using my site's xSpeed MCP connection: generate critical CSS for the top pages and enable unused-CSS removal, then re-test.AI prompt
Using my site's xSpeed MCP connection: enable WebP/AVIF conversion with URL rewriting, then re-test image audits.AI prompt
Using my site's xSpeed MCP connection: enable lazy loading for images and iframes, then re-test.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 www.shopify.com newest first · every report keeps its link
| Scanned | Score | Grade | Graded on | TTFB | Lighthouse | |
|---|---|---|---|---|---|---|
| 2026-09-26 03:36 UTC | 84 | B | desktop | 52ms | 81 | View report → |
| 2026-09-01 02:08 UTC this report | 70 | C | mobile | 50ms | 63 |
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.