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-serene.vercel.app

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

99 84 100 90 CWV 8AXE

Data from Aug 20, 2026, 7:05 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.

Vercel Hosted by Vercel

Scores

99
Performance
no change
84
Accessibility
no change
100
Best Practices
no change
90
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.71 s 1.71 s 1.71 s
CLS Cumulative Layout Shift 0.006 0.006 0.006
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 1.71 s 1.71 s 1.71 s
Speed Index 1.71 s 1.71 s 1.71 s
TTFB Time to First Byte 623 ms 623 ms 623 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 22 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 463.1 kB 463.1 kB 463.1 kB
Requests 9 9 9
Third-party Weight 460.0 kB 460.0 kB 460.0 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 457.5 kB · 3 req
stylesheet 4.0 kB · 4 req
document 1.1 kB · 1 req
script 494 B · 1 req
third party 460.0 kB · 6 req

Third parties 1 entities

460.0 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 460.0 kB · 0 ms CPU

Page health

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

Main thread work

other 73 ms
style layout 38 ms
script evaluation 14 ms
paint composite render 8 ms
parse HTML 6 ms
script parse compile 1 ms

Axe violations axe-core 4.13.0, full rule set

8 violating nodes across 4 rules, 101 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 link-in-text-block — Links must be distinguishable without relying on color 5 nodes
  • critical label — Form elements must have labels 1 node
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • moderate region — All page content should be contained by landmarks 1 node

Accessibility failures 3 of 17 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.

  • link-in-text-block — Links rely on color to be distinguishable. 5 nodes
  • label — Form elements do not have associated labels 1 node
  • landmark-one-main — Document does not have a main landmark. 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:05 PM UTC 99 1.71 s 0.006 0 ms 463.1 kB 3/3 ±6 3,010 20s

Embed this score

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