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 ·

statisweb.pages.dev

https://statisweb.pages.dev/

83 85 100 100 CWV 14AXE

Data from Aug 21, 2026, 3:52 PM UTC — 3h old.

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

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

Scores

83
Performance
no change
85
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.92 s 1.92 s 1.92 s
CLS Cumulative Layout Shift 0.293 0.293 0.293
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 1.92 s 1.92 s 1.92 s
Speed Index 1.92 s 1.92 s 1.92 s
TTFB Time to First Byte 490 ms 490 ms 490 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 118 ms
time to first byte 47 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 119.8 kB 119.8 kB 119.8 kB
Requests 8 8 8
Third-party Weight 115.2 kB 115.2 kB 115.2 kB
Third-party CPU 0 ms 0 ms 0 ms
Unused JS 0 B 0 B 0 B
Unused CSS 27.8 kB 27.8 kB 27.8 kB

By resource type

font 83.3 kB · 2 req
stylesheet 31.2 kB · 4 req
document 3.6 kB · 1 req
other 1.7 kB · 1 req
third party 115.2 kB · 6 req

Third parties 3 entities

115.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 84.6 kB · 0 ms CPU
JSDelivr CDN 28.9 kB · 0 ms CPU
11ty.dev 1.7 kB · 0 ms CPU

Page health

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

Main thread work

other 87 ms
style layout 76 ms
parse HTML 14 ms
script evaluation 12 ms
paint composite render 12 ms
script parse compile 0 ms

Axe violations axe-core 4.13.0, full rule set

14 violating nodes across 3 rules, 239 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 color-contrast — Elements must meet minimum color contrast ratio thresholds 8 nodes
  • moderate region — All page content should be contained by landmarks 4 nodes
  • moderate heading-order — Heading levels should only increase by one 2 nodes

Accessibility failures 2 of 11 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.

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 8 nodes
  • heading-order — Heading elements are not in a sequentially-descending order 2 nodes

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h3

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 21, 2026, 3:52 PM UTC 83 1.92 s 0.293 0 ms 119.8 kB 3/3 ±3 2,308 23s

Embed this score

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