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 ·

valinor.earth

https://valinor.earth/

78 96 100 92 3AXE CWV

Data from Aug 21, 2026, 9:48 AM UTC 2d old

11ty Emeritus · 1 measurement · since Aug 21, 2026

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.

GitHub Pages Hosted by GitHub Pages

Scores

78
Performance
no change
96
Accessibility
no change
100
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 5.65 s 5.65 s 5.65 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 79 ms 79 ms 79 ms
FCP First Contentful Paint 1.52 s 1.52 s 1.52 s
Speed Index 1.52 s 1.52 s 1.52 s
TTFB Time to First Byte 460 ms 460 ms 460 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 5.65 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 92 ms
time to first byte 14 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 925 kB 925 kB 925 kB
Requests 15 15 15
Third-party Weight 124 kB 124 kB 124 kB
Third-party CPU 51 ms 51 ms 51 ms
Unused JS 71.6 kB 71.6 kB 71.6 kB
Unused CSS 0 B 0 B 0 B

By resource type

image 787 kB · 6 req
script 124 kB · 4 req
document 5.6 kB · 1 req
stylesheet 4.3 kB · 1 req
other 735 B · 2 req
third party 124 kB · 5 req

Third parties 2 entities

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

posthog.com 112 kB · 48 ms CPU
Cloudflare 11.5 kB · 3 ms CPU

Page health

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

Main thread work

other 218 ms
script evaluation 216 ms
style layout 49 ms
script parse compile 33 ms
paint composite render 13 ms
parse HTML 9 ms

Axe violations axe-core 4.13.0, full rule set

3 violating nodes across 1 rule, 245 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.

  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 3 nodes

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

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 3 nodes

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, 9:48 AM UTC 78 5.65 s 0 79 ms 925 kB 3/3 ±5 2,485 26.8s

Embed this score

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