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 ·

designsystem.webstandards.ca.gov

https://designsystem.webstandards.ca.gov/

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

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

This URL redirects to https://designsystem.ca.gov/.

Lighthouse follows the redirect, so the numbers below describe the destination page, not this one. Not yet confirmed as a move; it needs to lead to the same place on several consecutive runs first.

Scores

77
Performance
no change
95
Accessibility
no change
100
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 3.89 s — — 3.89 s 3.89 s
CLS Cumulative Layout Shift 0.037 — — 0.037 0.037
TBT Total Blocking Time 241 ms — — 241 ms 241 ms
FCP First Contentful Paint 3.21 s — — 3.21 s 3.21 s
Speed Index 3.21 s — — 3.21 s 3.21 s
TTFB Time to First Byte 606 ms — — 606 ms 606 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.

element render delay 89 ms
time to first byte 11 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 367.7 kB — — 367.7 kB 367.7 kB
Requests 9 — — 9 9
Third-party Weight 357.0 kB — — 357.0 kB 357.0 kB
Third-party CPU 100 ms — — 100 ms 100 ms
Unused JS 141.9 kB — — 141.9 kB 141.9 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

script 319.9 kB · 2 req
font 35.9 kB · 1 req
image 2.8 kB · 1 req
stylesheet 2.8 kB · 2 req
document 1.7 kB · 1 req
other 150 B · 1 req
third party 357.0 kB · 4 req

Third parties 2 entities

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

Google Tag Manager 319.9 kB · 100 ms CPU
Google Fonts 37.1 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 563 ms — — 563 ms 563 ms
Long Tasks 3 — — 3 3
DOM Elements 28 — — 28 28
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 325 ms
script parse compile 98 ms
other 90 ms
style layout 37 ms
parse HTML 7 ms
paint composite render 6 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 68 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.

  • serious aria-hidden-focus — ARIA hidden element must not be focusable or contain focusable elements 1 node

Accessibility failures 1 of 18 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.

  • aria-hidden-focus — `[aria-hidden="true"]` elements contain focusable descendents 1 node

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, 8:30 PM UTC 77 3.89 s 0.037 241 ms 367.7 kB 3/3 ±5 2,493 21.6s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show designsystem.webstandards.ca.gov'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://designsystem.webstandards.ca.gov/"></speedlify-score>