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 ·

peterthaleikis.com

https://peterthaleikis.com/

66 90 73 100 CWV 0AXE

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

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

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.

Netlify Hosted by Netlify

Scores

66
Performance
no change
90
Accessibility
no change
73
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 3.96 s 3.96 s 3.96 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 554 ms 554 ms 554 ms
FCP First Contentful Paint 2.61 s 2.61 s 2.61 s
Speed Index 5.39 s 5.39 s 5.39 s
TTFB Time to First Byte 643 ms 643 ms 643 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 112 ms
time to first byte 44 ms
resource load delay 34 ms
resource load duration 23 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 22.79 MB 22.79 MB 22.79 MB
Requests 207 207 207
Third-party Weight 22.26 MB 22.26 MB 22.26 MB
Third-party CPU 281 ms 281 ms 281 ms
Unused JS 276.5 kB 276.5 kB 276.5 kB
Unused CSS 12.7 kB 12.7 kB 12.7 kB

By resource type

image 21.56 MB · 123 req
script 787.0 kB · 24 req
font 192.9 kB · 3 req
other 150.2 kB · 38 req
document 86.8 kB · 16 req
stylesheet 14.8 kB · 2 req
third party 22.77 MB · 201 req

Third parties 9 entities

22.26 MB transferred, 281 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

cloudfront.net 21.48 MB · 0 ms CPU
Google/Doubleclick Ads 291.6 kB · 175 ms CPU
FontAwesome CDN 162.8 kB · 0 ms CPU
Google Tag Manager 155.4 kB · 50 ms CPU
Google FundingChoices 78.1 kB · 24 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 3.90 s 3.90 s 3.90 s
Long Tasks 9 9 9
DOM Elements 569 569 569
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 0 0 0
A11y Failures 2 2 2
A11y Failing Nodes 29 29 29

Main thread work

script evaluation 2.05 s
other 1.13 s
style layout 322 ms
script parse compile 178 ms
paint composite render 156 ms
garbage collection 36 ms
parse HTML 33 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 877 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.

Accessibility failures 2 of 22 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. 28 nodes
  • button-name — Buttons do not have an accessible name 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, 5:40 AM UTC 66 3.96 s 0 554 ms 22.79 MB 3/3 ±17 2,468 57.4s

Embed this score

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