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 ·

gametime.events

https://gametime.events/

46 91 96 100 CWV 12AXE

Data from Aug 20, 2026, 11:26 PM UTC — 19h old.

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

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
Netlify Hosted by Netlify

Scores

46
Performance
no change
91
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 9.79 s 9.79 s 9.79 s
CLS Cumulative Layout Shift 0.004 0.004 0.004
TBT Total Blocking Time 1.19 s 1.19 s 1.19 s
FCP First Contentful Paint 1.73 s 1.73 s 1.73 s
Speed Index 5.50 s 5.50 s 5.50 s
TTFB Time to First Byte 630 ms 630 ms 630 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 251 ms
resource load duration 138 ms
time to first byte 29 ms
resource load delay 27 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 21.39 MB 21.39 MB 21.39 MB
Requests 106 106 106
Third-party Weight 663.5 kB 663.5 kB 663.5 kB
Third-party CPU 351 ms 351 ms 351 ms
Unused JS 287.3 kB 287.3 kB 287.3 kB
Unused CSS 30.8 kB 30.8 kB 30.8 kB

By resource type

media 13.15 MB · 1 req
image 6.31 MB · 27 req
script 1.59 MB · 43 req
stylesheet 133.1 kB · 4 req
document 106.4 kB · 3 req
font 91.1 kB · 4 req
other 9.1 kB · 24 req
third party 1.87 MB · 71 req

Third parties 7 entities

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

Google CDN 344.0 kB · 81 ms CPU
Google Tag Manager 165.4 kB · 117 ms CPU
FullStory 83.3 kB · 75 ms CPU
Unpkg 55.1 kB · 1 ms CPU
honeybadger.io 11.9 kB · 75 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 6.40 s 6.40 s 6.40 s
Long Tasks 17 17 17
DOM Elements 695 695 695
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 12 12 12
A11y Failures 3 3 3
A11y Failing Nodes 8 8 8

Main thread work

script evaluation 2.69 s
other 1.85 s
paint composite render 955 ms
script parse compile 360 ms
style layout 359 ms
parse HTML 109 ms
garbage collection 78 ms

Axe violations axe-core 4.13.0, full rule set

12 violating nodes across 6 rules, 1071 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.

  • critical button-name — Buttons must have discernible text 6 nodes
  • serious list — <ul> and <ol> must only directly contain <li>, <script> or <template> elements 2 nodes
  • critical aria-allowed-attr — Elements must only use supported ARIA attributes 1 node
  • serious aria-prohibited-attr — Elements must only use permitted ARIA attributes 1 node
  • minor empty-heading — Headings should not be empty 1 node
  • moderate region — All page content should be contained by landmarks 1 node

Accessibility failures 3 of 29 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.

  • button-name — Buttons do not have an accessible name 6 nodes
  • list — Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`). 1 node
  • label-content-name-mismatch — Elements with visible text labels do not have matching accessible names. 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 20, 2026, 11:26 PM UTC 46 9.79 s 0.004 1.19 s 21.39 MB 3/3 ±5 2,367 73.1s

Embed this score

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