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 ·

sport-game-catalog.netlify.app

https://sport-game-catalog.netlify.app/

98 100 100 100 –CWV 6AXE

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

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

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

98
Performance
no change
100
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 2.26 s — — 2.26 s 2.26 s
CLS Cumulative Layout Shift 0.043 — — 0.043 0.043
TBT Total Blocking Time 41 ms — — 41 ms 41 ms
FCP First Contentful Paint 1.21 s — — 1.21 s 1.21 s
Speed Index 1.21 s — — 1.21 s 1.21 s
TTFB Time to First Byte 606 ms — — 606 ms 606 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 73 ms
resource load delay 10 ms
time to first byte 6 ms
resource load duration 6 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 433.0 kB — — 433.0 kB 433.0 kB
Requests 40 — — 40 40
Third-party Weight 95.1 kB — — 95.1 kB 95.1 kB
Third-party CPU 42 ms — — 42 ms 42 ms
Unused JS 34.7 kB — — 34.7 kB 34.7 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

image 226.8 kB · 19 req
script 116.1 kB · 5 req
font 65.0 kB · 3 req
document 15.1 kB · 1 req
other 5.8 kB · 11 req
stylesheet 4.2 kB · 1 req
third party 95.1 kB · 13 req

Third parties 3 entities

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

FullStory 83.4 kB · 34 ms CPU
honeybadger.io 8.5 kB · 7 ms CPU
Fathom Analytics 3.2 kB · 2 ms CPU

Page health

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

Main thread work

other 822 ms
script evaluation 524 ms
paint composite render 500 ms
style layout 268 ms
script parse compile 53 ms
parse HTML 41 ms
garbage collection 20 ms

Axe violations axe-core 4.13.0, full rule set

6 violating nodes across 3 rules, 540 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.

  • minor empty-heading — Headings should not be empty 4 nodes
  • critical button-name — Buttons must have discernible text 1 node
  • moderate heading-order — Heading levels should only increase by one 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, 7:42 AM UTC 98 2.26 s 0.043 41 ms 433.0 kB 3/3 ±23 2,953 31.4s

Embed this score

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