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 ·

mikesthoughts.blog

https://mikesthoughts.blog/

100 96 88 45 –CWV 3AXE

Data from Aug 21, 2026, 4:40 AM UTC — 14h old.

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

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.

Op Hosted by Self-hosted

Scores

100
Performance
no change
96
Accessibility
no change
88
Best Practices
no change
45
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.72 s — — 1.72 s 1.72 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 814 ms — — 814 ms 814 ms
Speed Index 986 ms — — 986 ms 986 ms
TTFB Time to First Byte 651 ms — — 651 ms 651 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 418 ms
time to first byte 53 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 16.2 kB — — 16.2 kB 16.2 kB
Requests 5 — — 5 5
Third-party Weight 13.2 kB — — 13.2 kB 13.2 kB
Third-party CPU 1 ms — — 1 ms 1 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

other 11.7 kB · 2 req
document 3.1 kB · 1 req
script 1.4 kB · 1 req
third party 13.2 kB · 3 req

Third parties 1 entities

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

parklogic.com 13.2 kB · 1 ms CPU

Page health

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

Main thread work

other 58 ms
script evaluation 53 ms
style layout 12 ms
script parse compile 3 ms
paint composite render 2 ms
parse HTML 2 ms

Axe violations axe-core 4.13.0, full rule set

3 violating nodes across 2 rules, 83 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 2 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node

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

  • landmark-one-main — Document does not have a main landmark. 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 1 console error

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, 4:40 AM UTC 100 1.72 s 0 0 ms 16.2 kB 3/3 ±0 4,342 68.7s

Embed this score

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