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 ·

eleventy-react.netlify.app

https://eleventy-react.netlify.app/

99 100 100 100 3AXE –CWV

Data from Aug 20, 2026, 9:30 PM UTC 3d old

Build Awesome Starters #63 · 1 measurement · 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.

Eleventy Built with Eleventy
Netlify Hosted by Netlify

Scores

99
Performance
no change
100
Accessibility
no change
100
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.26 s — — 2.26 s 2.26 s
CLS Cumulative Layout Shift 0.019 — — 0.019 0.019
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 788 ms — — 788 ms 788 ms
Speed Index 788 ms — — 788 ms 788 ms
TTFB Time to First Byte 606 ms — — 606 ms 606 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 2.26 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 29 ms
resource load delay 9 ms
time to first byte 8 ms
resource load duration 5 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 140 kB — — 140 kB 140 kB
Requests 5 — — 5 5
Third-party Weight 135 kB — — 135 kB 135 kB
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

image 135 kB · 2 req
document 3.3 kB · 1 req
other 1.5 kB · 2 req
third party 135 kB · 2 req

Third parties 1 entities

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

cloudfront.net 135 kB · 0 ms CPU

Page health

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

Main thread work

other 87 ms
style layout 47 ms
script evaluation 9 ms
paint composite render 5 ms
parse HTML 5 ms
script parse compile 1 ms

Axe violations axe-core 4.13.0, full rule set

3 violating nodes across 3 rules, 86 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 landmark-no-duplicate-main — Document should not have more than one main landmark 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node
  • 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

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 20, 2026, 9:30 PM UTC 99 2.26 s 0.019 0 ms 140 kB 3/3 ±1 2,468 20.2s

Embed this score

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