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 ·

nealgamradt.com

https://nealgamradt.com/

74 63 96 100 CWV 12AXE

Data from Aug 21, 2026, 4:52 AM UTC — 14h old.

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

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 Built with Eleventy
Amazon S3 Hosted by Amazon S3

Scores

74
Performance
no change
63
Accessibility
no change
96
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 4.93 s 4.93 s 4.93 s
CLS Cumulative Layout Shift 0.004 0.004 0.004
TBT Total Blocking Time 179 ms 179 ms 179 ms
FCP First Contentful Paint 3.00 s 3.00 s 3.00 s
Speed Index 3.00 s 3.00 s 3.00 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 145 ms
time to first byte 3 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 486.4 kB 486.4 kB 486.4 kB
Requests 19 19 19
Third-party Weight 232.7 kB 232.7 kB 232.7 kB
Third-party CPU 84 ms 84 ms 84 ms
Unused JS 95.0 kB 95.0 kB 95.0 kB
Unused CSS 12.6 kB 12.6 kB 12.6 kB

By resource type

script 236.4 kB · 4 req
font 189.1 kB · 5 req
image 24.8 kB · 1 req
stylesheet 23.8 kB · 3 req
other 9.3 kB · 4 req
document 2.9 kB · 1 req
third party 232.7 kB · 10 req

Third parties 4 entities

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

Google Tag Manager 170.2 kB · 65 ms CPU
Google Fonts 34.9 kB · 0 ms CPU
Clarity 27.5 kB · 19 ms CPU
Google Analytics 48 B · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 653 ms 653 ms 653 ms
Long Tasks 4 4 4
DOM Elements 65 65 65
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 12 12 12
A11y Failures 5 5 5
A11y Failing Nodes 9 9 9

Main thread work

script evaluation 336 ms
other 117 ms
script parse compile 99 ms
style layout 75 ms
parse HTML 20 ms
paint composite render 6 ms

Axe violations axe-core 4.13.0, full rule set

12 violating nodes across 6 rules, 87 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 link-name — Links must have discernible text 5 nodes
  • moderate region — All page content should be contained by landmarks 3 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 1 node
  • serious html-has-lang — <html> element must have a lang attribute 1 node
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • moderate meta-viewport — Zooming and scaling must not be disabled 1 node

Accessibility failures 5 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.

  • link-name — Links do not have a discernible name 5 nodes
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 1 node
  • html-has-lang — `<html>` element does not have a `[lang]` attribute 1 node
  • meta-viewport — `[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5. 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, 4:52 AM UTC 74 4.93 s 0.004 179 ms 486.4 kB 3/3 ±18 2,515 26.9s

Embed this score

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