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 ·

11ty-beer.vercel.app

https://11ty-beer.vercel.app/

100 98 100 100 –CWV 2AXE

Data from Aug 20, 2026, 7:03 PM UTC — 24h old.

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

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.2 Built with Eleventy 3.1.2
Vercel Hosted by Vercel

Scores

100
Performance
no change
98
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.55 s — — 1.55 s 1.55 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.08 s — — 1.08 s 1.08 s
Speed Index 1.08 s — — 1.08 s 1.08 s
TTFB Time to First Byte 626 ms — — 626 ms 626 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 78 ms
resource load delay 64 ms
resource load duration 30 ms
time to first byte 21 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 2.37 MB — — 2.37 MB 2.37 MB
Requests 32 — — 32 32
Third-party Weight 2.0 kB — — 2.0 kB 2.0 kB
Third-party CPU 2 ms — — 2 ms 2 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 14.5 kB — — 14.5 kB 14.5 kB

By resource type

font 1.97 MB · 1 req
image 235.0 kB · 3 req
script 111.7 kB · 15 req
stylesheet 31.0 kB · 5 req
document 13.8 kB · 2 req
other 11.7 kB · 6 req
third party 329.4 kB · 20 req

Third parties 1 entities

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

giscus.app 2.0 kB · 2 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 535 ms — — 535 ms 535 ms
Long Tasks 1 — — 1 1
DOM Elements 508 — — 508 508
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 1 — — 1 1

Main thread work

style layout 221 ms
other 213 ms
script evaluation 56 ms
paint composite render 23 ms
parse HTML 18 ms
script parse compile 5 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 2 rules, 382 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
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

Accessibility failures 1 of 25 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 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, 7:03 PM UTC 100 1.55 s 0 0 ms 2.37 MB 3/3 ±44 3,028 27.3s

Embed this score

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