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 ·

divriots.com

https://divriots.com/

73 94 92 92 ✗CWV 43AXE

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

Cloudflare Hosted by Cloudflare

Core Web Vitals field data, origin-level

Real Chrome users, 28-day window (2026-07-22 → 2026-08-18). This is what Google measures you on.

LCP 1.32 s good
INP — no data
CLS 0.280 poor

Scores

73
Performance
no change
94
Accessibility
no change
92
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 5.39 s — — 5.39 s 5.39 s
CLS Cumulative Layout Shift 0.003 — — 0.003 0.003
TBT Total Blocking Time 22 ms — — 22 ms 22 ms
FCP First Contentful Paint 3.41 s — — 3.41 s 3.41 s
Speed Index 3.41 s — — 3.41 s 3.41 s
TTFB Time to First Byte 614 ms — — 614 ms 614 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 138 ms
resource load delay 52 ms
time to first byte 44 ms
resource load duration 25 ms

Field data Chrome UX Report, origin-level

Real Chrome users, 28-day trailing window (2026-07-22 → 2026-08-18). This is what Google measures you on.

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.32 s good 89.1% good
CLS CWV 0.280 poor 65.7% good
FCP 1.07 s good 88% good
TTFB 615 ms good 84.3% good

Lab vs field

Lab LCP 5.39 s · field p75 1.32 s · real users are 0.25× faster than the lab.

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 2.92 s — 0 2.32 s 1.41 s
2026-07-25 2.75 s — 0 2.14 s 1.39 s
2026-07-18 2.62 s — 0 1.99 s 1.33 s
2026-07-11 2.37 s — 0 1.95 s 1.28 s
2026-07-04 2.34 s — 0 1.74 s 1.27 s
2026-06-27 2.27 s — 0 1.70 s 1.20 s
2026-06-20 2.27 s — 0 1.66 s 1.20 s
2026-06-13 2.33 s — 0 1.66 s 1.20 s
2026-06-06 2.10 s — 0 1.45 s 960 ms
2026-05-30 2.08 s — 0.010 1.77 s 883 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 935.0 kB — — 935.0 kB 935.0 kB
Requests 39 — — 39 39
Third-party Weight 657.7 kB — — 657.7 kB 657.7 kB
Third-party CPU 4 ms — — 4 ms 4 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

image 609.2 kB · 22 req
document 164.0 kB · 1 req
font 145.0 kB · 7 req
script 13.4 kB · 3 req
stylesheet 1.9 kB · 1 req
other 1.4 kB · 2 req
third party 657.7 kB · 27 req

Third parties 3 entities

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

figweb.site 600.6 kB · 0 ms CPU
Google Fonts 53.9 kB · 0 ms CPU
Fathom Analytics 3.2 kB · 4 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 2.02 s — — 2.02 s 2.02 s
Long Tasks 3 — — 3 3
DOM Elements 883 — — 883 883
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 43 — — 43 43
A11y Failures 2 — — 2 2
A11y Failing Nodes 9 — — 9 9

Main thread work

other 1.25 s
paint composite render 287 ms
style layout 270 ms
script evaluation 118 ms
parse HTML 59 ms
script parse compile 28 ms
garbage collection 12 ms

Axe violations axe-core 4.13.0, full rule set

43 violating nodes across 2 rules, 1205 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 35 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 8 nodes

Accessibility failures 2 of 24 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. 8 nodes
  • landmark-one-main — Document does not have a main landmark. 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 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, 9:30 PM UTC 73 5.39 s 0.003 22 ms 935.0 kB 3/3 ±2 2,309 30.2s

Embed this score

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