speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time — measured continuously.

Measurement runs · Embed a score ·

ride.netlify.app/latest

https://ride.netlify.app/latest

84 73 100 82 8AXE –CWV

Data from Aug 21, 2026, 6:49 AM UTC 2d old

Built Awesome #1,085 · 1 measurement · since Aug 21, 2026

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

84
Performance
no change
73
Accessibility
no change
100
Best Practices
no change
82
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.67 s — — 1.67 s 1.67 s
CLS Cumulative Layout Shift 0.323 — — 0.323 0.323
TBT Total Blocking Time 52 ms — — 52 ms 52 ms
FCP First Contentful Paint 826 ms — — 826 ms 826 ms
Speed Index 826 ms — — 826 ms 826 ms
TTFB Time to First Byte 620 ms — — 620 ms 620 ms

What LCP is made of observed, unthrottled

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 1.67 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

element render delay 51 ms
time to first byte 33 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 175 kB — — 175 kB 175 kB
Requests 12 — — 12 12
Third-party Weight 162 kB — — 162 kB 162 kB
Third-party CPU 78 ms — — 78 ms 78 ms
Unused JS 129 kB — — 129 kB 129 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

script 146 kB · 4 req
image 15.9 kB · 4 req
document 10.0 kB · 2 req
other 2.6 kB · 2 req
third party 162 kB · 8 req

Third parties 3 entities

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

Google Tag Manager 125 kB · 60 ms CPU
Google Analytics 20.9 kB · 19 ms CPU
cloudfront.net 15.9 kB · 0 ms CPU

Page health

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

Main thread work

script evaluation 257 ms
other 136 ms
style layout 84 ms
script parse compile 72 ms
parse HTML 25 ms
paint composite render 12 ms

Axe violations axe-core 4.13.0, full rule set

8 violating nodes across 4 rules, 315 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 image-alt — Images must have alternative text 3 nodes
  • serious link-name — Links must have discernible text 3 nodes
  • serious frame-title — Frames must have an accessible name 1 node
  • serious list — <ul> and <ol> must only directly contain <li>, <script> or <template> elements 1 node

Accessibility failures 4 of 17 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.

  • image-alt — Image elements do not have `[alt]` attributes 3 nodes
  • link-name — Links do not have a discernible name 3 nodes
  • frame-title — `<frame>` or `<iframe>` elements do not have a title 1 node
  • list — Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`). 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 84 1.67 s 0.323 52 ms 175 kB 3/3 ±0 2,587 24s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show ride.netlify.app/latest's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify2-score.js component code into your site! 

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://ride.netlify.app/latest"></speedlify2-score>