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 ·

eslint.org

https://eslint.org/

72 97 100 100 ✓CWV 4AXE

Data from Aug 20, 2026, 9:31 PM UTC — 21h old.

Test Runners, 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.

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.48 s good
INP 104 ms good
CLS 0.010 good

Scores

72
Performance
no change
97
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.16 s — — 4.16 s 4.16 s
CLS Cumulative Layout Shift 0.273 — — 0.273 0.273
TBT Total Blocking Time 38 ms — — 38 ms 38 ms
FCP First Contentful Paint 1.53 s — — 1.53 s 1.53 s
Speed Index 2.03 s — — 2.03 s 2.03 s
TTFB Time to First Byte 634 ms — — 634 ms 634 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 201 ms
time to first byte 36 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.48 s good 90.3% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 104 ms good 91.7% good
CLS CWV 0.010 good 81.3% good
FCP 1.47 s good 87.5% good
TTFB 638 ms good 85.6% good

Lab vs field

Lab LCP 4.16 s · field p75 1.48 s · real users are 0.36× 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.49 s 99 ms 0.010 1.48 s 638 ms
2026-08-08 1.48 s 92 ms 0.010 1.43 s 637 ms
2026-08-01 1.60 s 94 ms 0.160 1.56 s 692 ms
2026-07-25 1.65 s 92 ms 0.130 1.59 s 721 ms
2026-07-18 1.91 s 96 ms 0.190 1.65 s 730 ms
2026-07-11 1.91 s 103 ms 0.220 1.74 s 780 ms
2026-07-04 1.78 s 96 ms 0.020 1.65 s 730 ms
2026-06-27 1.89 s 100 ms 0.010 1.71 s 797 ms
2026-06-20 1.77 s 95 ms 0 1.67 s 741 ms
2026-06-13 1.85 s 99 ms 0.020 1.70 s 727 ms
2026-06-06 1.80 s 105 ms 0.040 1.62 s 716 ms
2026-05-30 1.77 s 101 ms 0.120 1.58 s 701 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.11 MB — — 1.11 MB 1.11 MB
Requests 33 — — 33 33
Third-party Weight 566.8 kB — — 566.8 kB 566.8 kB
Third-party CPU 70 ms — — 70 ms 70 ms
Unused JS 69.9 kB — — 69.9 kB 69.9 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

font 522.9 kB · 6 req
image 325.2 kB · 10 req
script 228.0 kB · 10 req
document 18.1 kB · 1 req
stylesheet 16.0 kB · 1 req
other 970 B · 2 req
third party 566.8 kB · 9 req

Third parties 5 entities

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

GitHub 273.2 kB · 0 ms CPU
Google Tag Manager 167.9 kB · 46 ms CPU
JSDelivr CDN 78.7 kB · 0 ms CPU
Cloudflare CDN 35.4 kB · 24 ms CPU
opencollective.com 11.6 kB · 0 ms CPU

Page health

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

Main thread work

other 334 ms
script evaluation 310 ms
style layout 265 ms
paint composite render 98 ms
script parse compile 56 ms
parse HTML 30 ms

Axe violations axe-core 4.13.0, full rule set

4 violating nodes across 2 rules, 1237 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 aria-prohibited-attr — Elements must only use permitted ARIA attributes 3 nodes
  • moderate region — All page content should be contained by landmarks 1 node

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

  • aria-prohibited-attr — Elements use prohibited ARIA attributes 3 nodes

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, 9:31 PM UTC 72 4.16 s 0.273 38 ms 1.11 MB 3/3 ±19 3,238 26.2s

Embed this score

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