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 ·

astro.build

https://astro.build/

82 100 100 100 0AXE ✓CWV

Data from Aug 23, 2026, 6:30 PM UTC 3h old

Site Generators #7 · 4 measurements · since Aug 20, 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 7.2.3 Built with Astro 7.2.3
Cloudflare Hosted by Cloudflare

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 1.17 s good
INP 115 ms good
CLS 0 good

Scores

82
Performance
no change
100
Accessibility
no change
100
Best Practices
no change
100
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.80 s 4.76 s ↑ +44 ms (+0.9%) 2.48 s 4.80 s
CLS Cumulative Layout Shift 0 0 → no change 0 0
TBT Total Blocking Time 0 ms 0 ms → no change 0 ms 0 ms
FCP First Contentful Paint 1.47 s 1.41 s ↑ +56 ms (+4%) 1.41 s 1.47 s
Speed Index 1.47 s 1.41 s ↑ +56 ms (+4%) 1.41 s 1.47 s
TTFB Time to First Byte 677 ms 633 ms ↑ +44 ms (+7%) significant 631 ms 677 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.80 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 220 ms
time to first byte 68 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 1.17 s good 93.8% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 115 ms good 92.6% good
CLS CWV 0 good 96.4% good
FCP 1.18 s good 88.4% good
TTFB 521 ms good 86.1% good

Lab vs field

Lab LCP 4.80 s · field p75 1.17 s · real users are 0.24× 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 1.17 s 113 ms 0 1.18 s 522 ms
2026-08-08 1.16 s 113 ms 0 1.16 s 526 ms
2026-08-01 1.20 s 112 ms 0 1.20 s 537 ms
2026-07-25 1.25 s 112 ms 0 1.24 s 583 ms
2026-07-18 1.17 s 108 ms 0 1.17 s 534 ms
2026-07-11 1.21 s 109 ms 0 1.20 s 556 ms
2026-07-04 1.23 s 109 ms 0 1.22 s 566 ms
2026-06-27 1.16 s 109 ms 0 1.16 s 528 ms
2026-06-20 1.21 s 111 ms 0 1.21 s 570 ms
2026-06-13 1.22 s 112 ms 0 1.21 s 577 ms
2026-06-06 1.22 s 112 ms 0 1.22 s 576 ms
2026-05-30 1.25 s 112 ms 0 1.25 s 586 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 738 kB 738 kB ↑ +9 B 346 kB 738 kB
Requests 25 25 → no change 24 25
Third-party Weight 3.2 kB 3.2 kB ↓ -1 B 3.2 kB 3.2 kB
Third-party CPU 2 ms 2 ms ↓ -1 ms (-23.8%) significant 2 ms 2 ms
Unused JS 0 B 0 B → no change 0 B 0 B
Unused CSS 0 B 0 B → no change 0 B 0 B

By resource type

image 429 kB · 9 req
font 196 kB · 3 req
document 82.3 kB · 1 req
stylesheet 21.1 kB · 2 req
script 9.0 kB · 8 req
other 699 B · 1 req
third party 3.2 kB · 2 req

Third parties 1 entities

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

Fathom Analytics 3.2 kB · 2 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 531 ms 453 ms ↑ +78 ms (+17.2%) 453 ms 676 ms
Long Tasks 1 1 → no change 1 2
DOM Elements 1,802 1,802 → no change 1,801 1,802
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 0 0 → no change 0 0
A11y Failures 0 0 → no change 0 0
A11y Failing Nodes 0 0 → no change 0 0

Main thread work

other 205 ms
style layout 187 ms
parse HTML 57 ms
script evaluation 42 ms
paint composite render 35 ms
script parse compile 4 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 1693 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.

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, 6:30 PM UTC 82 4.80 s 0 0 ms 738 kB 3/3 ±11 2,460 30s
Aug 22, 2026, 5:22 PM UTC 82 4.76 s 0 0 ms 738 kB 3/3 ±18 3,381 27.6s
Aug 21, 2026, 4:37 PM UTC 82 4.77 s 0 0 ms 738 kB 3/3 ±10 2,692 29.1s
Aug 20, 2026, 4:29 PM UTC 97 2.48 s 0 0 ms 346 kB 3/3 ±17 2,487 28.7s

Embed this score

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