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 ·

spacebook.app

https://spacebook.app/

100 96 100 92 CWV 4AXE

Data from Aug 21, 2026, 7:48 AM UTC — 11h old.

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

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
100
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 806 ms 806 ms 806 ms
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 806 ms 806 ms 806 ms
Speed Index 806 ms 806 ms 806 ms
TTFB Time to First Byte 628 ms 628 ms 628 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 59 ms
time to first byte 30 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 62.6 kB 62.6 kB 62.6 kB
Requests 5 5 5
Third-party Weight 7.7 kB 7.7 kB 7.7 kB
Third-party CPU 1 ms 1 ms 1 ms
Unused JS 0 B 0 B 0 B
Unused CSS 0 B 0 B 0 B

By resource type

other 40.8 kB · 1 req
stylesheet 7.1 kB · 1 req
document 7.0 kB · 1 req
script 5.6 kB · 1 req
image 2.1 kB · 1 req
third party 7.7 kB · 2 req

Third parties 2 entities

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

Cloudflare CDN 5.6 kB · 1 ms CPU
Netlify 2.1 kB · 0 ms CPU

Page health

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

Main thread work

other 112 ms
style layout 51 ms
script evaluation 16 ms
paint composite render 11 ms
parse HTML 7 ms
script parse compile 3 ms

Axe violations axe-core 4.13.0, full rule set

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

  • serious aria-prohibited-attr — Elements must only use permitted ARIA attributes 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
  • serious scrollable-region-focusable — Scrollable region must have keyboard access 1 node

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

  • aria-prohibited-attr — Elements use prohibited ARIA attributes 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, 7:48 AM UTC 100 806 ms 0 0 ms 62.6 kB 3/3 ±1 4,293 20.8s

Embed this score

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