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 ·

lucas.computer

https://www.lucas.computer/

100 94 100 100 –CWV 10AXE

Data from Aug 21, 2026, 6:45 PM UTC — 27m old.

Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 27m

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.

Self-hosted · nginx Hosted by Self-hosted

Scores

100
Performance
no change
94
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.72 s — — 1.72 s 1.72 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 895 ms — — 895 ms 895 ms
Speed Index 895 ms — — 895 ms 895 ms
TTFB Time to First Byte 695 ms — — 695 ms 695 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 143 ms
time to first byte 96 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 142.1 kB — — 142.1 kB 142.1 kB
Requests 21 — — 21 21
Third-party Weight 18.7 kB — — 18.7 kB 18.7 kB
Third-party CPU 2 ms — — 2 ms 2 ms
Unused JS 21.8 kB — — 21.8 kB 21.8 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

font 80.1 kB · 2 req
script 35.3 kB · 2 req
image 15.2 kB · 10 req
document 8.2 kB · 1 req
other 2.2 kB · 5 req
media 1.1 kB · 1 req
third party 18.7 kB · 13 req

Third parties 1 entities

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

ilotreseau.net 18.7 kB · 2 ms CPU

Page health

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

Main thread work

other 145 ms
style layout 64 ms
script evaluation 57 ms
paint composite render 20 ms
script parse compile 15 ms
parse HTML 14 ms

Axe violations axe-core 4.13.0, full rule set

10 violating nodes across 1 rule, 269 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 10 nodes

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

  • target-size — Touch targets do not have sufficient size or spacing. 4 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, 6:45 PM UTC 100 1.72 s 0 0 ms 142.1 kB 3/3 ±0 2,341 23.7s

Embed this score

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