speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time — measured continuously.

Measurement runs · Embed a score ·

treypiepmeier.com

https://treypiepmeier.com/

98 94 100 100 9AXE –CWV

Data from Aug 21, 2026, 9:45 AM UTC 2d old

11ty Emeritus · 1 measurement · since Aug 21, 2026

Scores

98
Performance
no change
94
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 1.88 s — — 1.88 s 1.88 s
CLS Cumulative Layout Shift 0.089 — — 0.089 0.089
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 853 ms — — 853 ms 853 ms
Speed Index 853 ms — — 853 ms 853 ms
TTFB Time to First Byte 683 ms — — 683 ms 683 ms

What LCP is made of observed, unthrottled

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 1.88 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

element render delay 453 ms
time to first byte 95 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 196 kB — — 196 kB 196 kB
Requests 4 — — 4 4
Third-party Weight 0 B — — 0 B 0 B
Third-party CPU 0 ms — — 0 ms 0 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

font 183 kB · 1 req
stylesheet 6.2 kB · 1 req
document 5.5 kB · 1 req
other 2.0 kB · 1 req

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 131 ms — — 131 ms 131 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 9 — — 9 9
A11y Failures 2 — — 2 2
A11y Failing Nodes 5 — — 5 5

Main thread work

other 72 ms
style layout 37 ms
script evaluation 10 ms
parse HTML 8 ms
paint composite render 4 ms
script parse compile 1 ms

Axe violations axe-core 4.13.0, full rule set

9 violating nodes across 4 rules, 128 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.

  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 4 nodes
  • moderate region — All page content should be contained by landmarks 3 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • moderate page-has-heading-one — Page should contain a level-one heading 1 node

Accessibility failures 2 of 23 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.

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 4 nodes
  • 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

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, 9:45 AM UTC 98 1.88 s 0.089 0 ms 196 kB 3/3 ±2 2,457 22s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show treypiepmeier.com's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify2-score.js component code into your site! 

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://treypiepmeier.com/"></speedlify2-score>