speedlify2

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

Measurement runs · Embed a score · Field data from the Chrome UX Report ·

extensionworkshop.com

https://extensionworkshop.com/

82 93 100 92 ✓CWV 6AXE

Data from Aug 20, 2026, 10:30 PM UTC — 20h old.

Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 20h

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.

Op Hosted by Self-hosted

Core Web Vitals field data, url-level

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

LCP 1.95 s good
INP 174 ms good
CLS 0.010 good

Scores

82
Performance
no change
93
Accessibility
no change
100
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 4.75 s — — 4.75 s 4.75 s
CLS Cumulative Layout Shift 0.002 — — 0.002 0.002
TBT Total Blocking Time 107 ms — — 107 ms 107 ms
FCP First Contentful Paint 1.37 s — — 1.37 s 1.37 s
Speed Index 1.94 s — — 1.94 s 1.94 s
TTFB Time to First Byte 769 ms — — 769 ms 769 ms

What LCP is made of

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

resource load duration 221 ms
resource load delay 134 ms
time to first byte 113 ms
element render delay 30 ms

Field data Chrome UX Report, url-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.95 s good 83.6% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 174 ms good 80.2% good
CLS CWV 0.010 good 96.2% good
FCP 1.43 s good 85.6% good
TTFB 786 ms good 75.6% good

Lab vs field

Lab LCP 4.75 s · field p75 1.95 s · real users are 0.41× 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-15 1.95 s 174 ms 0.010 1.43 s 820 ms
2026-08-08 1.95 s 146 ms 0.010 1.43 s 809 ms
2026-08-01 2.08 s 157 ms 0.010 1.43 s 802 ms
2026-07-25 2.08 s 157 ms 0.010 1.40 s 790 ms
2026-07-18 2.08 s 144 ms 0.010 1.32 s 760 ms
2026-07-11 2.14 s 144 ms 0.010 1.37 s 821 ms
2026-07-04 2.13 s 129 ms 0.010 1.36 s 736 ms
2026-06-27 2.24 s 130 ms 0.010 1.48 s 734 ms
2026-06-20 2.24 s 159 ms 0.010 1.52 s 738 ms
2026-06-13 2.16 s 159 ms 0.010 1.47 s 734 ms
2026-06-06 2.17 s 159 ms 0.010 1.47 s 720 ms
2026-05-30 1.94 s 175 ms 0.010 1.39 s 692 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 777.4 kB — — 777.4 kB 777.4 kB
Requests 41 — — 41 41
Third-party Weight 183.7 kB — — 183.7 kB 183.7 kB
Third-party CPU 50 ms — — 50 ms 50 ms
Unused JS 102.0 kB — — 102.0 kB 102.0 kB
Unused CSS 33.7 kB — — 33.7 kB 33.7 kB

By resource type

script 257.7 kB · 5 req
font 248.3 kB · 3 req
image 184.4 kB · 29 req
stylesheet 38.6 kB · 1 req
document 28.1 kB · 1 req
other 20.3 kB · 2 req
third party 183.7 kB · 4 req

Third parties 3 entities

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

Google Tag Manager 158.0 kB · 47 ms CPU
Mozilla 16.0 kB · 0 ms CPU
YouTube 9.7 kB · 3 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.14 s — — 1.14 s 1.14 s
Long Tasks 4 — — 4 4
DOM Elements 1,412 — — 1,412 1,412
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 6 — — 6 6
A11y Failures 3 — — 3 3
A11y Failing Nodes 8 — — 8 8

Main thread work

script evaluation 396 ms
other 365 ms
style layout 198 ms
script parse compile 70 ms
paint composite render 64 ms
parse HTML 49 ms

Axe violations axe-core 4.13.0, full rule set

6 violating nodes across 3 rules, 638 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.

  • moderate heading-order — Heading levels should only increase by one 3 nodes
  • serious aria-hidden-focus — ARIA hidden element must not be focusable or contain focusable elements 2 nodes
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

Accessibility failures 3 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.

  • heading-order — Heading elements are not in a sequentially-descending order 4 nodes
  • link-name — Links do not have a discernible name 2 nodes
  • target-size — Touch targets do not have sufficient size or spacing. 2 nodes

Hygiene

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

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2

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 20, 2026, 10:30 PM UTC 82 4.75 s 0.002 107 ms 777.4 kB 3/3 ±22 2,349 29.8s

Embed this score

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

<speedlify-score speedlify-url="https://zachleat.github.io/speedlify2/" url="https://extensionworkshop.com/"></speedlify-score>