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 ·

ffconf.org

https://ffconf.org/

99 91 100 100 –CWV 5AXE

Data from Aug 20, 2026, 9:34 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.

Netlify Hosted by Netlify

Core Web Vitals field data, origin-level

Real Chrome users, 28-day window (2026-07-19 → 2026-08-15). From the backfilled CrUX history rather than this measurement, which predates the API key. This is what Google measures you on.

LCP — no data
INP — no data
CLS — no data

Scores

99
Performance
no change
91
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.69 s — — 1.69 s 1.69 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.69 s — — 1.69 s 1.69 s
Speed Index 1.69 s — — 1.69 s 1.69 s
TTFB Time to First Byte 654 ms — — 654 ms 654 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 181 ms
time to first byte 53 ms

Field history 25 weeks

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

Week ending LCPINPCLSFCPTTFB
2026-08-15 — — — — —
2026-08-08 — — — — —
2026-08-01 — — — — —
2026-07-25 — — — — —
2026-07-18 — — — — —
2026-07-11 — — — — —
2026-07-04 — — — — —
2026-06-27 — — — — —
2026-06-20 — — — — —
2026-06-13 — — — — —
2026-06-06 — — — — —
2026-05-30 — — — — —

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 133.5 kB — — 133.5 kB 133.5 kB
Requests 24 — — 24 24
Third-party Weight 2.7 kB — — 2.7 kB 2.7 kB
Third-party CPU 2 ms — — 2 ms 2 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

image 89.4 kB · 13 req
font 25.5 kB · 2 req
stylesheet 8.2 kB · 4 req
document 7.1 kB · 2 req
script 2.2 kB · 1 req
other 1.1 kB · 2 req
third party 2.7 kB · 2 req

Third parties 1 entities

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

Plausible 2.7 kB · 2 ms CPU

Page health

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

Main thread work

other 300 ms
style layout 100 ms
paint composite render 80 ms
script evaluation 24 ms
parse HTML 11 ms
script parse compile 3 ms

Axe violations axe-core 4.13.0, full rule set

5 violating nodes across 2 rules, 244 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 4 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 1 node

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

  • target-size — Touch targets do not have sufficient size or spacing. 8 nodes
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 3 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, 9:34 PM UTC 99 1.69 s 0 0 ms 133.5 kB 3/3 ±5 3,363 26.1s

Embed this score

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