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 ·

nuxt.com

https://nuxt.com/

44 96 100 100 CWV 2AXE

Data from Aug 21, 2026, 5:31 AM UTC — 13h old.

Site Generators · 1 measurement · since Aug 21, 2026 · last attempt 13h

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.

Nuxt Built with Nuxt
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.28 s good
INP 920 ms poor
CLS 0 good

Scores

44
Performance
no change
96
Accessibility
no change
100
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 5.24 s 5.24 s 5.24 s
CLS Cumulative Layout Shift 0.014 0.014 0.014
TBT Total Blocking Time 1.62 s 1.62 s 1.62 s
FCP First Contentful Paint 4.11 s 4.11 s 4.11 s
Speed Index 4.11 s 4.11 s 4.11 s
TTFB Time to First Byte 662 ms 662 ms 662 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 260 ms
time to first byte 21 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.28 s good 79.8% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 920 ms poor 41.8% good
CLS CWV 0 good 97.1% good
FCP 2.25 s needs-improvement 60.3% good
TTFB 1.39 s needs-improvement 47.9% good

Lab vs field

Lab LCP 5.24 s · field p75 2.28 s · real users are 0.44× 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.28 s 943 ms 0 2.25 s 1.38 s
2026-08-08 2.22 s 897 ms 0 2.19 s 1.36 s
2026-08-01 2.11 s 911 ms 0 2.09 s 1.28 s
2026-07-25 2.01 s 976 ms 0 2.00 s 1.21 s
2026-07-18 1.98 s 1.02 s 0 1.97 s 1.20 s
2026-07-11 1.98 s 1.01 s 0 1.97 s 1.21 s
2026-07-04 1.98 s 938 ms 0 1.97 s 1.21 s
2026-06-27 1.93 s 803 ms 0 1.92 s 1.15 s
2026-06-20 1.97 s 748 ms 0 1.96 s 1.13 s
2026-06-13 1.96 s 697 ms 0 1.96 s 1.11 s
2026-06-06 2.00 s 655 ms 0 2.00 s 1.12 s
2026-05-30 1.98 s 681 ms 0 1.98 s 1.12 s

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 3.26 MB 3.26 MB 3.26 MB
Requests 318 318 318
Third-party Weight 1.4 kB 1.4 kB 1.4 kB
Third-party CPU 0 ms 0 ms 0 ms
Unused JS 1.85 MB 1.85 MB 1.85 MB
Unused CSS 0 B 0 B 0 B

By resource type

other 2.38 MB · 48 req
script 662.8 kB · 183 req
image 109.3 kB · 43 req
document 43.0 kB · 1 req
stylesheet 38.8 kB · 4 req
font 26.9 kB · 1 req
third party 1.4 kB · 2 req

Third parties 2 entities

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

GitHub 1.0 kB · 0 ms CPU
Carbon Ads 356 B · 0 ms CPU

Page health

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

Main thread work

script evaluation 4.79 s
other 1.77 s
style layout 888 ms
garbage collection 384 ms
paint composite render 162 ms
parse HTML 84 ms
script parse compile 46 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 2 rules, 2557 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.

  • critical aria-valid-attr-value — ARIA attributes must conform to valid values 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

Accessibility failures 2 of 34 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.

  • aria-valid-attr-value — `[aria-*]` attributes do not have valid values 1 node
  • td-has-header — `<td>` elements in a large `<table>` do not have table headers. 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 21, 2026, 5:31 AM UTC 44 5.24 s 0.014 1.62 s 3.26 MB 3/3 ±10 3,529 65.4s

Embed this score

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