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 ·

dustinwhisman.com

https://dustinwhisman.com/

Data from Aug 20, 2026, 8:33 PM UTC — 21h old.

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

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

Scores

100
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 926 ms 926 ms 926 ms
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 806 ms 806 ms 806 ms
Speed Index 806 ms 806 ms 806 ms
TTFB Time to First Byte 626 ms 626 ms 626 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.

resource load duration 50 ms
time to first byte 28 ms
element render delay 15 ms
resource load delay 10 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 164.5 kB 164.5 kB 164.5 kB
Requests 12 12 12
Third-party Weight 1.4 kB 1.4 kB 1.4 kB
Third-party CPU 3 ms 3 ms 3 ms
Unused JS 0 B 0 B 0 B
Unused CSS 0 B 0 B 0 B

By resource type

image 153.8 kB · 5 req
stylesheet 4.0 kB · 1 req
document 2.5 kB · 1 req
other 2.4 kB · 3 req
script 1.8 kB · 2 req
third party 1.4 kB · 2 req

Third parties 1 entities

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

tinylytics.app 1.4 kB · 3 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 315 ms 315 ms 315 ms
Long Tasks 0 0 0
DOM Elements 98 98 98
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

other 207 ms
style layout 58 ms
script evaluation 27 ms
paint composite render 14 ms
parse HTML 8 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 227 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, 8:33 PM UTC 100 926 ms 0 0 ms 164.5 kB 3/3 ±2 2,463 24s

Embed this score

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