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 ·

byteaether.github.io

https://byteaether.github.io/

99 93 100 100 –CWV 2AXE

Data from Aug 20, 2026, 7:33 PM UTC — 23h old.

Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 23h

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
GitHub Pages Hosted by GitHub Pages

Scores

99
Performance
no change
93
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 903 ms — — 903 ms 903 ms
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 108 ms — — 108 ms 108 ms
FCP First Contentful Paint 786 ms — — 786 ms 786 ms
Speed Index 786 ms — — 786 ms 786 ms
TTFB Time to First Byte 603 ms — — 603 ms 603 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 49 ms
time to first byte 4 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 266.3 kB — — 266.3 kB 266.3 kB
Requests 13 — — 13 13
Third-party Weight 171.8 kB — — 171.8 kB 171.8 kB
Third-party CPU 54 ms — — 54 ms 54 ms
Unused JS 72.8 kB — — 72.8 kB 72.8 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

script 174.0 kB · 2 req
image 75.2 kB · 5 req
document 7.8 kB · 1 req
stylesheet 3.2 kB · 2 req
other 2.1 kB · 2 req
third party 262.2 kB · 12 req

Third parties 1 entities

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

Google Tag Manager 171.8 kB · 54 ms CPU

Page health

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

Main thread work

script evaluation 194 ms
other 108 ms
script parse compile 46 ms
style layout 42 ms
paint composite render 13 ms
parse HTML 10 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 2 rules, 584 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 landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node
  • serious link-in-text-block — Links must be distinguishable without relying on color 1 node

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

  • link-in-text-block — Links rely on color to be distinguishable. 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 20, 2026, 7:33 PM UTC 99 903 ms 0 108 ms 266.3 kB 3/3 ±0 2,311 23s

Embed this score

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