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

webpack.js.org

https://webpack.js.org/

77 89 100 100 ✗AXE ✗CWV

Data from Aug 27, 2026, 7:01 PM UTC old

Overall #1,458 Developer Tooling #69 · 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.

Vercel Hosted by Vercel

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 2.12 s good
INP 340 ms needs-improvement
CLS 0.020 good

Scores

77
Performance
no change
89
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

Without JavaScript

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

Scripts disabled
As rendered

1% of pixels differ — they are nearly identical. 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 3.54 s — — 3.54 s 3.54 s
CLS Cumulative Layout Shift 0.002 — — 0.002 0.002
TBT Total Blocking Time 373 ms — — 373 ms 373 ms
FCP First Contentful Paint 2.92 s — — 2.92 s 2.92 s
Speed Index 2.92 s — — 2.92 s 2.92 s
TTFB Time to First Byte 608 ms — — 608 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 3.54 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 141 ms
time to first byte 4 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 2.12 s good 80.8% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 340 ms needs-improvement 61.9% good
CLS CWV 0.020 good 83.7% good
FCP 2.17 s needs-improvement 66.2% good
TTFB 691 ms good 78.7% good

Lab vs field LCP

Lab 3.54 s
Field p75 2.12 s

The lab LCP is 1.67× the field p75 — real users likely have above-average hardware or network connectivity.

Field history 25 weeks

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

Week ending LCPINPCLSFCPTTFB
2026-08-22 2.07 s 330 ms 0.010 2.15 s 682 ms
2026-08-15 2.06 s 330 ms 0 2.10 s 684 ms
2026-08-08 2.15 s 353 ms 0 2.16 s 764 ms
2026-08-01 2.06 s 269 ms 0 2.06 s 807 ms
2026-07-25 2.05 s 272 ms 0 2.06 s 903 ms
2026-07-18 2.13 s 278 ms 0 2.14 s 943 ms
2026-07-11 2.10 s 283 ms 0 2.13 s 919 ms
2026-07-04 2.10 s 283 ms 0 2.12 s 887 ms
2026-06-27 2.13 s 258 ms 0.020 2.15 s 845 ms
2026-06-20 2.04 s 254 ms 0 2.06 s 804 ms
2026-06-13 1.90 s 257 ms 0 1.92 s 766 ms
2026-06-06 1.90 s 257 ms 0 1.93 s 777 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 793 kB — — 793 kB 793 kB
Requests 23 — — 23 23
Third-party Weight 248 kB — — 248 kB 248 kB
Third-party CPU 61 ms — — 61 ms 61 ms
Unused JS 199 kB — — 199 kB 199 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

script 591 kB · 5 req
image 77.9 kB · 7 req
font 73.4 kB · 4 req
stylesheet 22.2 kB · 3 req
other 17.8 kB · 3 req
document 10.6 kB · 1 req
third party 248 kB · 6 req

Third parties 2 entities

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

Google Tag Manager 174 kB · 61 ms CPU
Google Fonts 74.6 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.83 s — — 1.83 s 1.83 s
Long Tasks 10 — — 10 10
DOM Elements 2,625 — — 2,625 2,625
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 23 — — 23 23
A11y Failures 3 — — 3 3
A11y Failing Nodes 5 — — 5 5

Main thread work

script evaluation 922 ms
other 289 ms
style layout 272 ms
script parse compile 231 ms
paint composite render 61 ms
parse HTML 33 ms
garbage collection 23 ms

Axe violations axe-core 4.13.0, full rule set

23 violating nodes across 4 rules, 2796 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 18 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 3 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • serious scrollable-region-focusable — Scrollable region must have keyboard access 1 node

Accessibility failures 3 of 21 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.

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 3 nodes
  • target-size — Touch targets do not have sufficient size or spacing. 1 node
  • landmark-one-main — Document does not have a main landmark. 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 27, 2026, 7:01 PM UTC 77 3.54 s 0.002 373 ms 793 kB 3/3 ±10 2,465 57.1s

Embed this score

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