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 ·

11st.frede.dev

https://11st.frede.dev/

99 100 100 100 1AXE –CWV

Data from Aug 20, 2026, 7:03 PM UTC 3d old

Build Awesome Starters #61 · 1 measurement · since Aug 20, 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.

Self-hosted · Caddy Hosted by Self-hosted

Scores

99
Performance
no change
100
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.60 s — — 1.60 s 1.60 s
CLS Cumulative Layout Shift 0.017 — — 0.017 0.017
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.60 s — — 1.60 s 1.60 s
Speed Index 1.60 s — — 1.60 s 1.60 s
TTFB Time to First Byte 694 ms — — 694 ms 694 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.60 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 129 ms
time to first byte 96 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 383 kB — — 383 kB 383 kB
Requests 8 — — 8 8
Third-party Weight 367 kB — — 367 kB 367 kB
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

font 353 kB · 1 req
script 17.4 kB · 1 req
stylesheet 7.5 kB · 3 req
document 3.1 kB · 1 req
image 1.1 kB · 1 req
other 1.1 kB · 1 req
third party 355 kB · 3 req

Third parties 1 entities

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

rsms.me 367 kB · 0 ms CPU

Page health

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

Main thread work

other 107 ms
style layout 59 ms
script evaluation 36 ms
paint composite render 11 ms
parse HTML 10 ms
script parse compile 1 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 139 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.

  • moderate region — All page content should be contained by landmarks 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, 7:03 PM UTC 99 1.60 s 0.017 0 ms 383 kB 3/3 ±1 2,391 25.4s

Embed this score

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