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 ·

mattnortham.com

https://www.mattnortham.com/

90 100 100 100 CWV 1AXE

Data from Aug 21, 2026, 6:35 PM UTC — 38m old.

Built Awesome · 2 measurements · since Aug 21, 2026 · last attempt 38m

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 1.0.2 Built with Eleventy 1.0.2
Netlify Hosted by Netlify

Scores

90
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 3.20 s 3.20 s 3.20 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 65 ms 65 ms 65 ms
FCP First Contentful Paint 2.18 s 2.18 s 2.18 s
Speed Index 2.72 s 2.72 s 2.72 s
TTFB Time to First Byte 772 ms 772 ms 772 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.

time to first byte 528 ms
resource load delay 317 ms
resource load duration 145 ms
element render delay 86 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 405.2 kB 405.2 kB 405.2 kB
Requests 20 20 20
Third-party Weight 60.4 kB 60.4 kB 60.4 kB
Third-party CPU 144 ms 144 ms 144 ms
Unused JS 0 B 0 B 0 B
Unused CSS 21.3 kB 21.3 kB 21.3 kB

By resource type

font 108.4 kB · 4 req
image 106.1 kB · 5 req
other 96.2 kB · 2 req
script 75.1 kB · 5 req
stylesheet 11.5 kB · 1 req
document 5.6 kB · 1 req
third party 60.4 kB · 3 req

Third parties 2 entities

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

Netlify 55.2 kB · 37 ms CPU
simpleanalyticscdn.com 5.2 kB · 107 ms CPU

Page health

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

Main thread work

other 1.05 s
script evaluation 761 ms
style layout 428 ms
paint composite render 250 ms
parse HTML 112 ms
garbage collection 55 ms
script parse compile 30 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 331 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 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, 6:35 PM UTC 90 3.20 s 0 65 ms 405.2 kB 3/3 ±10 2,028 32s
Aug 21, 2026, 11:28 AM UTC The "start lh:driver:navigate" performance mark has not been set 159.2s

Embed this score

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