speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time — measured continuously.

Measurement runs · Embed a score ·

netlify.com

https://www.netlify.com/

51 97 77 92 1AXE CWV

Data from Aug 23, 2026, 2:21 PM UTC 7h old

Web Hosts #6 · 3 measurements · since Aug 21, 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.

Astro 5.18.2 Built with Astro 5.18.2
Netlify Hosted by Netlify

Core Web Vitals field data, url-level

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

LCP 2.10 s good
INP 298 ms needs-improvement
CLS 0 good

Scores

51
Performance
↓ -2 (-3.8%)
97
Accessibility
no change
77
Best Practices
no change
92
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

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 4.36 s 4.08 s ↑ +284 ms (+7%) significant 4.08 s 4.36 s
CLS Cumulative Layout Shift 0.001 0.029 ↓ -0.028 (-96.6%) 0.001 0.029
TBT Total Blocking Time 1.68 s 1.76 s ↓ -75 ms (-4.3%) 1.68 s 2.40 s
FCP First Contentful Paint 3.24 s 3.03 s ↑ +209 ms (+6.9%) 2.57 s 3.24 s
Speed Index 3.72 s 4.12 s ↓ -396 ms (-9.6%) 3.44 s 4.12 s
TTFB Time to First Byte 613 ms 629 ms ↓ -16 ms (-2.5%) 609 ms 629 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 4.36 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.

element render delay 181 ms
time to first byte 33 ms

Field data Chrome UX Report, url-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 2.10 s good 80.9% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 298 ms needs-improvement 58.6% good
CLS CWV 0 good 94.7% good
FCP 1.88 s needs-improvement 73.4% good
TTFB 794 ms good 75.2% good

Lab vs field

Lab LCP 4.36 s · field p75 2.10 s · real users are 0.48× 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.12 s 290 ms 0 1.89 s 808 ms
2026-08-08 2.13 s 283 ms 0 1.89 s 818 ms
2026-08-01 2.13 s 275 ms 0 1.88 s 823 ms
2026-07-25 2.11 s 274 ms 0 1.86 s 817 ms
2026-07-18 2.10 s 268 ms 0 1.85 s 816 ms
2026-07-11 2.09 s 268 ms 0 1.84 s 807 ms
2026-07-04 2.08 s 271 ms 0 1.85 s 800 ms
2026-06-27 2.07 s 273 ms 0 1.86 s 788 ms
2026-06-20 2.04 s 274 ms 0 1.87 s 774 ms
2026-06-13 2.04 s 274 ms 0 1.90 s 775 ms
2026-06-06 2.04 s 272 ms 0 1.91 s 775 ms
2026-05-30 2.04 s 271 ms 0 1.88 s 777 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 2.53 MB 2.56 MB ↓ -25.5 kB (-1%) 2.53 MB 2.56 MB
Requests 137 131 ↑ +6 (+4.6%) 131 137
Third-party Weight 1.57 MB 1.57 MB ↓ -774 B 1.57 MB 1.58 MB
Third-party CPU 765 ms 792 ms ↓ -28 ms (-3.5%) 765 ms 817 ms
Unused JS 900 kB 901 kB ↓ -1.3 kB (-0.1%) 900 kB 901 kB
Unused CSS 16.7 kB 16.7 kB ↑ +1 B 16.7 kB 16.7 kB

By resource type

script 1.70 MB · 49 req
font 215 kB · 7 req
image 207 kB · 27 req
document 171 kB · 4 req
other 150 kB · 36 req
stylesheet 88.5 kB · 10 req
third party 2.53 MB · 133 req

Third parties 11 entities

1.57 MB transferred, 765 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

Google Tag Manager 697 kB · 322 ms CPU
Google CDN 320 kB · 205 ms CPU
Hubspot 309 kB · 115 ms CPU
Optanon 191 kB · 98 ms CPU
Segment 47.7 kB · 22 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 8.31 s 9.36 s ↓ -1051 ms (-11.2%) significant 8.31 s 9.70 s
Long Tasks 20 20 → no change 20 20
DOM Elements 2,435 2,440 ↓ -5 (-0.2%) 2,435 2,440
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 1 1 → no change 1 1
A11y Failures 2 2 → no change 2 2
A11y Failing Nodes 3 3 → no change 3 3

Main thread work

script evaluation 4.63 s
other 1.39 s
style layout 953 ms
script parse compile 719 ms
paint composite render 307 ms
parse HTML 155 ms
garbage collection 153 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 1879 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.

  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 1 node

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

  • label-content-name-mismatch — Elements with visible text labels do not have matching accessible names. 2 nodes
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 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 23, 2026, 2:21 PM UTC 51 4.36 s 0.001 1.68 s 2.53 MB 3/3 ±17 2,451 53.5s
Aug 22, 2026, 2:19 PM UTC 53 4.08 s 0.029 1.76 s 2.56 MB 3/3 ±20 2,299 53.6s
Aug 21, 2026, 1:46 PM UTC 53 4.11 s 0.002 2.40 s 2.55 MB 3/3 ±9 2,498 50.1s

Embed this score

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