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 ·

jamstack-comments.netlify.app

https://jamstack-comments.netlify.app/

100 97 100 90 ✓CWV 6AXE

Data from Aug 21, 2026, 1:18 AM UTC — 17h old.

Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 17h

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.

Netlify Hosted by Netlify

Core Web Vitals field data, url-level

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

LCP 1.53 s good
INP — no data
CLS 0 good

Scores

100
Performance
no change
97
Accessibility
no change
100
Best Practices
no change
90
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 797 ms — — 797 ms 797 ms
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 797 ms — — 797 ms 797 ms
Speed Index 797 ms — — 797 ms 797 ms
TTFB Time to First Byte 633 ms — — 633 ms 633 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 39 ms
time to first byte 34 ms

Field data Chrome UX Report, url-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.53 s good 94.4% good
CLS CWV 0 good 99.4% good
FCP 1.54 s good 84.5% good
TTFB 1.34 s needs-improvement 46.4% good

Lab vs field

Lab LCP 797 ms · field p75 1.53 s · real users are 1.92× slower than the lab. A gap this wide usually means real users are on slower devices or networks than the simulated ones — the lab number is flattering you.

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-15 1.58 s — 0 1.59 s 1.42 s
2026-08-08 1.49 s — 0 1.55 s 1.41 s
2026-08-01 1.49 s — 0 1.49 s 1.33 s
2026-07-25 1.45 s — 0 1.45 s 1.27 s
2026-07-18 1.37 s — 0 1.37 s 1.27 s
2026-07-11 1.42 s — 0 1.43 s 1.32 s
2026-07-04 1.35 s — 0 1.35 s 1.25 s
2026-06-27 1.25 s — 0 1.25 s 1.15 s
2026-06-20 1.17 s — 0 1.18 s 1.10 s
2026-06-13 1.16 s — 0 1.17 s 1.08 s
2026-06-06 1.22 s — 0 1.22 s 1.09 s
2026-05-30 1.25 s — 0 1.25 s 1.09 s

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 2.3 kB — — 2.3 kB 2.3 kB
Requests 1 — — 1 1
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

document 2.3 kB · 1 req

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 60 ms — — 60 ms 60 ms
Long Tasks 0 — — 0 0
DOM Elements 33 — — 33 33
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 6 — — 6 6
A11y Failures 1 — — 1 1
A11y Failing Nodes 1 — — 1 1

Main thread work

other 38 ms
style layout 9 ms
script evaluation 7 ms
parse HTML 3 ms
paint composite render 2 ms
script parse compile 1 ms

Axe violations axe-core 4.13.0, full rule set

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

  • moderate region — All page content should be contained by landmarks 5 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node

Accessibility failures 1 of 13 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.

  • landmark-one-main — Document does not have a main landmark. 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, 1:18 AM UTC 100 797 ms 0 0 ms 2.3 kB 3/3 ±0 3,403 18.9s

Embed this score

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