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 ·

ted.dev

https://ted.dev/

95 95 77 100 –CWV 2AXE

Data from Aug 21, 2026, 9:37 AM UTC — 9h old.

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

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

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

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.03 s — — 2.03 s 2.03 s
CLS Cumulative Layout Shift 0.113 — — 0.113 0.113
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.70 s — — 1.70 s 1.70 s
Speed Index 1.70 s — — 1.70 s 1.70 s
TTFB Time to First Byte 635 ms — — 635 ms 635 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 100 ms
time to first byte 37 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 280.3 kB — — 280.3 kB 280.3 kB
Requests 17 — — 17 17
Third-party Weight 255.3 kB — — 255.3 kB 255.3 kB
Third-party CPU 5 ms — — 5 ms 5 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

font 234.2 kB · 3 req
script 19.8 kB · 4 req
stylesheet 10.8 kB · 3 req
document 9.0 kB · 1 req
other 2.1 kB · 5 req
third party 255.6 kB · 10 req

Third parties 4 entities

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

Google Fonts 235.6 kB · 0 ms CPU
convertkit.com 15.0 kB · 4 ms CPU
Unpkg 3.6 kB · 1 ms CPU
JSDelivr CDN 1.1 kB · 0 ms CPU

Page health

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

Main thread work

other 127 ms
style layout 118 ms
script evaluation 43 ms
parse HTML 19 ms
paint composite render 19 ms
script parse compile 10 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 2 rules, 253 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 link-in-text-block — Links must be distinguishable without relying on color 1 node
  • moderate region — All page content should be contained by landmarks 1 node

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

  • link-in-text-block — Links rely on color to be distinguishable. 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 21, 2026, 9:37 AM UTC 95 2.03 s 0.113 0 ms 280.3 kB 3/3 ±3 2,367 22.6s

Embed this score

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