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 ·

briangershon.com

https://www.briangershon.com/

100 91 100 100 –CWV 4AXE

Data from Aug 21, 2026, 11:27 AM UTC — 7h old.

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

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.

Vercel Hosted by Vercel

Scores

100
Performance
no change
91
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 1.82 s — — 1.82 s 1.82 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 911 ms — — 911 ms 911 ms
Speed Index 911 ms — — 911 ms 911 ms
TTFB Time to First Byte 611 ms — — 611 ms 611 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 31 ms
resource load duration 19 ms
resource load delay 19 ms
time to first byte 4 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 227.3 kB — — 227.3 kB 227.3 kB
Requests 15 — — 15 15
Third-party Weight 133.5 kB — — 133.5 kB 133.5 kB
Third-party CPU 3 ms — — 3 ms 3 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

image 142.0 kB · 9 req
other 58.0 kB · 2 req
script 14.4 kB · 2 req
stylesheet 8.3 kB · 1 req
document 4.6 kB · 1 req
third party 133.5 kB · 5 req

Third parties 2 entities

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

stashfive.com 130.4 kB · 0 ms CPU
Fathom Analytics 3.2 kB · 3 ms CPU

Page health

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

Main thread work

other 1.31 s
script evaluation 494 ms
style layout 48 ms
paint composite render 41 ms
garbage collection 18 ms
parse HTML 13 ms
script parse compile 6 ms

Axe violations axe-core 4.13.0, full rule set

4 violating nodes across 2 rules, 192 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 3 nodes
  • minor image-redundant-alt — Alternative text of images should not be repeated as text 1 node

Accessibility failures 1 of 12 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 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, 11:27 AM UTC 100 1.82 s 0 0 ms 227.3 kB 3/3 ±0 2,497 22.8s

Embed this score

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