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 ·

neat-starter.netlify.app

https://neat-starter.netlify.app/

98 90 100 90 CWV 4AXE

Data from Aug 21, 2026, 4:38 AM UTC — 14h old.

Build Awesome Starters · 1 measurement · since Aug 21, 2026 · last attempt 14h

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

Scores

98
Performance
no change
90
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 1.87 s 1.87 s 1.87 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 1 ms 1 ms 1 ms
FCP First Contentful Paint 1.87 s 1.87 s 1.87 s
Speed Index 1.87 s 1.87 s 1.87 s
TTFB Time to First Byte 606 ms 606 ms 606 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 52 ms
time to first byte 8 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 77.7 kB 77.7 kB 77.7 kB
Requests 5 5 5
Third-party Weight 55.1 kB 55.1 kB 55.1 kB
Third-party CPU 25 ms 25 ms 25 ms
Unused JS 0 B 0 B 0 B
Unused CSS 21.3 kB 21.3 kB 21.3 kB

By resource type

script 69.1 kB · 2 req
stylesheet 6.0 kB · 1 req
document 1.6 kB · 1 req
third party 55.1 kB · 1 req

Third parties 1 entities

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

Netlify 55.1 kB · 25 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 250 ms 250 ms 250 ms
Long Tasks 2 2 2
DOM Elements 46 46 46
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 4 4 4
A11y Failures 3 3 3
A11y Failing Nodes 3 3 3

Main thread work

script evaluation 109 ms
other 73 ms
style layout 28 ms
script parse compile 27 ms
parse HTML 10 ms
paint composite render 3 ms

Axe violations axe-core 4.13.0, full rule set

4 violating nodes across 4 rules, 81 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
  • moderate heading-order — Heading levels should only increase by one 1 node
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • moderate region — All page content should be contained by landmarks 1 node

Accessibility failures 3 of 17 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.

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 1 node
  • heading-order — Heading elements are not in a sequentially-descending order 1 node
  • 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, 4:38 AM UTC 98 1.87 s 0 1 ms 77.7 kB 3/3 ±9 2,483 21.2s

Embed this score

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