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 ·

signalkuppe.com

https://www.signalkuppe.com/

100 100 100 100 1AXE CWV

Data from Aug 21, 2026, 7:33 PM UTC 2d old

11ty Emeritus · 1 measurement · since Aug 21, 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.

Astro 7.2.3 Built with Astro 7.2.3
Netlify Hosted by Netlify

Core Web Vitals field data, origin-level

Real Chrome users, 28-day window (2026-07-23 → 2026-08-19). This is what Google measures you on.

LCP 1.96 s good
INP no data
CLS 0 good

Scores

100
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.21 s 1.21 s 1.21 s
CLS Cumulative Layout Shift 0.001 0.001 0.001
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 942 ms 942 ms 942 ms
Speed Index 942 ms 942 ms 942 ms
TTFB Time to First Byte 611 ms 611 ms 611 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.21 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 50 ms
time to first byte 31 ms

Field data Chrome UX Report, origin-level

Real Chrome users, 28-day trailing window (2026-07-23 → 2026-08-19). This is what Google measures you on.

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.96 s good 85.8% good
CLS CWV 0 good 99.3% good
FCP 1.95 s needs-improvement 72.2% good
TTFB 1.71 s needs-improvement 39.3% good

Lab vs field

Lab LCP 1.21 s · field p75 1.96 s · real users are 1.62× slower than the lab. A gap this wide usually means real users are on slower devices or networks than the simulated ones — the lab number is flattering you.

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
2026-08-01 2.74 s 0 2.46 s
2026-07-25
2026-07-18
2026-07-11
2026-07-04 3.38 s 0 2.72 s 2.21 s
2026-06-27
2026-06-20
2026-06-13
2026-06-06 4.36 s 0 3.22 s 2.59 s
2026-05-30

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 92.7 kB 92.7 kB 92.7 kB
Requests 12 12 12
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

font 40.6 kB · 1 req
other 21.5 kB · 4 req
document 19.8 kB · 1 req
script 8.0 kB · 5 req
stylesheet 2.8 kB · 1 req

Page health

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

Main thread work

other 104 ms
script evaluation 39 ms
style layout 31 ms
parse HTML 12 ms
paint composite render 7 ms
script parse compile 3 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 348 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

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 21, 2026, 7:33 PM UTC 100 1.21 s 0.001 0 ms 92.7 kB 3/3 ±1 2,490 24s

Embed this score

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