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 ·

courtnotes.netlify.app

https://courtnotes.netlify.app/

81 95 96 92 –CWV 26AXE

Data from Aug 20, 2026, 7:08 PM UTC — 24h old.

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

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 Built with Eleventy
Netlify Hosted by Netlify

Scores

81
Performance
no change
95
Accessibility
no change
96
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.97 s — — 1.97 s 1.97 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 730 ms — — 730 ms 730 ms
FCP First Contentful Paint 838 ms — — 838 ms 838 ms
Speed Index 838 ms — — 838 ms 838 ms
TTFB Time to First Byte 666 ms — — 666 ms 666 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 144 ms
time to first byte 23 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 10.33 MB — — 10.33 MB 10.33 MB
Requests 11 — — 11 11
Third-party Weight 55.3 kB — — 55.3 kB 55.3 kB
Third-party CPU 19 ms — — 19 ms 19 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 21.3 kB — — 21.3 kB 21.3 kB

By resource type

image 10.27 MB · 7 req
script 55.3 kB · 1 req
document 4.9 kB · 1 req
stylesheet 2.8 kB · 1 req
other 41 B · 1 req
third party 55.3 kB · 1 req

Third parties 1 entities

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

Netlify 55.3 kB · 19 ms CPU

Page health

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

Main thread work

other 944 ms
script evaluation 74 ms
style layout 35 ms
script parse compile 20 ms
parse HTML 11 ms
paint composite render 9 ms

Axe violations axe-core 4.13.0, full rule set

26 violating nodes across 2 rules, 257 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 color-contrast — Elements must meet minimum color contrast ratio thresholds 25 nodes
  • moderate page-has-heading-one — Page should contain a level-one heading 1 node

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

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 25 nodes

Hygiene

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

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2 1 console error

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, 7:08 PM UTC 81 1.97 s 0 730 ms 10.33 MB 3/3 ±10 3,027 25.8s

Embed this score

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