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 ·

hamatti.org

https://hamatti.org/

94 96 100 100 ✓CWV 0AXE

Data from Aug 20, 2026, 11:31 PM UTC — 19h old.

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

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.

Eleventy 2.0.1 Built with Eleventy 2.0.1
Netlify Hosted by Netlify

Core Web Vitals field data, origin-level

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

LCP 2.04 s good
INP — no data
CLS 0 good

Scores

94
Performance
no change
96
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 1.20 s — — 1.20 s 1.20 s
CLS Cumulative Layout Shift 0.151 — — 0.151 0.151
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.04 s — — 1.04 s 1.04 s
Speed Index 1.04 s — — 1.04 s 1.04 s
TTFB Time to First Byte 675 ms — — 675 ms 675 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 167 ms
time to first byte 74 ms
resource load delay 73 ms
element render delay 19 ms

Field data Chrome UX Report, origin-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 2.04 s good 86.6% good
CLS CWV 0 good 97.4% good
FCP 1.82 s needs-improvement 73.8% good
TTFB 1.13 s needs-improvement 51% good

Lab vs field

Lab LCP 1.20 s · field p75 2.04 s · real users are 1.7× slower than the lab. A gap this wide usually means real users are on slower devices or networks than the simulated ones — the lab number is flattering you.

Field history 25 weeks

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

Week ending LCPINPCLSFCPTTFB
2026-08-15 2.04 s — 0 1.80 s 1.12 s
2026-08-08 1.97 s — 0 1.69 s 1.08 s
2026-08-01 1.83 s — 0 1.63 s 907 ms
2026-07-25 1.87 s — 0 1.68 s 907 ms
2026-07-18 2.04 s — 0 1.92 s 1.02 s
2026-07-11 2.04 s — 0 1.92 s 950 ms
2026-07-04 2.06 s — 0 1.95 s 1.19 s
2026-06-27 2.24 s — 0 2.16 s 1.32 s
2026-06-20 2.09 s — 0 1.90 s 1.23 s
2026-06-13 2.10 s — 0 1.97 s 1.22 s
2026-06-06 2.09 s — 0 1.89 s 1.16 s
2026-05-30 2.04 s — 0 1.74 s 1.04 s

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 2.63 MB — — 2.63 MB 2.63 MB
Requests 61 — — 61 61
Third-party Weight 1.37 MB — — 1.37 MB 1.37 MB
Third-party CPU 0 ms — — 0 ms 0 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

media 1.63 MB · 4 req
image 953.9 kB · 25 req
stylesheet 17.1 kB · 21 req
document 15.4 kB · 1 req
font 12.7 kB · 1 req
other 5.6 kB · 2 req
script 1.0 kB · 1 req
third party 1.63 MB · 4 req

Third parties 1 entities

1.37 MB transferred, 0 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

Amazon Web Services 1.37 MB · 0 ms CPU

Page health

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

Main thread work

other 341 ms
style layout 168 ms
paint composite render 85 ms
script evaluation 30 ms
parse HTML 27 ms
script parse compile 1 ms

Axe violations axe-core 4.13.0, full rule set

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

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

  • target-size — Touch targets do not have sufficient size or spacing. 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, 11:31 PM UTC 94 1.20 s 0.151 0 ms 2.63 MB 3/3 ±6 2,509 30.6s

Embed this score

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