speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time — measured continuously.

Measurement runs · Embed a score ·

speedlify.dev

https://www.speedlify.dev/

97 100 100 100 0AXE CWV

Data from Aug 23, 2026, 7:21 PM UTC 2h old

Built Awesome #223 · 3 measurements · since Aug 21, 2026

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.

GitHub Pages Hosted by GitHub Pages

Scores

97
Performance
↓ -2 (-2%)
100
Accessibility
↑ +4 (+4.2%)
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.28 s 1.28 s ↑ +1 ms (+0.1%) 793 ms 1.28 s
CLS Cumulative Layout Shift 0 0 → no change 0 0
TBT Total Blocking Time 189 ms 120 ms ↑ +69 ms (+57.5%) 0 ms 189 ms
FCP First Contentful Paint 1.20 s 1.20 s ↑ +1 ms (+0.1%) 793 ms 1.20 s
Speed Index 1.20 s 1.20 s ↑ +1 ms (+0.1%) 793 ms 1.20 s
TTFB Time to First Byte 603 ms 602 ms ↑ +1 ms (+0.2%) 602 ms 633 ms

What LCP is made of observed, unthrottled

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 1.28 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

element render delay 127 ms
time to first byte 5 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 181 kB 183 kB ↓ -2.0 kB (-1.1%) 50.4 kB 183 kB
Requests 25 27 ↓ -2 (-7.4%) 4 27
Third-party Weight 100 kB 102 kB ↓ -2.0 kB (-2%) 0 B 102 kB
Third-party CPU 0 ms 0 ms → no change 0 ms 0 ms
Unused JS 0 B 0 B → no change 0 B 21.3 kB
Unused CSS 12.2 kB 12.0 kB ↑ +224 B (+1.9%) 0 B 12.2 kB

By resource type

image 100 kB · 23 req
document 62.5 kB · 1 req
stylesheet 18.3 kB · 1 req
third party 100 kB · 23 req

Third parties 1 entities

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

11ty.dev 100 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.44 s 1.18 s ↑ +266 ms (+22.6%) 121 ms 1.44 s
Long Tasks 6 5 ↑ +1 (+20%) 0 6
DOM Elements 10,690 10,790 ↓ -100 (-0.9%) 64 10,790
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 0 0 → no change 0 0
A11y Failures 0 1 ↓ -1 (-100%) 0 1
A11y Failing Nodes 0 10 ↓ -10 (-100%) 0 10

Main thread work

style layout 492 ms
paint composite render 404 ms
other 344 ms
parse HTML 170 ms
script evaluation 30 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 26885 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 23, 2026, 7:21 PM UTC 97 1.28 s 0 189 ms 181 kB 3/3 ±7 2,386 58.5s
Aug 23, 2026, 5:19 PM UTC 99 1.28 s 0 120 ms 183 kB 3/3 ±7 2,486 56.3s
Aug 21, 2026, 1:55 PM UTC 100 793 ms 0 0 ms 50.4 kB 3/3 ±0 2,502 21.8s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show speedlify.dev's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify2-score.js component code into your site!

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://www.speedlify.dev/"></speedlify2-score>