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 ·

conf.11ty.dev

https://conf.11ty.dev/

99 100 100 100 –CWV 2AXE

Data from Aug 20, 2026, 7:35 PM UTC — 23h old.

Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 23h

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.0.0 Built with Eleventy 3.0.0
Vercel Hosted by Vercel

Scores

99
Performance
no change
100
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.75 s — — 1.75 s 1.75 s
CLS Cumulative Layout Shift 0.018 — — 0.018 0.018
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.67 s — — 1.67 s 1.67 s
Speed Index 1.67 s — — 1.67 s 1.67 s
TTFB Time to First Byte 618 ms — — 618 ms 618 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 49 ms
resource load delay 49 ms
resource load duration 28 ms
time to first byte 14 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 100.7 kB — — 100.7 kB 100.7 kB
Requests 17 — — 17 17
Third-party Weight 12.2 kB — — 12.2 kB 12.2 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

image 61.0 kB · 11 req
document 21.3 kB · 1 req
font 12.2 kB · 1 req
script 4.5 kB · 1 req
other 1.7 kB · 1 req
third party 12.2 kB · 1 req

Third parties 1 entities

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

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 333 ms — — 333 ms 333 ms
Long Tasks 0 — — 0 0
DOM Elements 387 — — 387 387
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 143 ms
style layout 88 ms
script evaluation 56 ms
paint composite render 32 ms
parse HTML 11 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 1 rule, 749 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, 7:35 PM UTC 99 1.75 s 0.018 0 ms 100.7 kB 3/3 ±0 2,368 23.6s

Embed this score

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