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 ·

olivernorred.com/blog

https://olivernorred.com/blog

85 81 100 100 –CWV 1AXE

Data from Aug 21, 2026, 5:41 AM UTC — 13h old.

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

This URL redirects to https://olivernorred.com/blog/.

A trailing slash only, so both forms are treated as one site rather than two — one history, measured once. Lighthouse follows the redirect, so the numbers below describe the canonical page; the only cost is an extra hop on each run.

Scores

85
Performance
no change
81
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.65 s — — 3.65 s 3.65 s
CLS Cumulative Layout Shift 0.027 — — 0.027 0.027
TBT Total Blocking Time 78 ms — — 78 ms 78 ms
FCP First Contentful Paint 2.61 s — — 2.61 s 2.61 s
Speed Index 2.61 s — — 2.61 s 2.61 s
TTFB Time to First Byte 454 ms — — 454 ms 454 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 100 ms
time to first byte 8 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 522.7 kB — — 522.7 kB 522.7 kB
Requests 20 — — 20 20
Third-party Weight 261.9 kB — — 261.9 kB 261.9 kB
Third-party CPU 56 ms — — 56 ms 56 ms
Unused JS 115.7 kB — — 115.7 kB 115.7 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

script 260.6 kB · 5 req
font 250.9 kB · 5 req
stylesheet 6.9 kB · 5 req
document 3.0 kB · 1 req
other 1.3 kB · 4 req
third party 261.9 kB · 8 req

Third parties 4 entities

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

Google Tag Manager 150.1 kB · 45 ms CPU
Google CDN 109.9 kB · 11 ms CPU
Adobe TypeKit 1.6 kB · 0 ms CPU
Firebase 250 B · 0 ms CPU

Page health

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

Main thread work

script evaluation 218 ms
other 122 ms
style layout 64 ms
script parse compile 54 ms
parse HTML 13 ms
paint composite render 9 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 354 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 1 node

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

  • target-size — Touch targets do not have sufficient size or spacing. 4 nodes
  • link-in-text-block — Links rely on color to be distinguishable. 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 21, 2026, 5:41 AM UTC 85 3.65 s 0.027 78 ms 522.7 kB 3/3 ±16 2,409 23.2s

Embed this score

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