v8.dev
Data from Aug 21, 2026, 10:29 AM UTC — 8h old.
Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 8h
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.
Scores
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 769 ms | — | — | 769 ms | 769 ms | |
| CLS Cumulative Layout Shift | 0 | — | — | 0 | 0 | |
| TBT Total Blocking Time | 0 ms | — | — | 0 ms | 0 ms | |
| FCP First Contentful Paint | 769 ms | — | — | 769 ms | 769 ms | |
| Speed Index | 769 ms | — | — | 769 ms | 769 ms | |
| TTFB Time to First Byte | 602 ms | — | — | 602 ms | 602 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.
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 | 962 ms | good | 94.9% good |
| INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run | 80 ms | good | 94.8% good |
| CLS CWV | 0 | good | 95.7% good |
| FCP | 973 ms | good | 91% good |
| TTFB | 645 ms | good | 79.5% good |
Lab vs field
Lab LCP 769 ms · field p75 962 ms · real users are 1.25× slower 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 | 970 ms | 82 ms | 0 | 977 ms | 648 ms |
| 2026-08-08 | 937 ms | 82 ms | 0 | 936 ms | 630 ms |
| 2026-08-01 | 893 ms | 87 ms | 0 | 898 ms | 572 ms |
| 2026-07-25 | 893 ms | 84 ms | 0 | 896 ms | 573 ms |
| 2026-07-18 | 887 ms | 84 ms | 0 | 896 ms | 582 ms |
| 2026-07-11 | 859 ms | 84 ms | 0 | 880 ms | 558 ms |
| 2026-07-04 | 872 ms | 79 ms | 0 | 900 ms | 603 ms |
| 2026-06-27 | 861 ms | 77 ms | 0 | 871 ms | 585 ms |
| 2026-06-20 | 851 ms | 74 ms | 0 | 866 ms | 570 ms |
| 2026-06-13 | 862 ms | 70 ms | 0 | 866 ms | 614 ms |
| 2026-06-06 | 841 ms | 73 ms | 0 | 848 ms | 612 ms |
| 2026-05-30 | 850 ms | 73 ms | 0 | 870 ms | 567 ms |
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 17.3 kB | — | — | 17.3 kB | 17.3 kB | |
| Requests | 9 | — | — | 9 | 9 | |
| 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
Page health
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Main Thread Work | 175 ms | — | — | 175 ms | 175 ms | |
| Long Tasks | 0 | — | — | 0 | 0 | |
| DOM Elements | 103 | — | — | 103 | 103 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 1 | — | — | 1 | 1 | |
| A11y Failures | 0 | — | — | 0 | 0 | |
| A11y Failing Nodes | 0 | — | — | 0 | 0 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
1 violating node across 1 rule, 215 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.
-
minor
empty-heading— Headings should not be empty 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 21, 2026, 10:29 AM UTC | 100 | 769 ms | 0 | 0 ms | 17.3 kB | 3/3 | ±0 | 2,471 | 20.1s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
v8.dev'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://v8.dev/"></speedlify-score>