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 ·

roboleary.net

https://www.roboleary.net/

95 100 96 69 CWV 1AXE

Data from Aug 21, 2026, 6:39 PM UTC — 34m old.

Built Awesome · 2 measurements · since Aug 21, 2026 · last attempt 34m

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
Cloudflare Hosted by Cloudflare

Scores

95
Performance
no change
100
Accessibility
no change
96
Best Practices
no change
69
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.57 s 2.57 s 2.57 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 2.13 s 2.13 s 2.13 s
Speed Index 2.13 s 2.13 s 2.13 s
TTFB Time to First Byte 618 ms 618 ms 618 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.

resource load delay 51 ms
element render delay 51 ms
time to first byte 39 ms
resource load duration 16 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 254.4 kB 254.4 kB 254.4 kB
Requests 15 15 15
Third-party Weight 48.0 kB 48.0 kB 48.0 kB
Third-party CPU 20 ms 20 ms 20 ms
Unused JS 0 B 0 B 0 B
Unused CSS 0 B 0 B 0 B

By resource type

image 95.0 kB · 5 req
document 49.6 kB · 1 req
script 49.4 kB · 3 req
font 43.9 kB · 1 req
other 11.6 kB · 3 req
stylesheet 4.8 kB · 2 req
third party 48.0 kB · 2 req

Third parties 1 entities

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

JSDelivr CDN 48.0 kB · 20 ms CPU

Page health

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

Main thread work

other 304 ms
paint composite render 184 ms
script evaluation 148 ms
style layout 123 ms
parse HTML 20 ms
script parse compile 14 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 365 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 page-has-heading-one — Page should contain a level-one heading 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, 6:39 PM UTC 95 2.57 s 0 0 ms 254.4 kB 3/3 ±1 2,415 23.3s
Aug 21, 2026, 11:34 AM UTC TRACING_ALREADY_STARTED: An internal Chrome error occurred. Please restart Chrome and try re-running Lighthouse. 20.1s

Embed this score

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