speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time — measured continuously.

Measurement runs · Embed a score ·

mochajs.org

https://mochajs.org/

100 100 100 91 1AXE ✓CWV

Data from Aug 23, 2026, 5:28 AM UTC 16h old

Test Runners #2 · 3 measurements · since Aug 21, 2026

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.

Astro 7.1.1 Built with Astro 7.1.1
Netlify Hosted by Netlify

Core Web Vitals field data, url-level

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

LCP 1.38 s good
INP — no data
CLS 0 good

Scores

100
Performance
no change
100
Accessibility
no change
100
Best Practices
no change
91
SEO
no change

Filmstrip Lighthouse, mobile

How the page drew during the measured load, at 8 points across 3.00 s.

  1. 375 ms
  2. 750 ms
  3. 1.13 s
  4. 1.50 s
  5. 1.88 s
  6. 2.25 s
  7. 2.63 s
  8. 3.00 s

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.77 s 1.78 s ↓ -9 ms (-0.5%) 1.77 s 1.78 s
CLS Cumulative Layout Shift 0 0 → no change 0 0
TBT Total Blocking Time 0 ms 1 ms ↓ -1 ms (-100%) 0 ms 1 ms
FCP First Contentful Paint 906 ms 908 ms ↓ -2 ms (-0.2%) 906 ms 912 ms
Speed Index 906 ms 908 ms ↓ -2 ms (-0.2%) 906 ms 912 ms
TTFB Time to First Byte 605 ms 608 ms ↓ -3 ms (-0.5%) 604 ms 608 ms

What LCP is made of observed, unthrottled

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 1.77 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

element render delay 98 ms
time to first byte 6 ms

Field data Chrome UX Report, url-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.38 s good 92.8% good
CLS CWV 0 good 98.5% good
FCP 1.30 s good 84.7% good
TTFB 1.09 s needs-improvement 69.7% good

Lab vs field

Lab LCP 1.77 s · field p75 1.38 s · real users are 0.78× 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 1.40 s — 0 1.30 s 1.05 s
2026-08-08 1.23 s — 0 1.23 s 988 ms
2026-08-01 1.14 s — 0 1.10 s 985 ms
2026-07-25 1.14 s — 0 1.12 s 840 ms
2026-07-18 1.14 s — 0 1.13 s 733 ms
2026-07-11 1.31 s — 0 1.26 s 746 ms
2026-07-04 1.37 s — 0 1.29 s 800 ms
2026-06-27 1.38 s — 0 1.33 s 746 ms
2026-06-20 990 ms — 0 868 ms 940 ms
2026-06-13 888 ms — 0 763 ms 804 ms
2026-06-06 834 ms — 0 736 ms 677 ms
2026-05-30 886 ms — 0 786 ms 784 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 334 kB 333 kB ↑ +390 B (+0.1%) 333 kB 334 kB
Requests 111 111 → no change 111 111
Third-party Weight 273 kB 273 kB ↑ +52 B 273 kB 274 kB
Third-party CPU 11 ms 13 ms ↓ -2 ms (-12.3%) significant 11 ms 13 ms
Unused JS 30.2 kB 30.2 kB ↓ -31 B (-0.1%) 29.3 kB 30.2 kB
Unused CSS 0 B 0 B → no change 0 B 0 B

By resource type

image 236 kB · 97 req
script 71.6 kB · 8 req
stylesheet 12.8 kB · 2 req
document 12.3 kB · 1 req
other 1.3 kB · 3 req
third party 274 kB · 95 req

Third parties 4 entities

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

opencollective.com 225 kB · 0 ms CPU
Matomo 45.1 kB · 11 ms CPU
Netlify 1.7 kB · 0 ms CPU
shields.io 1.2 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 912 ms 976 ms ↓ -64 ms (-6.5%) 912 ms 976 ms
Long Tasks 2 2 → no change 2 3
DOM Elements 682 682 → no change 682 682
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 1 1 → no change 1 1
A11y Failures 0 0 → no change 0 0
A11y Failing Nodes 0 0 → no change 0 0

Main thread work

other 517 ms
script evaluation 149 ms
style layout 126 ms
paint composite render 61 ms
parse HTML 39 ms
script parse compile 20 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 1087 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 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 23, 2026, 5:28 AM UTC 100 1.77 s 0 0 ms 334 kB 3/3 ±1 2,496 33s
Aug 22, 2026, 5:26 AM UTC 100 1.78 s 0 1 ms 333 kB 3/3 ±10 2,333 36.3s
Aug 21, 2026, 4:45 AM UTC 100 1.78 s 0 0 ms 334 kB 3/3 ±0 2,467 31.8s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show mochajs.org's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify2-score.js component code into your site! 

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://mochajs.org/"></speedlify2-score>