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 ·

slay.sh

https://slay.sh/

93 96 77 90 CWV 6AXE

Data from Aug 21, 2026, 6:49 AM UTC — 12h old.

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

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

93
Performance
no change
96
Accessibility
no change
77
Best Practices
no change
90
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.87 s 2.87 s 2.87 s
CLS Cumulative Layout Shift 0.005 0.005 0.005
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 2.26 s 2.26 s 2.26 s
Speed Index 2.26 s 2.26 s 2.26 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 98 ms
time to first byte 6 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 221.5 kB 221.5 kB 221.5 kB
Requests 15 15 15
Third-party Weight 71.8 kB 71.8 kB 71.8 kB
Third-party CPU 31 ms 31 ms 31 ms
Unused JS 0 B 0 B 0 B
Unused CSS 0 B 0 B 0 B

By resource type

document 133.8 kB · 3 req
script 45.8 kB · 4 req
font 36.4 kB · 1 req
stylesheet 4.8 kB · 4 req
other 481 B · 1 req
image 184 B · 1 req
third party 191.6 kB · 10 req

Third parties 3 entities

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

Adobe TypeKit 37.6 kB · 0 ms CPU
Twitter 30.7 kB · 28 ms CPU
Cloudflare CDN 3.5 kB · 3 ms CPU

Page health

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

Main thread work

script evaluation 205 ms
other 134 ms
style layout 89 ms
paint composite render 22 ms
script parse compile 19 ms
parse HTML 13 ms
garbage collection 4 ms

Axe violations axe-core 4.13.0, full rule set

6 violating nodes across 4 rules, 266 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.

  • moderate page-has-heading-one — Page should contain a level-one heading 2 nodes
  • serious scrollable-region-focusable — Scrollable region must have keyboard access 2 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 1 node
  • moderate region — All page content should be contained by landmarks 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.

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 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, 6:49 AM UTC 93 2.87 s 0.005 0 ms 221.5 kB 3/3 ±4 2,478 24.9s

Embed this score

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