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 ·

eslint.org

https://eslint.org/

74 97 100 100 4AXE CWV

Data from Aug 22, 2026, 11:19 PM UTC 22h old

Test Runners #3 Built Awesome #704 · 3 measurements · since Aug 20, 2026

The measuring machine was slower than usual.

Lighthouse benchmark index was 2446.5 against a baseline of 3092.8 (-20.9%). CPU-bound metrics — TBT, TTI, main thread work — are affected by this and may have moved without the site changing at all.

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-24 → 2026-08-20). This is what Google measures you on.

LCP 1.48 s good
INP 104 ms good
CLS 0.010 good

Scores

74
Performance
↑ +4 (+5.7%)
97
Accessibility
no change
100
Best Practices
no change
100
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 5.93 s 7.21 s ↓ -1281 ms (-17.8%) 4.16 s 7.21 s
CLS Cumulative Layout Shift 0.011 0 ↑ +0.011 0 0.273
TBT Total Blocking Time 148 ms 139 ms ↑ +9 ms (+6.5%) 38 ms 148 ms
FCP First Contentful Paint 2.41 s 2.66 s ↓ -249 ms (-9.4%) 1.53 s 2.66 s
Speed Index 2.41 s 3.38 s ↓ -973 ms (-28.8%) 2.03 s 3.38 s
TTFB Time to First Byte 604 ms 619 ms ↓ -15 ms (-2.4%) 604 ms 634 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 5.93 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 136 ms
time to first byte 4 ms

Field data Chrome UX Report, url-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.48 s good 90.7% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 104 ms good 91% good
CLS CWV 0.010 good 81.9% good
FCP 1.43 s good 86.9% good
TTFB 629 ms good 86.8% good

Lab vs field

Lab LCP 5.93 s · field p75 1.48 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 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.14 MB 1.14 MB ↓ -1.5 kB (-0.1%) 1.11 MB 1.14 MB
Requests 33 34 ↓ -1 (-2.9%) 33 34
Third-party Weight 599 kB 600 kB ↓ -1.4 kB (-0.2%) 567 kB 600 kB
Third-party CPU 80 ms 72 ms ↑ +8 ms (+10.9%) significant 70 ms 80 ms
Unused JS 69.9 kB 68.9 kB ↑ +999 B (+1.5%) 68.9 kB 69.9 kB
Unused CSS 0 B 0 B → no change 0 B 0 B

By resource type

font 523 kB · 6 req
image 350 kB · 10 req
script 228 kB · 10 req
document 18.1 kB · 1 req
stylesheet 15.9 kB · 1 req
other 977 B · 2 req
third party 599 kB · 10 req

Third parties 5 entities

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

GitHub 305 kB · 0 ms CPU
Google Tag Manager 168 kB · 58 ms CPU
JSDelivr CDN 78.7 kB · 0 ms CPU
Cloudflare CDN 35.4 kB · 22 ms CPU
opencollective.com 11.6 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.22 s 1.18 s ↑ +38 ms (+3.2%) 1.09 s 1.22 s
Long Tasks 4 5 ↓ -1 (-20%) 2 5
DOM Elements 578 578 → no change 578 578
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 4 4 → no change 4 4
A11y Failures 1 1 → no change 1 1
A11y Failing Nodes 3 3 → no change 3 3

Main thread work

other 368 ms
script evaluation 361 ms
style layout 286 ms
paint composite render 95 ms
script parse compile 74 ms
parse HTML 35 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 22, 2026, 11:19 PM UTC 74 5.93 s 0.011 148 ms 1.14 MB 3/3 ±12 2,447 28.7s
Aug 21, 2026, 10:23 PM UTC 70 7.21 s 0 139 ms 1.14 MB 3/3 ±3 2,948 26.1s
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 speedlify2-score.js component code into your site!

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