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 ·

stevenhicks.me

https://www.stevenhicks.me/

85 93 100 100 10AXE CWV

Data from Aug 22, 2026, 2:53 AM UTC 43h old

Built Awesome #914 · 2 measurements · 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.

Netlify Hosted by Netlify

Scores

85
Performance
no change
93
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.43 s 3.43 s 3.43 s
CLS Cumulative Layout Shift 0.001 0.001 0.001
TBT Total Blocking Time 143 ms 143 ms 143 ms
FCP First Contentful Paint 2.83 s 2.83 s 2.83 s
Speed Index 2.83 s 2.83 s 2.83 s
TTFB Time to First Byte 664 ms 664 ms 664 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 3.43 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.

time to first byte 181 ms
element render delay 141 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 519 kB 519 kB 519 kB
Requests 16 16 16
Third-party Weight 450 kB 450 kB 450 kB
Third-party CPU 104 ms 104 ms 104 ms
Unused JS 136 kB 136 kB 136 kB
Unused CSS 0 B 0 B 0 B

By resource type

script 330 kB · 4 req
font 110 kB · 3 req
image 63.0 kB · 2 req
stylesheet 11.9 kB · 4 req
document 2.1 kB · 1 req
other 409 B · 1 req
third party 450 kB · 12 req

Third parties 5 entities

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

Google Tag Manager 292 kB · 81 ms CPU
Bootstrap CDN 85.3 kB · 0 ms CPU
Google Fonts 32.8 kB · 0 ms CPU
Google Analytics 21.8 kB · 18 ms CPU
Cloudflare CDN 17.9 kB · 5 ms CPU

Page health

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

Main thread work

script evaluation 394 ms
other 123 ms
style layout 119 ms
script parse compile 86 ms
paint composite render 14 ms
parse HTML 13 ms

Axe violations axe-core 4.13.0, full rule set

10 violating nodes across 3 rules, 194 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 7 nodes
  • moderate heading-order — Heading levels should only increase by one 2 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node

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

  • heading-order — Heading elements are not in a sequentially-descending order 2 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 22, 2026, 2:53 AM UTC 85 3.43 s 0.001 143 ms 519 kB 3/3 ±1 2,460 22.2s
Aug 21, 2026, 7:36 PM UTC The "start lh:prepare:navigationMode" performance mark has not been set 242.1s

Embed this score

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