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 ·

gatsbyjs.com

https://www.gatsbyjs.com/

86 100 96 92 3AXE CWV

Data from Aug 23, 2026, 1:31 PM UTC 9h old

Site Generators #9 · 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.

Gatsby 4.24.6 Built with Gatsby 4.24.6
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 1.99 s good
INP 101 ms good
CLS 0 good

Scores

86
Performance
↑ +2 (+2.4%)
100
Accessibility
no change
96
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 3.86 s 4.02 s ↓ -166 ms (-4.1%) 3.86 s 4.02 s
CLS Cumulative Layout Shift 0 0 → no change 0 0
TBT Total Blocking Time 155 ms 205 ms ↓ -50 ms (-24.4%) 154 ms 205 ms
FCP First Contentful Paint 953 ms 936 ms ↑ +17 ms (+1.8%) 936 ms 964 ms
Speed Index 953 ms 936 ms ↑ +17 ms (+1.8%) 936 ms 964 ms
TTFB Time to First Byte 620 ms 606 ms ↑ +14 ms (+2.3%) 606 ms 632 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 3.86 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 245 ms
resource load delay 76 ms
time to first byte 22 ms
resource load duration 21 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.99 s good 86.4% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 101 ms good 96.3% good
CLS CWV 0 good 98.5% good
FCP 1.31 s good 85.8% good
TTFB 988 ms needs-improvement 65% good

Lab vs field

Lab LCP 3.86 s · field p75 1.99 s · real users are 0.52× 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.94 s 99 ms 0 1.28 s 946 ms
2026-08-08 1.99 s 99 ms 0 1.33 s 988 ms
2026-08-01 2.00 s 103 ms 0 1.40 s 1.01 s
2026-07-25 2.00 s 110 ms 0 1.40 s 1.03 s
2026-07-18 2.02 s 128 ms 0 1.43 s 1.12 s
2026-07-11 2.01 s 113 ms 0 1.43 s 1.09 s
2026-07-04 1.97 s 106 ms 0 1.39 s 1.04 s
2026-06-27 1.88 s 120 ms 0 1.35 s 991 ms
2026-06-20 1.82 s 120 ms 0 1.26 s 956 ms
2026-06-13 1.82 s 120 ms 0 1.26 s 968 ms
2026-06-06 1.80 s 122 ms 0 1.25 s 989 ms
2026-05-30 1.78 s 108 ms 0 1.23 s 977 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 469 kB 469 kB ↓ -247 B (-0.1%) 469 kB 469 kB
Requests 43 43 → no change 43 43
Third-party Weight 9.5 kB 9.5 kB ↑ +30 B (+0.3%) 9.5 kB 9.5 kB
Third-party CPU 0 ms 0 ms → no change 0 ms 0 ms
Unused JS 62.6 kB 62.6 kB ↓ -8 B 62.5 kB 62.6 kB
Unused CSS 12.0 kB 12.1 kB ↓ -21 B (-0.2%) 12.0 kB 12.1 kB

By resource type

script 342 kB · 28 req
font 55.7 kB · 2 req
document 32.0 kB · 1 req
other 20.3 kB · 8 req
image 18.8 kB · 3 req
third party 9.5 kB · 4 req

Third parties 1 entities

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

ctfassets.net 9.5 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.06 s 1.10 s ↓ -37 ms (-3.4%) 1.06 s 1.10 s
Long Tasks 3 3 → no change 3 3
DOM Elements 331 331 → no change 331 331
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 3 3 → no change 3 3
A11y Failures 0 0 → no change 0 0
A11y Failing Nodes 0 0 → no change 0 0

Main thread work

script evaluation 517 ms
other 212 ms
script parse compile 149 ms
style layout 114 ms
parse HTML 40 ms
paint composite render 25 ms
garbage collection 7 ms

Axe violations axe-core 4.13.0, full rule set

3 violating nodes across 2 rules, 405 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 aria-allowed-role — ARIA role should be appropriate for the element 2 nodes
  • moderate region — All page content should be contained by landmarks 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 2 console errors

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, 1:31 PM UTC 86 3.86 s 0 155 ms 469 kB 3/3 ±16 2,494 29s
Aug 22, 2026, 1:30 PM UTC 84 4.02 s 0 205 ms 469 kB 3/3 ±21 2,492 28.9s
Aug 21, 2026, 12:50 PM UTC 85 4.01 s 0 154 ms 469 kB 3/3 ±25 2,477 27.3s

Embed this score

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