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 ·

docusaurus.io

https://docusaurus.io/

74 98 100 100 ✗CWV 3AXE

Data from Aug 20, 2026, 8:31 PM UTC — 22h old.

Site Generators · 1 measurement · since Aug 20, 2026 · last attempt 22h

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.

Docusaurus 3.10.1 Built with Docusaurus 3.10.1
Netlify Hosted by Netlify

Core Web Vitals field data, url-level

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

LCP 1.51 s good
INP 233 ms needs-improvement
CLS 0 good

Scores

74
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 4.72 s — — 4.72 s 4.72 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 361 ms — — 361 ms 361 ms
FCP First Contentful Paint 1.61 s — — 1.61 s 1.61 s
Speed Index 1.85 s — — 1.85 s 1.85 s
TTFB Time to First Byte 504 ms — — 504 ms 504 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 251 ms
time to first byte 87 ms

Field data Chrome UX Report, url-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.51 s good 90.6% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 233 ms needs-improvement 68.4% good
CLS CWV 0 good 96.8% good
FCP 1.50 s good 82.1% good
TTFB 752 ms good 77.4% good

Lab vs field

Lab LCP 4.72 s · field p75 1.51 s · real users are 0.32× 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.48 s 233 ms 0 1.47 s 743 ms
2026-08-08 1.46 s 234 ms 0 1.45 s 698 ms
2026-08-01 1.44 s 222 ms 0 1.43 s 707 ms
2026-07-25 1.40 s 224 ms 0 1.40 s 688 ms
2026-07-18 1.35 s 222 ms 0 1.35 s 667 ms
2026-07-11 1.33 s 218 ms 0 1.33 s 681 ms
2026-07-04 1.40 s 218 ms 0 1.40 s 698 ms
2026-06-27 1.44 s 210 ms 0 1.44 s 705 ms
2026-06-20 1.40 s 208 ms 0 1.40 s 691 ms
2026-06-13 1.45 s 219 ms 0 1.48 s 740 ms
2026-06-06 1.44 s 235 ms 0 1.44 s 740 ms
2026-05-30 1.41 s 240 ms 0 1.42 s 743 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 773.0 kB — — 773.0 kB 773.0 kB
Requests 50 — — 50 50
Third-party Weight 266.9 kB — — 266.9 kB 266.9 kB
Third-party CPU 68 ms — — 68 ms 68 ms
Unused JS 115.3 kB — — 115.3 kB 115.3 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

script 476.7 kB · 7 req
image 153.8 kB · 14 req
other 91.1 kB · 19 req
stylesheet 37.1 kB · 2 req
document 14.2 kB · 2 req
third party 273.1 kB · 8 req

Third parties 4 entities

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

Google Tag Manager 170.3 kB · 68 ms CPU
YouTube 64.6 kB · 0 ms CPU
unavatar.io 32.0 kB · 0 ms CPU
Google Analytics 48 B · 0 ms CPU

Page health

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

Main thread work

script evaluation 930 ms
other 503 ms
style layout 246 ms
script parse compile 237 ms
paint composite render 100 ms
parse HTML 47 ms
garbage collection 30 ms

Axe violations axe-core 4.13.0, full rule set

3 violating nodes across 3 rules, 664 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.

  • minor aria-allowed-role — ARIA role should be appropriate for the element 1 node
  • moderate heading-order — Heading levels should only increase by one 1 node
  • serious nested-interactive — Interactive controls must not be nested 1 node

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

Hygiene

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

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h3

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, 8:31 PM UTC 74 4.72 s 0 361 ms 773.0 kB 3/3 ±19 2,485 33.6s

Embed this score

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