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 ·

vercel.com

https://vercel.com/

63 95 92 100 CWV 1AXE

Data from Aug 21, 2026, 5:10 PM UTC — 1h old.

Web Hosts · 1 measurement · since Aug 21, 2026 · last attempt 1h

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

LCP 2.06 s good
INP 229 ms needs-improvement
CLS 0 good

Scores

63
Performance
no change
95
Accessibility
no change
92
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 4.07 s 4.07 s 4.07 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 834 ms 834 ms 834 ms
FCP First Contentful Paint 1.82 s 1.82 s 1.82 s
Speed Index 5.01 s 5.01 s 5.01 s
TTFB Time to First Byte 621 ms 621 ms 621 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 588 ms
time to first byte 4 ms

Field data Chrome UX Report, url-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 2.06 s good 81.2% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 229 ms needs-improvement 70.4% good
CLS CWV 0 good 97.9% good
FCP 1.86 s needs-improvement 73.6% good
TTFB 949 ms needs-improvement 69.3% good

Lab vs field

Lab LCP 4.07 s · field p75 2.06 s · real users are 0.51× 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 2.08 s 231 ms 0 1.87 s 930 ms
2026-08-08 2.07 s 229 ms 0 1.86 s 924 ms
2026-08-01 2.05 s 229 ms 0 1.85 s 910 ms
2026-07-25 2.02 s 225 ms 0 1.82 s 892 ms
2026-07-18 2.02 s 217 ms 0 1.82 s 894 ms
2026-07-11 2.08 s 203 ms 0 1.85 s 901 ms
2026-07-04 2.21 s 179 ms 0 1.90 s 909 ms
2026-06-27 2.31 s 162 ms 0 1.93 s 916 ms
2026-06-20 2.42 s 147 ms 0 1.98 s 915 ms
2026-06-13 2.49 s 140 ms 0 2.00 s 919 ms
2026-06-06 2.45 s 136 ms 0 1.97 s 906 ms
2026-05-30 2.42 s 133 ms 0 1.97 s 890 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 2.07 MB 2.07 MB 2.07 MB
Requests 124 124 124
Third-party Weight 57.4 kB 57.4 kB 57.4 kB
Third-party CPU 0 ms 0 ms 0 ms
Unused JS 360.8 kB 360.8 kB 360.8 kB
Unused CSS 20.2 kB 20.2 kB 20.2 kB

By resource type

script 1.24 MB · 74 req
other 318.6 kB · 28 req
font 227.8 kB · 7 req
stylesheet 150.8 kB · 5 req
image 72.7 kB · 8 req
document 56.6 kB · 1 req
third party 57.4 kB · 5 req

Third parties 2 entities

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

vercel-storage.com 57.1 kB · 0 ms CPU
Sentry 269 B · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 6.67 s 6.67 s 6.67 s
Long Tasks 13 13 13
DOM Elements 972 972 972
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 1 1 1

Main thread work

script evaluation 2.68 s
style layout 2.03 s
other 1.22 s
script parse compile 488 ms
parse HTML 123 ms
paint composite render 118 ms
garbage collection 14 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 1026 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 meta-viewport — Zooming and scaling must not be disabled 1 node

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

  • meta-viewport — `[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5. 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 3 console errors

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 21, 2026, 5:10 PM UTC 63 4.07 s 0 834 ms 2.07 MB 3/3 ±29 2,490 90.7s

Embed this score

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