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 ·

engaged.ca.gov

https://engaged.ca.gov/

84 100 100 92 CWV 0AXE

Data from Aug 20, 2026, 9:29 PM UTC — 21h old.

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

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.

Amazon S3 Hosted by Amazon S3

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-07-19 → 2026-08-15). From the backfilled CrUX history rather than this measurement, which predates the API key. This is what Google measures you on.

LCP no data
INP no data
CLS no data

Scores

84
Performance
no change
100
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 3.84 s 3.84 s 3.84 s
CLS Cumulative Layout Shift 0.005 0.005 0.005
TBT Total Blocking Time 218 ms 218 ms 218 ms
FCP First Contentful Paint 1.81 s 1.81 s 1.81 s
Speed Index 1.81 s 1.81 s 1.81 s
TTFB Time to First Byte 613 ms 613 ms 613 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 126 ms
time to first byte 14 ms

Field history 25 weeks

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

Week ending LCPINPCLSFCPTTFB
2026-08-15
2026-08-08
2026-08-01
2026-07-25
2026-07-18
2026-07-11
2026-07-04
2026-06-27 858 ms 0 988 ms 261 ms
2026-06-20 1.02 s 0 1.06 s 306 ms
2026-06-13 1.06 s 0 1.10 s 299 ms
2026-06-06 1.10 s 0 1.19 s 327 ms
2026-05-30 1.08 s 0 1.08 s 277 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.40 MB 1.40 MB 1.40 MB
Requests 39 39 39
Third-party Weight 522.0 kB 522.0 kB 522.0 kB
Third-party CPU 116 ms 116 ms 116 ms
Unused JS 236.7 kB 236.7 kB 236.7 kB
Unused CSS 42.9 kB 42.9 kB 42.9 kB

By resource type

image 672.6 kB · 23 req
script 498.3 kB · 6 req
font 145.0 kB · 3 req
stylesheet 73.4 kB · 4 req
document 8.3 kB · 1 req
other 1.7 kB · 1 req
third party 522.0 kB · 6 req

Third parties 2 entities

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

Google Tag Manager 464.7 kB · 116 ms CPU
Google Fonts 57.3 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 988 ms 988 ms 988 ms
Long Tasks 4 4 4
DOM Elements 219 219 219
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 0 0 0
A11y Failures 0 0 0
A11y Failing Nodes 0 0 0

Main thread work

script evaluation 407 ms
other 256 ms
style layout 159 ms
script parse compile 104 ms
parse HTML 33 ms
paint composite render 29 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 452 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.

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, 9:29 PM UTC 84 3.84 s 0.005 218 ms 1.40 MB 3/3 ±10 3,231 27.7s

Embed this score

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