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 ·

lunabee.dev

https://lunabee.dev/

99 100 100 100 CWV 1AXE

Data from Aug 21, 2026, 4:38 AM UTC — 14h old.

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

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

Scores

99
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 1.56 s 1.56 s 1.56 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 1.56 s 1.56 s 1.56 s
Speed Index 1.56 s 1.56 s 1.56 s
TTFB Time to First Byte 622 ms 622 ms 622 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 66 ms
time to first byte 23 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 93.4 kB 93.4 kB 93.4 kB
Requests 7 7 7
Third-party Weight 55.7 kB 55.7 kB 55.7 kB
Third-party CPU 20 ms 20 ms 20 ms
Unused JS 0 B 0 B 0 B
Unused CSS 21.3 kB 21.3 kB 21.3 kB

By resource type

script 55.6 kB · 2 req
image 13.9 kB · 2 req
document 3.7 kB · 1 req
stylesheet 603 B · 1 req
third party 55.7 kB · 2 req

Third parties 2 entities

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

Netlify 55.1 kB · 20 ms CPU
Google Fonts 603 B · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 202 ms 202 ms 202 ms
Long Tasks 0 0 0
DOM Elements 48 48 48
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 73 ms
script evaluation 68 ms
style layout 28 ms
script parse compile 21 ms
parse HTML 11 ms
paint composite render 3 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 110 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

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, 4:38 AM UTC 99 1.56 s 0 0 ms 93.4 kB 3/3 ±0 3,006 21.1s

Embed this score

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