speedlify2

Lighthouse lab metrics, Axe, and Chrome UX Report field data for a list of sites recorded and compared over time.

Measurement runs Embed a score

esbuild.github.io

https://esbuild.github.io/

100 95 100 70 !AXE ✓CWV

Data from Aug 27, 2026, 6:58 PM UTC old

Overall #907 Developer Tooling #23 · 1 measurement · since Aug 27, 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.

GitHub Pages Hosted by GitHub Pages

Core Web Vitals field data, url-level

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

LCP 733 ms good
INP 80 ms good
CLS 0 good

Scores

100
Performance
no change
95
Accessibility
no change
100
Best Practices
no change
70
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

Without JavaScript

The same load, photographed twice at 412×823: once with scripts disabled, once as rendered.

Scripts disabled
As rendered

18.1% of pixels differ — parts of the page change. A shifted layout counts as difference, so a <noscript> banner alone can account for a large figure.

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 806 ms — — 806 ms 806 ms
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 806 ms — — 806 ms 806 ms
Speed Index 806 ms — — 806 ms 806 ms
TTFB Time to First Byte 619 ms — — 619 ms 619 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 806 ms 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 36 ms
time to first byte 20 ms

Field data Chrome UX Report, url-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 733 ms good 95.9% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 80 ms good 95.9% good
CLS CWV 0 good 100% good
FCP 722 ms good 93.3% good
TTFB 511 ms good 88.9% good

Lab vs field LCP

Lab 806 ms
Field p75 733 ms

The lab LCP is 1.1× the field p75 — real users likely have similar hardware or network connectivity to the lab test.

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-22 733 ms 80 ms 0 722 ms 551 ms
2026-08-15 801 ms 88 ms 0 784 ms 593 ms
2026-08-08 862 ms 97 ms 0 821 ms 605 ms
2026-08-01 862 ms 112 ms 0 846 ms 642 ms
2026-07-25 883 ms 114 ms 0 875 ms 638 ms
2026-07-18 783 ms 115 ms 0 777 ms 642 ms
2026-07-11 853 ms 105 ms 0 826 ms 642 ms
2026-07-04 761 ms 95 ms 0 762 ms 601 ms
2026-06-27 721 ms 93 ms 0 741 ms 601 ms
2026-06-20 758 ms 85 ms 0 760 ms 601 ms
2026-06-13 680 ms 85 ms 0 679 ms 533 ms
2026-06-06 662 ms 84 ms 0 659 ms 531 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 7.7 kB — — 7.7 kB 7.7 kB
Requests 3 — — 3 3
Third-party Weight 0 B — — 0 B 0 B
Third-party CPU 0 ms — — 0 ms 0 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

document 7.2 kB · 1 req
image 444 B · 1 req
third party 7.7 kB · 3 req

Page health

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

Main thread work

other 228 ms
style layout 142 ms
paint composite render 122 ms
script evaluation 22 ms
parse HTML 9 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 472 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

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

  • target-size — Touch targets do not have sufficient size or spacing. 2 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 27, 2026, 6:58 PM UTC 100 806 ms 0 0 ms 7.7 kB 3/3 ±3 2,452 22.5s

Embed this score

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