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 ·

interviews.shanehudson.net

https://interviews.shanehudson.net/

100 93 100 90 –CWV 3AXE

Data from Aug 21, 2026, 1:17 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

100
Performance
no change
93
Accessibility
no change
100
Best Practices
no change
90
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 797 ms — — 797 ms 797 ms
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 797 ms — — 797 ms 797 ms
Speed Index 797 ms — — 797 ms 797 ms
TTFB Time to First Byte 628 ms — — 628 ms 628 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 51 ms
time to first byte 30 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 5.9 kB — — 5.9 kB 5.9 kB
Requests 3 — — 3 3
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

other 3.8 kB · 1 req
document 1.1 kB · 1 req
stylesheet 961 B · 1 req

Page health

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

Main thread work

other 50 ms
style layout 23 ms
script evaluation 6 ms
paint composite render 3 ms
parse HTML 2 ms
script parse compile 0 ms

Axe violations axe-core 4.13.0, full rule set

3 violating nodes across 3 rules, 79 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 heading-order — Heading levels should only increase by one 1 node
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • moderate region — All page content should be contained by landmarks 1 node

Accessibility failures 2 of 13 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 1 node
  • 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, 1:17 AM UTC 100 797 ms 0 0 ms 5.9 kB 3/3 ±0 3,408 20.9s

Embed this score

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