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

alpinejs.dev

https://alpinejs.dev/

92 93 100 100 ✗AXE ✓CWV

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

Overall #1,106 Developer Tooling #32 Frameworks and Libraries #7 · 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.

Cloudflare Hosted by Cloudflare

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 1.71 s good
INP 62 ms good
CLS 0 good

Scores

92
Performance
no change
93
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

0.8% 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 2.89 s — — 2.89 s 2.89 s
CLS Cumulative Layout Shift 0.001 — — 0.001 0.001
TBT Total Blocking Time 4 ms — — 4 ms 4 ms
FCP First Contentful Paint 2.49 s — — 2.49 s 2.49 s
Speed Index 2.49 s — — 2.49 s 2.49 s
TTFB Time to First Byte 478 ms — — 478 ms 478 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 2.89 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.

time to first byte 117 ms
element render delay 55 ms
resource load duration 35 ms
resource load delay 11 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 1.71 s good 88.2% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 62 ms good 97.3% good
CLS CWV 0 good 99.9% good
FCP 1.69 s good 77.5% good
TTFB 960 ms needs-improvement 66.4% good

Lab vs field LCP

Lab 2.89 s
Field p75 1.71 s

The lab LCP is 1.69× 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 1.69 s 62 ms 0 1.68 s 948 ms
2026-08-15 1.64 s 63 ms 0 1.63 s 925 ms
2026-08-08 1.65 s 63 ms 0 1.64 s 903 ms
2026-08-01 1.66 s 65 ms 0 1.65 s 908 ms
2026-07-25 1.69 s 68 ms 0 1.68 s 912 ms
2026-07-18 1.73 s 69 ms 0 1.72 s 935 ms
2026-07-11 1.75 s 69 ms 0 1.74 s 948 ms
2026-07-04 1.73 s 69 ms 0 1.74 s 939 ms
2026-06-27 1.70 s 66 ms 0 1.73 s 937 ms
2026-06-20 1.69 s 68 ms 0 1.73 s 908 ms
2026-06-13 1.59 s 68 ms 0 1.61 s 837 ms
2026-06-06 1.50 s 69 ms 0 1.50 s 795 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 219 kB — — 219 kB 219 kB
Requests 25 — — 25 25
Third-party Weight 147 kB — — 147 kB 147 kB
Third-party CPU 31 ms — — 31 ms 31 ms
Unused JS 61.4 kB — — 61.4 kB 61.4 kB
Unused CSS 11.9 kB — — 11.9 kB 11.9 kB

By resource type

script 161 kB · 15 req
font 24.3 kB · 1 req
stylesheet 17.6 kB · 3 req
document 7.9 kB · 1 req
image 6.6 kB · 3 req
other 1.6 kB · 2 req
third party 147 kB · 18 req

Third parties 4 entities

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

JSDelivr CDN 108 kB · 26 ms CPU
Google Fonts 24.8 kB · 0 ms CPU
Cloudflare 11.5 kB · 4 ms CPU
Fathom Analytics 3.2 kB · 2 ms CPU

Page health

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

Main thread work

other 150 ms
script evaluation 144 ms
style layout 64 ms
script parse compile 55 ms
parse HTML 21 ms
paint composite render 20 ms

Axe violations axe-core 4.13.0, full rule set

53 violating nodes across 5 rules, 305 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 35 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 15 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • moderate page-has-heading-one — Page should contain a level-one heading 1 node
  • serious scrollable-region-focusable — Scrollable region must have keyboard access 1 node

Accessibility failures 2 of 19 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. 15 nodes
  • 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 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 27, 2026, 6:58 PM UTC 92 2.89 s 0.001 4 ms 219 kB 3/3 ±9 2,497 32.4s

Embed this score

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