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 ·

wearedeepspace.com

https://www.wearedeepspace.com/

62 91 100 100 AXE CWV

Data from Aug 21, 2026, 12:48 PM UTC 2d old

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

Scores

62
Performance
no change
91
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 2.29 s 2.29 s 2.29 s
CLS Cumulative Layout Shift 0.056 0.056 0.056
TBT Total Blocking Time 1.24 s 1.24 s 1.24 s
FCP First Contentful Paint 1.86 s 1.86 s 1.86 s
Speed Index 18.86 s 18.86 s 18.86 s
TTFB Time to First Byte 637 ms 637 ms 637 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 2.29 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 163 ms
time to first byte 38 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 5.06 MB 5.06 MB 5.06 MB
Requests 58 58 58
Third-party Weight 704 kB 704 kB 704 kB
Third-party CPU 2.06 s 2.06 s 2.06 s
Unused JS 321 kB 321 kB 321 kB
Unused CSS 40.0 kB 40.0 kB 40.0 kB

By resource type

image 4.07 MB · 26 req
script 578 kB · 14 req
font 272 kB · 4 req
stylesheet 91.3 kB · 7 req
document 47.5 kB · 3 req
other 330 B · 4 req
third party 777 kB · 26 req

Third parties 8 entities

704 kB transferred, 2.06 s of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

Google CDN 320 kB · 171 ms CPU
saassurf.com 185 kB · 0 ms CPU
Cloudflare CDN 128 kB · 24 ms CPU
Google Fonts 36.3 kB · 0 ms CPU
Unpkg 17.5 kB · 2 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 178.85 s 178.85 s 178.85 s
Long Tasks 20 20 20
DOM Elements 1,062 1,062 1,062
A11y Failures 2 2 2
A11y Failing Nodes 4 4 4

Main thread work

other 149.05 s
script evaluation 15.11 s
style layout 8.31 s
paint composite render 5.86 s
garbage collection 291 ms
script parse compile 188 ms
parse HTML 58 ms

Axe violations axe-core , full rule set

The axe run failed: Navigation timeout of 120000 ms exceeded

Accessibility failures 2 of 16 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 2 nodes
  • link-name — Links do not have a discernible name 2 nodes

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, 12:48 PM UTC 62 2.29 s 0.056 1.24 s 5.06 MB 3/3 ±22 2,413 368.4s

Embed this score

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