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 ·

bruijn.me

https://bruijn.me/

70 75 100 92 CWV 10AXE

Data from Aug 20, 2026, 4:23 PM UTC — 26h old.

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

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 2.0.1 Built with Eleventy 2.0.1
GitHub Pages Hosted by GitHub Pages

Scores

70
Performance
no change
75
Accessibility
no change
100
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 21.68 s 21.68 s 21.68 s
CLS Cumulative Layout Shift 0.121 0.121 0.121
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 1.57 s 1.57 s 1.57 s
Speed Index 2.68 s 2.68 s 2.68 s
TTFB Time to First Byte 490 ms 490 ms 490 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 62 ms
resource load duration 55 ms
time to first byte 54 ms
resource load delay 11 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 3.89 MB 3.89 MB 3.89 MB
Requests 16 16 16
Third-party Weight 14.8 kB 14.8 kB 14.8 kB
Third-party CPU 4 ms 4 ms 4 ms
Unused JS 39.3 kB 39.3 kB 39.3 kB
Unused CSS 0 B 0 B 0 B

By resource type

image 3.78 MB · 5 req
script 84.3 kB · 3 req
font 17.4 kB · 2 req
stylesheet 5.1 kB · 1 req
document 3.4 kB · 1 req
other 1.1 kB · 4 req
third party 14.8 kB · 4 req

Third parties 2 entities

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

Cloudflare 11.4 kB · 3 ms CPU
umami.is 3.3 kB · 2 ms CPU

Page health

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

Main thread work

other 421 ms
style layout 397 ms
script evaluation 221 ms
paint composite render 96 ms
script parse compile 27 ms
parse HTML 7 ms

Axe violations axe-core 4.13.0, full rule set

10 violating nodes across 4 rules, 236 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.

  • critical aria-valid-attr — ARIA attributes must conform to valid names 4 nodes
  • critical image-alt — Images must have alternative text 4 nodes
  • critical button-name — Buttons must have discernible text 1 node
  • serious list — <ul> and <ol> must only directly contain <li>, <script> or <template> elements 1 node

Accessibility failures 4 of 20 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.

  • aria-valid-attr — `[aria-*]` attributes are not valid or misspelled 4 nodes
  • image-alt — Image elements do not have `[alt]` attributes 4 nodes
  • button-name — Buttons do not have an accessible name 1 node
  • list — Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`). 1 node

Hygiene

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

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h3

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, 4:23 PM UTC 70 21.68 s 0.121 0 ms 3.89 MB 3/3 ±26 3,225 32s

Embed this score

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