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 ·

cri.dev

https://cri.dev/

100 95 96 100 –CWV 5AXE

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

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

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.

Cloudflare Hosted by Cloudflare

Scores

100
Performance
no change
95
Accessibility
no change
96
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.68 s — — 1.68 s 1.68 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 839 ms — — 839 ms 839 ms
Speed Index 839 ms — — 839 ms 839 ms
TTFB Time to First Byte 490 ms — — 490 ms 490 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 84 ms
time to first byte 26 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 17.8 kB — — 17.8 kB 17.8 kB
Requests 10 — — 10 10
Third-party Weight 0 B — — 0 B 0 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

document 8.9 kB · 1 req
script 5.7 kB · 3 req
other 3.2 kB · 4 req

Page health

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

Main thread work

other 361 ms
style layout 156 ms
paint composite render 135 ms
script evaluation 36 ms
parse HTML 12 ms
script parse compile 5 ms

Axe violations axe-core 4.13.0, full rule set

5 violating nodes across 2 rules, 190 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.

  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 4 nodes
  • moderate region — All page content should be contained by landmarks 1 node

Accessibility failures 1 of 21 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.

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 4 nodes

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h3 1 console error

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:36 PM UTC 100 1.68 s 0 0 ms 17.8 kB 3/3 ±0 2,417 26.5s

Embed this score

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