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 ·

josephrex.me

https://www.josephrex.me/

100 100 100 100 1AXE –CWV

Data from Aug 21, 2026, 6:41 PM UTC 2d old

Built Awesome #346 · 1 measurement · since Aug 21, 2026

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 3.1.1 Built with Eleventy 3.1.1
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 799 ms — — 799 ms 799 ms
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 88 ms — — 88 ms 88 ms
FCP First Contentful Paint 799 ms — — 799 ms 799 ms
Speed Index 799 ms — — 799 ms 799 ms
TTFB Time to First Byte 608 ms — — 608 ms 608 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 799 ms 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 35 ms
time to first byte 10 ms

Page weight

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

By resource type

script 163 kB · 1 req
document 8.6 kB · 1 req
other 2.2 kB · 2 req
third party 163 kB · 1 req

Third parties 1 entities

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

Google Tag Manager 163 kB · 48 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 351 ms — — 351 ms 351 ms
Long Tasks 2 — — 2 2
DOM Elements 131 — — 131 131
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

script evaluation 169 ms
other 75 ms
script parse compile 41 ms
style layout 40 ms
parse HTML 12 ms
garbage collection 8 ms
paint composite render 6 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 305 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:41 PM UTC 100 799 ms 0 88 ms 174 kB 3/3 ±1 2,360 21.4s

Embed this score

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