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 ·

switowski.com

https://switowski.com/

84 100 100 100 1AXE ✓CWV

Data from Aug 21, 2026, 4:35 PM UTC 2d old

Built Awesome #646 · 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.

Eleventy 1.0.2 Built with Eleventy 1.0.2
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.32 s good
INP — no data
CLS 0 good

Scores

84
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 4.31 s — — 4.31 s 4.31 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.68 s — — 1.68 s 1.68 s
Speed Index 1.68 s — — 1.68 s 1.68 s
TTFB Time to First Byte 469 ms — — 469 ms 469 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 4.31 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 59 ms
resource load duration 36 ms
time to first byte 18 ms
resource load delay 11 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.32 s good 95.1% good
CLS CWV 0 good 100% good
FCP 1.26 s good 93% good
TTFB 1.00 s needs-improvement 61.6% good

Lab vs field

Lab LCP 4.31 s · field p75 1.32 s · real users are 0.31× faster than the lab.

Field history 25 weeks

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

Week ending LCPINPCLSFCPTTFB
2026-08-15 1.25 s — 0 1.21 s 972 ms
2026-08-08 1.32 s — 0 1.23 s 928 ms
2026-08-01 1.37 s — 0 1.31 s 1.00 s
2026-07-25 1.39 s — 0 1.38 s 1.02 s
2026-07-18 1.49 s — 0 1.40 s 1.06 s
2026-07-11 1.67 s — 0 1.61 s 1.07 s
2026-07-04 1.42 s — 0 1.38 s 922 ms
2026-06-27 1.48 s — 0 1.45 s 916 ms
2026-06-20 1.44 s — 0 1.44 s 861 ms
2026-06-13 1.29 s — 0 1.21 s 793 ms
2026-06-06 1.30 s — 0 1.26 s 794 ms
2026-05-30 1.25 s — 0 1.19 s 697 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 737 kB — — 737 kB 737 kB
Requests 17 — — 17 17
Third-party Weight 13.5 kB — — 13.5 kB 13.5 kB
Third-party CPU 5 ms — — 5 ms 5 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

image 652 kB · 6 req
script 44.1 kB · 3 req
document 23.7 kB · 1 req
stylesheet 9.8 kB · 1 req
other 6.5 kB · 6 req
third party 13.5 kB · 4 req

Third parties 2 entities

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

Cloudflare 11.5 kB · 4 ms CPU
switowski.top 2.1 kB · 2 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 385 ms — — 385 ms 385 ms
Long Tasks 0 — — 0 0
DOM Elements 502 — — 502 502
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 154 ms
script evaluation 95 ms
style layout 82 ms
parse HTML 18 ms
script parse compile 18 ms
paint composite render 18 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 704 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 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, 4:35 PM UTC 84 4.31 s 0 0 ms 737 kB 3/3 ±14 2,500 26.6s

Embed this score

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