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 ·

supermaya-demo.netlify.app

https://supermaya-demo.netlify.app/

100 96 96 100 –CWV 3AXE

Data from Aug 21, 2026, 8:46 AM UTC — 10h old.

Build Awesome Starters · 1 measurement · since Aug 21, 2026 · last attempt 10h

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
96
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 802 ms — — 802 ms 802 ms
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 802 ms — — 802 ms 802 ms
Speed Index 802 ms — — 802 ms 802 ms
TTFB Time to First Byte 621 ms — — 621 ms 621 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 74 ms
time to first byte 23 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 12.8 kB — — 12.8 kB 12.8 kB
Requests 13 — — 13 13
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

script 6.9 kB · 4 req
stylesheet 2.7 kB · 2 req
document 2.3 kB · 1 req
other 960 B · 6 req

Page health

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

Main thread work

other 84 ms
style layout 30 ms
script evaluation 23 ms
parse HTML 15 ms
paint composite render 6 ms
script parse compile 4 ms

Axe violations axe-core 4.13.0, full rule set

3 violating nodes across 3 rules, 182 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 landmark-contentinfo-is-top-level — Contentinfo landmark should not be contained in another landmark 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node
  • serious link-name — Links must have discernible text 1 node

Accessibility failures 1 of 23 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.

  • link-name — Links do not have a discernible name 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 4 console errors

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, 8:46 AM UTC 100 802 ms 0 0 ms 12.8 kB 3/3 ±0 2,493 22s

Embed this score

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