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 ·

eleventyblog.vercel.app

https://eleventyblog.vercel.app/

79 100 96 100 –CWV 2AXE

Data from Aug 20, 2026, 9:34 PM UTC — 21h old.

Build Awesome Starters · 1 measurement · since Aug 20, 2026 · last attempt 21h

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
Vercel Hosted by Vercel

Scores

79
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 2.21 s — — 2.21 s 2.21 s
CLS Cumulative Layout Shift 0.415 — — 0.415 0.415
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.07 s — — 1.07 s 1.07 s
Speed Index 1.07 s — — 1.07 s 1.07 s
TTFB Time to First Byte 611 ms — — 611 ms 611 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.

time to first byte 102 ms
resource load duration 79 ms
element render delay 25 ms
resource load delay 24 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 542.3 kB — — 542.3 kB 542.3 kB
Requests 17 — — 17 17
Third-party Weight 364.0 kB — — 364.0 kB 364.0 kB
Third-party CPU 0 ms — — 0 ms 0 ms
Unused JS 20.7 kB — — 20.7 kB 20.7 kB
Unused CSS 28.8 kB — — 28.8 kB 28.8 kB

By resource type

image 474.4 kB · 12 req
stylesheet 31.3 kB · 2 req
script 24.8 kB · 1 req
document 11.7 kB · 1 req
third party 364.0 kB · 10 req

Third parties 3 entities

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

googleusercontent.com 228.6 kB · 0 ms CPU
pages.dev 127.2 kB · 0 ms CPU
getbootstrap.com 8.2 kB · 0 ms CPU

Page health

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

Main thread work

other 156 ms
style layout 97 ms
paint composite render 53 ms
parse HTML 21 ms
script evaluation 21 ms
script parse compile 10 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 1 rule, 852 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 2 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 20, 2026, 9:34 PM UTC 79 2.21 s 0.415 0 ms 542.3 kB 3/3 ±20 2,323 27.8s

Embed this score

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