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 ·

eleventy-chirpy-blog-template.netlify.app

https://eleventy-chirpy-blog-template.netlify.app/

99 100 100 69 –CWV 10AXE

Data from Aug 20, 2026, 8:35 PM UTC — 22h old.

Build Awesome Starters · 1 measurement · since Aug 20, 2026 · last attempt 22h

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

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

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.05 s — — 2.05 s 2.05 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 2 ms — — 2 ms 2 ms
FCP First Contentful Paint 925 ms — — 925 ms 925 ms
Speed Index 925 ms — — 925 ms 925 ms
TTFB Time to First Byte 625 ms — — 625 ms 625 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 105 ms
time to first byte 27 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 136.5 kB — — 136.5 kB 136.5 kB
Requests 9 — — 9 9
Third-party Weight 89.1 kB — — 89.1 kB 89.1 kB
Third-party CPU 16 ms — — 16 ms 16 ms
Unused JS 56.6 kB — — 56.6 kB 56.6 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

script 104.9 kB · 3 req
other 11.6 kB · 2 req
document 8.4 kB · 1 req
stylesheet 7.3 kB · 2 req
image 4.3 kB · 1 req
third party 89.1 kB · 1 req

Third parties 1 entities

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

Google Tag Manager 89.1 kB · 16 ms CPU

Page health

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

Main thread work

script evaluation 86 ms
other 85 ms
style layout 29 ms
script parse compile 27 ms
parse HTML 11 ms
paint composite render 4 ms

Axe violations axe-core 4.13.0, full rule set

10 violating nodes across 2 rules, 217 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
  • moderate page-has-heading-one — Page should contain a level-one heading 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, 8:35 PM UTC 99 2.05 s 0 2 ms 136.5 kB 3/3 ±4 2,473 22s

Embed this score

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