speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time — measured continuously.

Measurement runs · Embed a score ·

shopify.com

https://www.shopify.com/

44 100 58 100 !AXE ✗CWV

Data from Aug 25, 2026, 1:50 PM UTC 6h old

Overall #1,457 Website Builders #6 · 1 measurement · since Aug 25, 2026

Stack

Detected on the same page load as the accessibility pass — the generator from <meta name="generator"> or the shape of the page, the host from response headers.

Cloudflare Hosted by Cloudflare

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-07-27 → 2026-08-23). This is what Google measures you on.

LCP 2.07 s good
INP 405 ms needs-improvement
CLS 0.020 good

Scores

44
Performance
no change
100
Accessibility
no change
58
Best Practices
no change
100
SEO
no change

Filmstrip Lighthouse, mobile

How the page drew during the measured load, at 8 points across 5.01 s.

  1. 626 ms
  2. 1.25 s
  3. 1.88 s
  4. 2.50 s
  5. 3.13 s
  6. 3.75 s
  7. 4.38 s
  8. 5.01 s

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 6.00 s — — 6.00 s 6.00 s
CLS Cumulative Layout Shift 0.024 — — 0.024 0.024
TBT Total Blocking Time 1.73 s — — 1.73 s 1.73 s
FCP First Contentful Paint 3.19 s — — 3.19 s 3.19 s
Speed Index 3.94 s — — 3.94 s 3.94 s
TTFB Time to First Byte 614 ms — — 614 ms 614 ms

What LCP is made of observed, unthrottled

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 6.00 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

element render delay 163 ms
time to first byte 46 ms
resource load duration 28 ms
resource load delay 17 ms

Field data Chrome UX Report, url-level

Real Chrome users, 28-day trailing window (2026-07-27 → 2026-08-23). This is what Google measures you on.

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 2.07 s good 82% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 405 ms needs-improvement 48.4% good
CLS CWV 0.020 good 93.4% good
FCP 1.79 s good 75.3% good
TTFB 906 ms needs-improvement 70.8% good

Lab vs field

Lab LCP 6.00 s · field p75 2.07 s · real users are 0.35× faster than the lab.

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-22 2.08 s 405 ms 0.020 1.80 s 906 ms
2026-08-15 2.05 s 403 ms 0.020 1.81 s 868 ms
2026-08-08 1.92 s 400 ms 0.020 1.75 s 721 ms
2026-08-01 1.82 s 393 ms 0.020 1.71 s 607 ms
2026-07-25 1.79 s 395 ms 0.020 1.70 s 563 ms
2026-07-18 1.83 s 391 ms 0.020 1.72 s 576 ms
2026-07-11 1.86 s 383 ms 0.020 1.75 s 584 ms
2026-07-04 1.89 s 373 ms 0.020 1.77 s 587 ms
2026-06-27 1.87 s 363 ms 0.020 1.76 s 561 ms
2026-06-20 1.88 s 360 ms 0.020 1.78 s 553 ms
2026-06-13 1.86 s 345 ms 0.020 1.77 s 543 ms
2026-06-06 1.85 s 328 ms 0.020 1.77 s 546 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 2.16 MB — — 2.16 MB 2.16 MB
Requests 132 — — 132 132
Third-party Weight 245 kB — — 245 kB 245 kB
Third-party CPU 166 ms — — 166 ms 166 ms
Unused JS 223 kB — — 223 kB 223 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

script 974 kB · 46 req
image 591 kB · 46 req
other 320 kB · 32 req
font 170 kB · 4 req
document 109 kB · 3 req
third party 2.16 MB · 131 req

Third parties 4 entities

245 kB transferred, 166 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

Facebook 201 kB · 131 ms CPU
LinkedIn Ads 43.0 kB · 35 ms CPU
Other Google APIs/SDKs 713 B · 0 ms CPU
Bing Ads 177 B · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 7.14 s — — 7.14 s 7.14 s
Long Tasks 20 — — 20 20
DOM Elements 2,281 — — 2,281 2,281
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 1 — — 1 1
A11y Failures 1 — — 1 1
A11y Failing Nodes 1 — — 1 1

Main thread work

script evaluation 3.58 s
other 1.53 s
style layout 1.26 s
script parse compile 290 ms
paint composite render 250 ms
parse HTML 146 ms
garbage collection 80 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 1571 passing. This is a standalone axe run, stricter than the subset Lighthouse folds into its score above — and it is the second tiebreaker in the ranking.

  • minor aria-allowed-role — ARIA role should be appropriate for the element 1 node

Accessibility failures 1 of 34 audits

Tracked as a count, not just the score — the weighted score is coarse enough that you can ship a broken component and barely move it.

  • label-content-name-mismatch — Elements with visible text labels do not have matching accessible names. 1 node

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h3

Measurement log

Every stored run for this URL, newest first. Failures are kept as records — "this site was down on Tuesday" is data too.

When PerfLCPCLSTBTWeight RunsSpreadBenchTook
Aug 25, 2026, 1:50 PM UTC 44 6.00 s 0.024 1.73 s 2.16 MB 3/3 ±1 2,459 86s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show shopify.com's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify2-score.js component code into your site! 

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://www.shopify.com/"></speedlify2-score>