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 ·

jensa.dev

https://jensa.dev/

99 96 100 100 –CWV 2AXE

Data from Aug 21, 2026, 1:19 AM UTC — 17h old.

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

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

99
Performance
no change
96
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.72 s — — 1.72 s 1.72 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.58 s — — 1.58 s 1.58 s
Speed Index 1.58 s — — 1.58 s 1.58 s
TTFB Time to First Byte 652 ms — — 652 ms 652 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 182 ms
time to first byte 56 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 95.0 kB — — 95.0 kB 95.0 kB
Requests 10 — — 10 10
Third-party Weight 1.6 kB — — 1.6 kB 1.6 kB
Third-party CPU 2 ms — — 2 ms 2 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

font 65.4 kB · 2 req
other 14.0 kB · 2 req
script 8.2 kB · 3 req
stylesheet 3.8 kB · 1 req
document 3.3 kB · 1 req
third party 1.6 kB · 2 req

Third parties 1 entities

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

counter.dev 1.6 kB · 2 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 134 ms — — 134 ms 134 ms
Long Tasks 0 — — 0 0
DOM Elements 123 — — 123 123
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 9 — — 9 9

Main thread work

other 75 ms
script evaluation 24 ms
style layout 20 ms
parse HTML 7 ms
paint composite render 5 ms
script parse compile 3 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 2 rules, 289 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 color-contrast — Elements must meet minimum color contrast ratio thresholds 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

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

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 9 nodes

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, 1:19 AM UTC 99 1.72 s 0 0 ms 95.0 kB 3/3 ±1 3,370 23.3s

Embed this score

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