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 ·

webwewant.fyi

https://webwewant.fyi/

96 100 100 100 –CWV 1AXE

Data from Aug 21, 2026, 5:13 PM UTC — 1h old.

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

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.1.2 Built with Eleventy 3.1.2
Netlify Hosted by Netlify

Scores

96
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 2.30 s — — 2.30 s 2.30 s
CLS Cumulative Layout Shift 0.003 — — 0.003 0.003
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 2.30 s — — 2.30 s 2.30 s
Speed Index 2.30 s — — 2.30 s 2.30 s
TTFB Time to First Byte 604 ms — — 604 ms 604 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 98 ms
time to first byte 6 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 78.7 kB — — 78.7 kB 78.7 kB
Requests 8 — — 8 8
Third-party Weight 16.6 kB — — 16.6 kB 16.6 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 43.2 kB · 1 req
font 15.9 kB · 2 req
document 9.4 kB · 1 req
other 9.4 kB · 3 req
stylesheet 631 B · 1 req
third party 16.6 kB · 3 req

Third parties 1 entities

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

Page health

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

Main thread work

other 113 ms
style layout 90 ms
script evaluation 14 ms
paint composite render 12 ms
parse HTML 12 ms
script parse compile 3 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 237 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 page-has-heading-one — Page should contain a level-one heading 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 21, 2026, 5:13 PM UTC 96 2.30 s 0.003 0 ms 78.7 kB 3/3 ±2 2,477 21.6s

Embed this score

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