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 ·

developers.thegreenwebfoundation.org

https://developers.thegreenwebfoundation.org/

99 94 100 100 CWV 33AXE

Data from Aug 20, 2026, 9:29 PM UTC — 21h old.

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

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 Built with Eleventy
Cloudflare Hosted by Cloudflare

Scores

99
Performance
no change
94
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.83 s 1.83 s 1.83 s
CLS Cumulative Layout Shift 0.028 0.028 0.028
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 1.68 s 1.68 s 1.68 s
Speed Index 1.68 s 1.68 s 1.68 s
TTFB Time to First Byte 619 ms 619 ms 619 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 51 ms
time to first byte 39 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 47.4 kB 47.4 kB 47.4 kB
Requests 11 11 11
Third-party Weight 20.5 kB 20.5 kB 20.5 kB
Third-party CPU 7 ms 7 ms 7 ms
Unused JS 0 B 0 B 0 B
Unused CSS 11.5 kB 11.5 kB 11.5 kB

By resource type

script 20.3 kB · 3 req
document 19.8 kB · 1 req
image 5.0 kB · 2 req
other 2.3 kB · 5 req
third party 20.5 kB · 6 req

Third parties 3 entities

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

Cloudflare 11.5 kB · 3 ms CPU
GitHub 6.9 kB · 1 ms CPU
Cabin 2.2 kB · 2 ms CPU

Page health

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

Main thread work

other 129 ms
style layout 79 ms
script evaluation 48 ms
parse HTML 26 ms
paint composite render 18 ms
script parse compile 4 ms

Axe violations axe-core 4.13.0, full rule set

33 violating nodes across 3 rules, 512 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 29 nodes
  • serious link-name — Links must have discernible text 3 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node

Accessibility failures 2 of 23 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-name — Links do not have a discernible name 3 nodes
  • 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, 9:29 PM UTC 99 1.83 s 0.028 0 ms 47.4 kB 3/3 ±2 2,380 23.8s

Embed this score

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