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 ·

fumes.junglestar.org

https://fumes.junglestar.org/

99 100 100 100 0AXE CWV

Data from Aug 20, 2026, 10:28 PM UTC 3d old

Built Awesome #155 · 1 measurement · since Aug 20, 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.

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.84 s 1.84 s 1.84 s
CLS Cumulative Layout Shift 0.040 0.040 0.040
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 989 ms 989 ms 989 ms
Speed Index 989 ms 989 ms 989 ms
TTFB Time to First Byte 605 ms 605 ms 605 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 1.84 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 64 ms
time to first byte 6 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 244 kB 244 kB 244 kB
Requests 16 16 16
Third-party Weight 200 kB 200 kB 200 kB
Third-party CPU 14 ms 14 ms 14 ms
Unused JS 0 B 0 B 0 B
Unused CSS 0 B 0 B 0 B

By resource type

image 182 kB · 10 req
document 35.8 kB · 1 req
script 17.9 kB · 2 req
other 8.1 kB · 3 req
third party 200 kB · 12 req

Third parties 3 entities

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

cloudfront.net 182 kB · 0 ms CPU
Google/Doubleclick Ads 17.3 kB · 4 ms CPU
Google Analytics 667 B · 9 ms CPU

Page health

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

Main thread work

other 123 ms
style layout 81 ms
script evaluation 73 ms
parse HTML 22 ms
paint composite render 21 ms
script parse compile 8 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 2000 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.

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, 10:28 PM UTC 99 1.84 s 0.040 0 ms 244 kB 3/3 ±2 2,319 29s

Embed this score

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