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 ·

rsixersdonates.com

https://rsixersdonates.com/

97 90 100 100 CWV 9AXE

Data from Aug 21, 2026, 6:52 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.

Eleventy Built with Eleventy
Netlify Hosted by Netlify

Scores

97
Performance
no change
90
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 1.56 s 1.56 s 1.56 s
CLS Cumulative Layout Shift 0.092 0.092 0.092
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 1.56 s 1.56 s 1.56 s
Speed Index 1.56 s 1.56 s 1.56 s
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 90 ms
time to first byte 23 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.54 MB 1.54 MB 1.54 MB
Requests 16 16 16
Third-party Weight 30.2 kB 30.2 kB 30.2 kB
Third-party CPU 0 ms 0 ms 0 ms
Unused JS 0 B 0 B 0 B
Unused CSS 39.3 kB 39.3 kB 39.3 kB

By resource type

media 1.30 MB · 2 req
font 112.7 kB · 4 req
image 83.8 kB · 2 req
stylesheet 42.9 kB · 4 req
script 3.1 kB · 2 req
document 2.4 kB · 1 req
other 70 B · 1 req
third party 30.2 kB · 3 req

Third parties 1 entities

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

Google Fonts 30.2 kB · 0 ms CPU

Page health

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

Main thread work

other 299 ms
style layout 193 ms
paint composite render 105 ms
script evaluation 63 ms
parse HTML 45 ms
script parse compile 3 ms

Axe violations axe-core 4.13.0, full rule set

9 violating nodes across 4 rules, 120 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 6 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 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 2 of 15 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
  • 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, 6:52 AM UTC 97 1.56 s 0.092 0 ms 1.54 MB 3/3 ±1 2,603 23.9s

Embed this score

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