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 ·

lessonsofacto.com

https://lessonsofacto.com/

88 96 100 100 –CWV 24AXE

Data from Aug 21, 2026, 3:10 AM UTC — 16h old.

Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 16h

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
Cloudflare Hosted by Cloudflare

Scores

88
Performance
no change
96
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 3.84 s — — 3.84 s 3.84 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.73 s — — 1.73 s 1.73 s
Speed Index 1.73 s — — 1.73 s 1.73 s
TTFB Time to First Byte 616 ms — — 616 ms 616 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 89 ms
resource load duration 16 ms
time to first byte 15 ms
resource load delay 13 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.62 MB — — 1.62 MB 1.62 MB
Requests 67 — — 67 67
Third-party Weight 38.7 kB — — 38.7 kB 38.7 kB
Third-party CPU 21 ms — — 21 ms 21 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

other 970.4 kB · 26 req
image 321.9 kB · 23 req
font 156.1 kB · 3 req
document 127.7 kB · 2 req
script 46.9 kB · 7 req
third party 582.9 kB · 13 req

Third parties 4 entities

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

cloudflare.com 26.8 kB · 15 ms CPU
Cloudflare 11.5 kB · 6 ms CPU
workers.dev 494 B · 0 ms CPU
cloudflareinsights.com 36 B · 0 ms CPU

Page health

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

Main thread work

other 434 ms
style layout 149 ms
script evaluation 143 ms
parse HTML 67 ms
paint composite render 29 ms
script parse compile 24 ms

Axe violations axe-core 4.13.0, full rule set

24 violating nodes across 2 rules, 429 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 color-contrast — Elements must meet minimum color contrast ratio thresholds 23 nodes
  • moderate region — All page content should be contained by landmarks 1 node

Accessibility failures 1 of 24 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.

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 22 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, 3:10 AM UTC 88 3.84 s 0 0 ms 1.62 MB 3/3 ±7 2,429 39.7s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show lessonsofacto.com'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://lessonsofacto.com/"></speedlify-score>