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 ·

reduxflakes.nekoweb.org

https://reduxflakes.nekoweb.org/

63 100 96 100 CWV 7AXE

Data from Aug 21, 2026, 6:46 AM UTC — 12h old.

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

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 4.0.0 Built with Eleventy 4.0.0
Cloudflare Hosted by Cloudflare

Scores

63
Performance
no change
100
Accessibility
no change
96
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 10.85 s 10.85 s 10.85 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 13 ms 13 ms 13 ms
FCP First Contentful Paint 4.10 s 4.10 s 4.10 s
Speed Index 5.07 s 5.07 s 5.07 s
TTFB Time to First Byte 659 ms 659 ms 659 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 1.45 s
resource load delay 652 ms
resource load duration 220 ms
time to first byte 32 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.44 MB 1.44 MB 1.44 MB
Requests 55 55 55
Third-party Weight 58.6 kB 58.6 kB 58.6 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 1.10 MB · 30 req
font 278.5 kB · 5 req
document 30.3 kB · 5 req
script 24.0 kB · 6 req
stylesheet 7.2 kB · 1 req
other 4.2 kB · 7 req
third party 84.3 kB · 22 req

Third parties 13 entities

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

gwenbnuuy.moe 28.6 kB · 0 ms CPU
Fastly 5.1 kB · 0 ms CPU
keepandroidopen.org 4.8 kB · 4 ms CPU
zgo.at 4.5 kB · 2 ms CPU
ioxtv.co 4.2 kB · 0 ms CPU

Page health

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

Main thread work

other 608 ms
style layout 253 ms
paint composite render 222 ms
script evaluation 64 ms
parse HTML 46 ms
script parse compile 8 ms

Axe violations axe-core 4.13.0, full rule set

7 violating nodes across 4 rules, 1052 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 region — All page content should be contained by landmarks 3 nodes
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 2 nodes
  • moderate landmark-no-duplicate-banner — Document should not have more than one banner landmark 1 node
  • serious link-name — Links must have discernible text 1 node

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, 6:46 AM UTC 63 10.85 s 0 13 ms 1.44 MB 3/3 ±7 2,602 50.3s

Embed this score

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