speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time — measured continuously.

Measurement runs · Embed a score ·

11ty.dev

https://www.11ty.dev/

100 100 100 100 0AXE ✓CWV

Data from Aug 23, 2026, 7:21 PM UTC 2h old

Site Generators #1 Built Awesome #40 · 3 measurements · since Aug 21, 2026

The measuring machine was faster than usual.

Lighthouse benchmark index was 3010 against a baseline of 2420.3 (24.4%). CPU-bound metrics — TBT, TTI, main thread work — are affected by this and may have moved without the site changing at all.

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.

Build Awesome 4.0.0 Built with Build Awesome 4.0.0
Vercel Hosted by Vercel

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-07-25 → 2026-08-21). This is what Google measures you on.

LCP 984 ms good
INP 92 ms good
CLS 0 good

Scores

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

Filmstrip Lighthouse, mobile

How the page drew during the measured load, at 8 points across 3.00 s.

  1. 375 ms
  2. 750 ms
  3. 1.13 s
  4. 1.50 s
  5. 1.88 s
  6. 2.25 s
  7. 2.63 s
  8. 3.00 s

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.29 s 1.25 s ↑ +40 ms (+3.2%) 1.21 s 1.29 s
CLS Cumulative Layout Shift 0 0 → no change 0 0
TBT Total Blocking Time 8 ms 36 ms ↓ -28 ms (-77.8%) 8 ms 36 ms
FCP First Contentful Paint 1.29 s 1.10 s ↑ +190 ms (+17.3%) significant 1.06 s 1.29 s
Speed Index 1.29 s 1.10 s ↑ +190 ms (+17.3%) significant 1.06 s 1.29 s
TTFB Time to First Byte 615 ms 649 ms ↓ -34 ms (-5.2%) 610 ms 649 ms

What LCP is made of observed, unthrottled

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 1.29 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

element render delay 96 ms
time to first byte 4 ms

Field data Chrome UX Report, url-level

Real Chrome users, 28-day trailing window (2026-07-25 → 2026-08-21). This is what Google measures you on.

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 984 ms good 93.8% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 92 ms good 93.8% good
CLS CWV 0 good 92.9% good
FCP 986 ms good 89.8% good
TTFB 514 ms good 86.6% good

Lab vs field

Lab LCP 1.29 s · field p75 984 ms · real users are 0.76× faster than the lab.

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-15 1.07 s 88 ms 0 1.07 s 560 ms
2026-08-08 1.10 s 88 ms 0 1.10 s 527 ms
2026-08-01 1.18 s 89 ms 0 1.16 s 593 ms
2026-07-25 1.21 s 93 ms 0 1.19 s 607 ms
2026-07-18 1.19 s 96 ms 0 1.19 s 607 ms
2026-07-11 1.18 s 97 ms 0 1.17 s 604 ms
2026-07-04 1.13 s 95 ms 0 1.14 s 573 ms
2026-06-27 1.10 s 89 ms 0 1.06 s 558 ms
2026-06-20 1.06 s 87 ms 0 994 ms 506 ms
2026-06-13 1.13 s 91 ms 0 953 ms 532 ms
2026-06-06 1.14 s 91 ms 0 942 ms 544 ms
2026-05-30 1.15 s 94 ms 0 938 ms 544 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 167 kB 175 kB ↓ -8.7 kB (-5.1%) 92.2 kB 175 kB
Requests 52 54 ↓ -2 (-3.7%) 11 54
Third-party Weight 0 B 0 B → no change 0 B 0 B
Third-party CPU 0 ms 0 ms → no change 0 ms 0 ms
Unused JS 0 B 0 B → no change 0 B 0 B
Unused CSS 0 B 0 B → no change 0 B 0 B

By resource type

script 89.3 kB · 41 req
document 39.6 kB · 1 req
font 21.9 kB · 2 req
stylesheet 9.3 kB · 1 req
image 3.0 kB · 1 req
other 1.7 kB · 1 req

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 759 ms 935 ms ↓ -176 ms (-18.8%) 598 ms 935 ms
Long Tasks 3 3 → no change 2 3
DOM Elements 1,541 1,541 → no change 1,489 1,541
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 0 0 → no change 0 0
A11y Failures 0 0 → no change 0 0
A11y Failing Nodes 0 0 → no change 0 0

Main thread work

style layout 304 ms
other 216 ms
script evaluation 110 ms
paint composite render 90 ms
parse HTML 34 ms
script parse compile 5 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 2466 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.

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 23, 2026, 7:21 PM UTC 100 1.29 s 0 8 ms 167 kB 3/3 ±5 3,010 34.8s
Aug 22, 2026, 6:28 PM UTC 100 1.25 s 0 36 ms 175 kB 3/3 ±10 2,370 40.5s
Aug 21, 2026, 5:28 PM UTC 100 1.21 s 0 9 ms 92.2 kB 3/3 ±1 2,471 35.5s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show 11ty.dev's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify2-score.js component code into your site! 

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://www.11ty.dev/"></speedlify2-score>