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 ·

indieweb-blog-starter.netlify.app

https://indieweb-blog-starter.netlify.app/

100 92 100 100 CWV 3AXE

Data from Aug 20, 2026, 11:34 PM UTC — 19h old.

Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 19h

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

100
Performance
no change
92
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 942 ms 942 ms 942 ms
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 942 ms 942 ms 942 ms
Speed Index 942 ms 942 ms 942 ms
TTFB Time to First Byte 642 ms 642 ms 642 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 127 ms
time to first byte 35 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 25.7 kB 25.7 kB 25.7 kB
Requests 21 21 21
Third-party Weight 0 B 0 B 0 B
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

stylesheet 15.6 kB · 17 req
document 7.1 kB · 1 req
image 1.3 kB · 1 req
other 865 B · 1 req
script 801 B · 1 req

Page health

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

Main thread work

other 121 ms
style layout 61 ms
parse HTML 14 ms
script evaluation 12 ms
paint composite render 10 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

3 violating nodes across 2 rules, 622 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 link-in-text-block — Links must be distinguishable without relying on color 2 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 1 node

Accessibility failures 2 of 25 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.

  • link-in-text-block — Links rely on color to be distinguishable. 2 nodes
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 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, 11:34 PM UTC 100 942 ms 0 0 ms 25.7 kB 3/3 ±0 2,331 23.2s

Embed this score

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