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 ·

austinjavascript.com

https://austinjavascript.com/

95 96 77 100 –CWV 1AXE

Data from Aug 20, 2026, 3:46 PM UTC — 27h old.

Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 27h

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.

GitHub Pages Hosted by GitHub Pages

Scores

95
Performance
no change
96
Accessibility
no change
77
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.12 s — — 2.12 s 2.12 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 210 ms — — 210 ms 210 ms
FCP First Contentful Paint 1.60 s — — 1.60 s 1.60 s
Speed Index 1.60 s — — 1.60 s 1.60 s
TTFB Time to First Byte 535 ms — — 535 ms 535 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 54 ms
time to first byte 26 ms
resource load duration 25 ms
resource load delay 12 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 998.8 kB — — 998.8 kB 998.8 kB
Requests 141 — — 141 141
Third-party Weight 190.3 kB — — 190.3 kB 190.3 kB
Third-party CPU 113 ms — — 113 ms 113 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

script 455.4 kB · 25 req
image 414.3 kB · 102 req
other 55.4 kB · 6 req
font 32.4 kB · 1 req
stylesheet 22.3 kB · 5 req
document 19.1 kB · 2 req
third party 572.9 kB · 37 req

Third parties 3 entities

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

Google Tag Manager 157.9 kB · 66 ms CPU
Google Analytics 20.9 kB · 42 ms CPU
Cloudflare 11.5 kB · 4 ms CPU

Page health

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

Main thread work

other 546 ms
script evaluation 517 ms
style layout 163 ms
paint composite render 158 ms
script parse compile 77 ms
parse HTML 21 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 2325 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 frame-title — Frames must have an accessible name 1 node

Accessibility failures 1 of 24 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.

  • frame-title — `<frame>` or `<iframe>` elements do not have a title 1 node

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h3

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 20, 2026, 3:46 PM UTC 95 2.12 s 0 210 ms 998.8 kB 3/3 ±10 2,334 30.9s

Embed this score

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