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 ·

eshlox.net

https://eshlox.net/

85 96 100 100 –CWV 24AXE

Data from Aug 20, 2026, 10:28 PM UTC — 20h old.

11ty Emeritus · 1 measurement · since Aug 20, 2026 · last attempt 20h

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.

Astro 7.1.6 Built with Astro 7.1.6
Cloudflare Hosted by Cloudflare

Scores

85
Performance
no change
96
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 2.63 s — — 2.63 s 2.63 s
CLS Cumulative Layout Shift 0.215 — — 0.215 0.215
TBT Total Blocking Time 52 ms — — 52 ms 52 ms
FCP First Contentful Paint 2.00 s — — 2.00 s 2.00 s
Speed Index 2.00 s — — 2.00 s 2.00 s
TTFB Time to First Byte 465 ms — — 465 ms 465 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 121 ms
time to first byte 33 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 220.4 kB — — 220.4 kB 220.4 kB
Requests 16 — — 16 16
Third-party Weight 11.5 kB — — 11.5 kB 11.5 kB
Third-party CPU 15 ms — — 15 ms 15 ms
Unused JS 49.5 kB — — 49.5 kB 49.5 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

script 111.9 kB · 7 req
font 92.6 kB · 3 req
stylesheet 7.8 kB · 1 req
document 7.1 kB · 1 req
other 1.0 kB · 4 req
third party 11.5 kB · 3 req

Third parties 2 entities

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

Cloudflare 11.5 kB · 15 ms CPU
cloudflareinsights.com 36 B · 0 ms CPU

Page health

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

Main thread work

script evaluation 273 ms
other 193 ms
style layout 148 ms
script parse compile 40 ms
paint composite render 17 ms
parse HTML 11 ms

Axe violations axe-core 4.13.0, full rule set

24 violating nodes across 1 rule, 284 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 24 nodes

Accessibility failures 1 of 26 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. 24 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 20, 2026, 10:28 PM UTC 85 2.63 s 0.215 52 ms 220.4 kB 3/3 ±3 2,377 23.9s

Embed this score

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