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 ·

thisis11ty.netlify.app

https://thisis11ty.netlify.app/

100 100 100 100 9AXE –CWV

Data from Aug 21, 2026, 8:47 AM UTC 2d old

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

Eleventy 2.0.1 Built with Eleventy 2.0.1
Netlify Hosted by Netlify

Scores

100
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 920 ms — — 920 ms 920 ms
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 920 ms — — 920 ms 920 ms
Speed Index 920 ms — — 920 ms 920 ms
TTFB Time to First Byte 600 ms — — 600 ms 600 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 920 ms above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

time to first byte 99 ms
element render delay 45 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 35.3 kB — — 35.3 kB 35.3 kB
Requests 2 — — 2 2
Third-party Weight 5.1 kB — — 5.1 kB 5.1 kB
Third-party CPU 0 ms — — 0 ms 0 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 27.6 kB — — 27.6 kB 27.6 kB

By resource type

document 30.2 kB · 1 req
other 5.1 kB · 1 req
third party 5.1 kB · 1 req

Third parties 1 entities

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

pages.dev 5.1 kB · 0 ms CPU

Page health

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

Main thread work

other 69 ms
style layout 30 ms
parse HTML 28 ms
script evaluation 9 ms
paint composite render 4 ms
script parse compile 1 ms

Axe violations axe-core 4.13.0, full rule set

9 violating nodes across 1 rule, 309 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 9 nodes

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, 8:47 AM UTC 100 920 ms 0 0 ms 35.3 kB 3/3 ±1 3,226 20.7s

Embed this score

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