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 ·

blog.andrewshell.org

https://blog.andrewshell.org/

Data from Aug 20, 2026, 7:08 PM UTC — 22h old.

11ty Emeritus · 1 measurement · since Aug 20, 2026 · last attempt 22h

This URL redirects to https://andrewshell.org/.

Lighthouse follows the redirect, so the numbers below describe the destination page, not this one. Not yet confirmed as a move; it needs to lead to the same place on several consecutive runs first.

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.

WordPress 7.1 Built with WordPress 7.1
Li Hosted by Self-hosted

Scores

76
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.19 s — — 6.19 s 6.19 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 112 ms — — 112 ms 112 ms
FCP First Contentful Paint 1.69 s — — 1.69 s 1.69 s
Speed Index 2.24 s — — 2.24 s 2.24 s
TTFB Time to First Byte 607 ms — — 607 ms 607 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 66 ms
time to first byte 9 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 972.8 kB — — 972.8 kB 972.8 kB
Requests 23 — — 23 23
Third-party Weight 167.3 kB — — 167.3 kB 167.3 kB
Third-party CPU 58 ms — — 58 ms 58 ms
Unused JS 70.0 kB — — 70.0 kB 70.0 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

image 782.5 kB · 5 req
script 168.7 kB · 5 req
document 11.7 kB · 1 req
stylesheet 6.9 kB · 5 req
other 3.0 kB · 6 req
third party 167.3 kB · 9 req

Third parties 5 entities

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

Google Tag Manager 158.0 kB · 55 ms CPU
umami.is 3.3 kB · 2 ms CPU
iheartrss.com 2.7 kB · 0 ms CPU
WordPress Site Stats 1.9 kB · 1 ms CPU
WordPress 1.3 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 551 ms — — 551 ms 551 ms
Long Tasks 2 — — 2 2
DOM Elements 157 — — 157 157
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 evaluation 243 ms
other 147 ms
script parse compile 71 ms
style layout 56 ms
parse HTML 24 ms
paint composite render 11 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 349 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, 7:08 PM UTC 76 6.19 s 0 112 ms 972.8 kB 3/3 ±1 2,489 23.8s

Embed this score

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