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 ·

beeps.website

https://beeps.website/

100 96 100 100 –CWV 33AXE

Data from Aug 20, 2026, 4:39 PM UTC — 26h old.

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

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.6 Built with Eleventy 3.1.6
Self-hosted · nginx Hosted by Self-hosted

Core Web Vitals field data, origin-level

Real Chrome users, 28-day window (2026-07-19 → 2026-08-15). From the backfilled CrUX history rather than this measurement, which predates the API key. This is what Google measures you on.

LCP — no data
INP — no data
CLS — no data

Scores

100
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 1.46 s — — 1.46 s 1.46 s
CLS Cumulative Layout Shift 0.024 — — 0.024 0.024
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 994 ms — — 994 ms 994 ms
Speed Index 1.39 s — — 1.39 s 1.39 s
TTFB Time to First Byte 694 ms — — 694 ms 694 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.

resource load duration 288 ms
time to first byte 95 ms
element render delay 31 ms
resource load delay 12 ms

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-15 — — — — —
2026-08-08 917 ms — 0 837 ms 677 ms
2026-08-01 1.02 s 53 ms 0 930 ms 684 ms
2026-07-25 976 ms 57 ms 0 925 ms 685 ms
2026-07-18 1.01 s 60 ms 0 930 ms 685 ms
2026-07-11 — — — — —
2026-07-04 — — — — —
2026-06-27 — — — — —
2026-06-20 — — — — —
2026-06-13 — — — — —
2026-06-06 — — — — —
2026-05-30 — — — — —

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 461.1 kB — — 461.1 kB 461.1 kB
Requests 35 — — 35 35
Third-party Weight 0 B — — 0 B 0 B
Third-party CPU 0 ms — — 0 ms 0 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

image 257.9 kB · 16 req
font 170.8 kB · 1 req
stylesheet 16.9 kB · 12 req
document 8.9 kB · 1 req
script 3.8 kB · 3 req
other 2.8 kB · 2 req

Page health

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

Main thread work

other 218 ms
style layout 105 ms
script evaluation 34 ms
paint composite render 31 ms
parse HTML 26 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

33 violating nodes across 1 rule, 535 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 33 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. 38 nodes

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, 4:39 PM UTC 100 1.46 s 0.024 0 ms 461.1 kB 3/3 ±5 2,466 24.9s

Embed this score

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