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 ·

cfp.watch

https://cfp.watch/

98 98 100 100 –CWV 2AXE

Data from Aug 20, 2026, 4:29 PM UTC — 26h old.

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

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

Scores

98
Performance
no change
98
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.34 s — — 2.34 s 2.34 s
CLS Cumulative Layout Shift 0.002 — — 0.002 0.002
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.57 s — — 1.57 s 1.57 s
Speed Index 1.57 s — — 1.57 s 1.57 s
TTFB Time to First Byte 634 ms — — 634 ms 634 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 111 ms
time to first byte 37 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 46.1 kB — — 46.1 kB 46.1 kB
Requests 15 — — 15 15
Third-party Weight 26.3 kB — — 26.3 kB 26.3 kB
Third-party CPU 6 ms — — 6 ms 6 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

font 14.5 kB · 1 req
document 12.2 kB · 1 req
script 11.7 kB · 5 req
stylesheet 4.2 kB · 2 req
other 1.6 kB · 3 req
third party 26.3 kB · 7 req

Third parties 3 entities

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

Google Fonts 14.9 kB · 0 ms CPU
buymeacoffee.com 6.3 kB · 4 ms CPU
Plausible 5.1 kB · 2 ms CPU

Page health

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

Main thread work

other 102 ms
style layout 47 ms
script evaluation 35 ms
parse HTML 16 ms
paint composite render 10 ms
script parse compile 4 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 2 rules, 982 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 heading-order — Heading levels should only increase by one 1 node
  • moderate region — All page content should be contained by landmarks 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.

  • heading-order — Heading elements are not in a sequentially-descending order 1 node
  • label-content-name-mismatch — Elements with visible text labels do not have matching accessible names. 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, 4:29 PM UTC 98 2.34 s 0.002 0 ms 46.1 kB 3/3 ±2 3,367 22.5s

Embed this score

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