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 ·

oisin.io

https://oisin.io/

91 100 100 100 CWV 0AXE

Data from Aug 21, 2026, 5:35 AM UTC — 13h old.

Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 13h

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 3.1.2 Built with Eleventy 3.1.2
Netlify Hosted by Netlify

Scores

91
Performance
no change
100
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 3.01 s 3.01 s 3.01 s
CLS Cumulative Layout Shift 0.001 0.001 0.001
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 2.46 s 2.46 s 2.46 s
Speed Index 2.46 s 2.46 s 2.46 s
TTFB Time to First Byte 493 ms 493 ms 493 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 duration 56 ms
element render delay 43 ms
time to first byte 39 ms
resource load delay 12 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 394.4 kB 394.4 kB 394.4 kB
Requests 32 32 32
Third-party Weight 73.8 kB 73.8 kB 73.8 kB
Third-party CPU 7 ms 7 ms 7 ms
Unused JS 0 B 0 B 0 B
Unused CSS 0 B 0 B 0 B

By resource type

image 268.9 kB · 15 req
font 77.8 kB · 5 req
script 29.3 kB · 4 req
stylesheet 7.7 kB · 3 req
document 6.0 kB · 1 req
other 541 B · 3 req
third party 73.9 kB · 9 req

Third parties 3 entities

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

Google Fonts 45.5 kB · 0 ms CPU
Unpkg 16.8 kB · 3 ms CPU
Cloudflare 11.5 kB · 4 ms CPU

Page health

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

Main thread work

other 206 ms
style layout 83 ms
script evaluation 78 ms
paint composite render 27 ms
parse HTML 14 ms
script parse compile 8 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 267 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.

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h3

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, 5:35 AM UTC 91 3.01 s 0.001 0 ms 394.4 kB 3/3 ±9 2,471 24.5s

Embed this score

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