vercel.com
Data from Aug 22, 2026, 5:19 PM UTC 28h old
Web Hosts #10 · 3 measurements · since Aug 21, 2026
PAGE_HUNG: Lighthouse was unable to reliably load the URL you requested because the page stopped responding.
Numbers below are from the last successful run, 28h old.
Lighthouse benchmark index was 1888.5 against a baseline of 2490 (-24.2%). 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.
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.
Scores
Filmstrip Lighthouse, mobile
How the page drew during the measured load, at 8 points across 9.01 s.
-
1.13 s
-
2.25 s
-
3.38 s
-
4.50 s
-
5.63 s
-
6.76 s
-
7.88 s
-
9.01 s
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 6.67 s | 4.07 s | ↑ +2596 ms (+63.8%) | 4.07 s | 6.67 s | |
| CLS Cumulative Layout Shift | 0 | 0 | → no change | 0 | 0 | |
| TBT Total Blocking Time | 87.00 s | 834 ms | ↑ +86170 ms (+10332.1%) | 834 ms | 87.00 s | |
| FCP First Contentful Paint | 2.33 s | 1.82 s | ↑ +514 ms (+28.2%) | 1.82 s | 2.33 s | |
| Speed Index | 19.21 s | 5.01 s | ↑ +14191 ms (+283%) | 5.01 s | 19.21 s | |
| TTFB Time to First Byte | 628 ms | 621 ms | ↑ +7 ms (+1.1%) | 621 ms | 628 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 6.67 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.
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 | 2.06 s | good | 80.9% good |
| INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run | 229 ms | needs-improvement | 71% good |
| CLS CWV | 0 | good | 97.7% good |
| FCP | 1.86 s | needs-improvement | 73.4% good |
| TTFB | 949 ms | needs-improvement | 69.3% good |
Lab vs field
Lab LCP 6.67 s · field p75 2.06 s · real users are 0.31× faster than the lab.
Field history 25 weeks
Weekly p75 from the CrUX History API, backfilled in a single request.
| Week ending | LCP | INP | CLS | FCP | TTFB |
|---|---|---|---|---|---|
| 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.18 MB | 2.07 MB | ↑ +103.6 kB (+5.1%) | 2.07 MB | 2.18 MB | |
| Requests | 119 | 124 | ↓ -5 (-4%) | 119 | 124 | |
| Third-party Weight | 80.8 kB | 57.4 kB | ↑ +22.9 kB (+40.9%) | 57.4 kB | 80.8 kB | |
| Third-party CPU | 0 ms | 0 ms | → no change | 0 ms | 0 ms | |
| Unused JS | 541 kB | 361 kB | ↑ +176.4 kB (+50.1%) | 361 kB | 541 kB | |
| Unused CSS | 20.1 kB | 20.2 kB | ↓ -57 B (-0.3%) | 20.1 kB | 20.2 kB |
By resource type
Third parties 3 entities
80.8 kB transferred, 0 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.
Page health
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Main Thread Work | 178.46 s | 6.67 s | ↑ +171790 ms (+2575.2%) | 6.67 s | 178.46 s | |
| Long Tasks | 20 | 13 | ↑ +7 (+53.8%) | 13 | 20 | |
| DOM Elements | 970 | 972 | ↓ -2 (-0.2%) | 970 | 972 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 1 | 1 | → no change | 1 | 1 | |
| A11y Failures | 1 | 1 | → no change | 1 | 1 | |
| A11y Failing Nodes | 1 | 1 | → no change | 1 | 1 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
1 violating node across 1 rule, 1022 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.
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 | Perf | LCP | CLS | TBT | Weight | Runs | Spread | Bench | Took |
|---|---|---|---|---|---|---|---|---|---|
| Aug 23, 2026, 6:27 PM UTC | PAGE_HUNG: Lighthouse was unable to reliably load the URL you requested because the page stopped responding. |
152.7s | |||||||
| Aug 22, 2026, 5:19 PM UTC | 34 | 6.67 s | 0 | 87.00 s | 2.18 MB | 3/3 | ±19 | 1,889 | 269.6s |
| 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 speedlify2-score.js component code into your site!
<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://vercel.com/"></speedlify2-score>