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 ·

chringel.dev

https://chringel.dev/

90 100 96 100 –CWV 0AXE

Data from Aug 20, 2026, 7:39 PM UTC — 23h old.

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

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

Scores

90
Performance
no change
100
Accessibility
no change
96
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.27 s — — 1.27 s 1.27 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 28 ms — — 28 ms 28 ms
FCP First Contentful Paint 1.13 s — — 1.13 s 1.13 s
Speed Index 14.99 s — — 14.99 s 14.99 s
TTFB Time to First Byte 10.09 s — — 10.09 s 10.09 s

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.

time to first byte 10.09 s
resource load duration 252 ms
resource load delay 75 ms
element render delay 24 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 203.1 kB — — 203.1 kB 203.1 kB
Requests 20 — — 20 20
Third-party Weight 55.3 kB — — 55.3 kB 55.3 kB
Third-party CPU 25 ms — — 25 ms 25 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 21.3 kB — — 21.3 kB 21.3 kB

By resource type

image 106.4 kB · 9 req
script 58.0 kB · 4 req
font 23.6 kB · 2 req
stylesheet 8.5 kB · 2 req
document 4.2 kB · 1 req
other 2.4 kB · 1 req
third party 55.3 kB · 1 req

Third parties 1 entities

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

Netlify 55.3 kB · 25 ms CPU

Page health

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

Main thread work

other 266 ms
script evaluation 84 ms
style layout 81 ms
garbage collection 38 ms
paint composite render 37 ms
script parse compile 23 ms
parse HTML 15 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 215 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 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:39 PM UTC 90 1.27 s 0 28 ms 203.1 kB 2/3 ±10 2,378 108s

Embed this score

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