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 ·

crlf.link

https://crlf.link/

88 83 100 83 –CWV 6AXE

Data from Aug 20, 2026, 7:31 PM UTC — 23h old.

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

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

88
Performance
no change
83
Accessibility
no change
100
Best Practices
no change
83
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 3.79 s — — 3.79 s 3.79 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.45 s — — 1.45 s 1.45 s
Speed Index 2.80 s — — 2.80 s 2.80 s
TTFB Time to First Byte 697 ms — — 697 ms 697 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 1.24 s
time to first byte 93 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 2.00 s — 0 2.00 s 960 ms
2026-07-04 2.05 s — 0 2.04 s 1.09 s
2026-06-27 2.04 s — 0 2.04 s 1.07 s
2026-06-20 2.07 s — 0 2.06 s 1.09 s
2026-06-13 2.04 s — 0 2.04 s 1.12 s
2026-06-06 — — — — —
2026-05-30 — — — — —

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 331.2 kB — — 331.2 kB 331.2 kB
Requests 8 — — 8 8
Third-party Weight 320 B — — 320 B 320 B
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

font 321.7 kB · 2 req
stylesheet 4.0 kB · 1 req
document 2.2 kB · 1 req
script 1.2 kB · 1 req
image 320 B · 1 req
other 37 B · 1 req
third party 320 B · 1 req

Third parties 1 entities

320 B transferred, 0 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

xxiivv.com 320 B · 0 ms CPU

Page health

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

Main thread work

other 103 ms
style layout 51 ms
script evaluation 17 ms
parse HTML 6 ms
paint composite render 4 ms
script parse compile 1 ms

Axe violations axe-core 4.13.0, full rule set

6 violating nodes across 6 rules, 130 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
  • critical image-alt — Images must have alternative text 1 node
  • moderate landmark-banner-is-top-level — Banner landmark should not be contained in another landmark 1 node
  • moderate landmark-no-duplicate-banner — Document should not have more than one banner landmark 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node
  • serious link-name — Links must have discernible text 1 node

Accessibility failures 3 of 17 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
  • image-alt — Image elements do not have `[alt]` attributes 1 node
  • link-name — Links do not have a discernible name 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, 7:31 PM UTC 88 3.79 s 0 0 ms 331.2 kB 3/3 ±10 2,492 23.7s

Embed this score

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