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 ·

journa11ty.pages.dev

https://journa11ty.pages.dev/

97 97 100 91 –CWV 1AXE

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

Build Awesome Starters · 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 3.1.0 Built with Eleventy 3.1.0
Cloudflare Hosted by Cloudflare

Scores

97
Performance
no change
97
Accessibility
no change
100
Best Practices
no change
91
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.04 s — — 2.04 s 2.04 s
CLS Cumulative Layout Shift 0.004 — — 0.004 0.004
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 2.04 s — — 2.04 s 2.04 s
Speed Index 2.04 s — — 2.04 s 2.04 s
TTFB Time to First Byte 482 ms — — 482 ms 482 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 113 ms
time to first byte 34 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 114.4 kB — — 114.4 kB 114.4 kB
Requests 12 — — 12 12
Third-party Weight 67.9 kB — — 67.9 kB 67.9 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 65.7 kB · 2 req
script 24.2 kB · 3 req
stylesheet 20.4 kB · 5 req
document 2.0 kB · 1 req
third party 67.9 kB · 3 req

Third parties 1 entities

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

Google Fonts 67.9 kB · 0 ms CPU

Page health

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

Main thread work

other 74 ms
style layout 43 ms
script evaluation 21 ms
parse HTML 16 ms
script parse compile 7 ms
paint composite render 6 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 217 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 heading-order — Heading levels should only increase by one 1 node

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

  • heading-order — Heading elements are not in a sequentially-descending order 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 21, 2026, 1:22 AM UTC 97 2.04 s 0.004 0 ms 114.4 kB 3/3 ±12 3,356 21.7s

Embed this score

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