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 ·

joesahlsa.dev

https://joesahlsa.dev/

90 84 100 100 –CWV 17AXE

Data from Aug 21, 2026, 1:20 AM UTC — 17h old.

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

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

90
Performance
no change
84
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 2.90 s — — 2.90 s 2.90 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 1 ms — — 1 ms 1 ms
FCP First Contentful Paint 2.90 s — — 2.90 s 2.90 s
Speed Index 2.90 s — — 2.90 s 2.90 s
TTFB Time to First Byte 603 ms — — 603 ms 603 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 101 ms
time to first byte 7 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 261.4 kB — — 261.4 kB 261.4 kB
Requests 8 — — 8 8
Third-party Weight 37.6 kB — — 37.6 kB 37.6 kB
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 240.0 kB · 2 req
document 12.9 kB · 1 req
stylesheet 5.8 kB · 2 req
script 551 B · 1 req
other 370 B · 1 req
third party 37.6 kB · 2 req

Third parties 1 entities

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

Google Fonts 37.6 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 593 ms — — 593 ms 593 ms
Long Tasks 1 — — 1 1
DOM Elements 231 — — 231 231
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 17 — — 17 17
A11y Failures 3 — — 3 3
A11y Failing Nodes 17 — — 17 17

Main thread work

other 254 ms
style layout 167 ms
paint composite render 148 ms
parse HTML 12 ms
script evaluation 10 ms
script parse compile 1 ms

Axe violations axe-core 4.13.0, full rule set

17 violating nodes across 3 rules, 280 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 11 nodes
  • serious link-name — Links must have discernible text 3 nodes
  • serious listitem — <li> elements must be contained in a <ul> or <ol> 3 nodes

Accessibility failures 3 of 18 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. 11 nodes
  • link-name — Links do not have a discernible name 3 nodes
  • listitem — List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements. 3 nodes

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, 1:20 AM UTC 90 2.90 s 0 1 ms 261.4 kB 3/3 ±2 2,490 22.9s

Embed this score

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