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 ·

eleventyduo.netlify.app

https://eleventyduo.netlify.app/

53 100 100 100 0AXE –CWV

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

Build Awesome Starters #105 · 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.

Netlify Hosted by Netlify

Scores

53
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 6.64 s — — 6.64 s 6.64 s
CLS Cumulative Layout Shift 0.003 — — 0.003 0.003
TBT Total Blocking Time 342 ms — — 342 ms 342 ms
FCP First Contentful Paint 6.64 s — — 6.64 s 6.64 s
Speed Index 6.64 s — — 6.64 s 6.64 s
TTFB Time to First Byte 628 ms — — 628 ms 628 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 6.64 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 300 ms
time to first byte 29 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 963 kB — — 963 kB 963 kB
Requests 7 — — 7 7
Third-party Weight 955 kB — — 955 kB 955 kB
Third-party CPU 99 ms — — 99 ms 99 ms
Unused JS 878 kB — — 878 kB 878 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

script 937 kB · 2 req
font 17.5 kB · 1 req
stylesheet 3.6 kB · 2 req
document 2.0 kB · 1 req
third party 955 kB · 3 req

Third parties 2 entities

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

JSDelivr CDN 937 kB · 99 ms CPU
Google Fonts 18.3 kB · 0 ms CPU

Page health

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

Main thread work

script parse compile 268 ms
script evaluation 149 ms
other 73 ms
style layout 33 ms
paint composite render 10 ms
parse HTML 6 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 390 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.

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:27 PM UTC 53 6.64 s 0.003 342 ms 963 kB 3/3 ±6 3,273 25.4s

Embed this score

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