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 ·

mac-cursors.netlify.app

https://mac-cursors.netlify.app/

100 84 100 100 –CWV 122AXE

Data from Aug 21, 2026, 3:03 AM UTC — 16h old.

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

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

100
Performance
no change
84
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 954 ms — — 954 ms 954 ms
CLS Cumulative Layout Shift 0.004 — — 0.004 0.004
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 954 ms — — 954 ms 954 ms
Speed Index 954 ms — — 954 ms 954 ms
TTFB Time to First Byte 629 ms — — 629 ms 629 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 35 ms
time to first byte 31 ms

Page weight

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

By resource type

image 90.1 kB · 1 req
document 18.6 kB · 1 req
other 161 B · 1 req

Page health

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

Main thread work

other 116 ms
style layout 67 ms
paint composite render 27 ms
parse HTML 12 ms
script evaluation 10 ms
script parse compile 1 ms

Axe violations axe-core 4.13.0, full rule set

122 violating nodes across 4 rules, 762 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 region — All page content should be contained by landmarks 119 nodes
  • moderate heading-order — Heading levels should only increase by one 1 node
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • serious link-name — Links must have discernible text 1 node

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

  • heading-order — Heading elements are not in a sequentially-descending order 1 node
  • link-name — Links do not have a discernible name 1 node
  • landmark-one-main — Document does not have a main landmark. 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, 3:03 AM UTC 100 954 ms 0.004 0 ms 108.9 kB 3/3 ±0 2,270 23s

Embed this score

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