jeremyswinnen.com
Data from Aug 21, 2026, 1:19 AM UTC — 16h old.
11ty Emeritus · 1 measurement · since Aug 21, 2026 · last attempt 16h
https://kkk.andyvpnc.com/.
Lighthouse follows the redirect, so the numbers below describe the destination page, not this one. Not yet confirmed as a move; it needs to lead to the same place on several consecutive runs first.
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.
Scores
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 9.81 s | — | — | 9.81 s | 9.81 s | |
| CLS Cumulative Layout Shift | 0 | — | — | 0 | 0 | |
| TBT Total Blocking Time | 1.61 s | — | — | 1.61 s | 1.61 s | |
| FCP First Contentful Paint | 6.30 s | — | — | 6.30 s | 6.30 s | |
| Speed Index | 6.30 s | — | — | 6.30 s | 6.30 s | |
| TTFB Time to First Byte | 888 ms | — | — | 888 ms | 888 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.
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 2.42 MB | — | — | 2.42 MB | 2.42 MB | |
| Requests | 121 | — | — | 121 | 121 | |
| Third-party Weight | 13.1 kB | — | — | 13.1 kB | 13.1 kB | |
| Third-party CPU | 10 ms | — | — | 10 ms | 10 ms | |
| Unused JS | 22.4 kB | — | — | 22.4 kB | 22.4 kB | |
| Unused CSS | 53.3 kB | — | — | 53.3 kB | 53.3 kB |
By resource type
Third parties 2 entities
13.1 kB transferred, 10 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.
Page health
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| DOM Elements | 489 | — | — | 489 | 489 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 92 | — | — | 92 | 92 | |
| A11y Failures | 6 | — | — | 6 | 6 | |
| A11y Failing Nodes | 50 | — | — | 50 | 50 |
Axe violations axe-core 4.13.0, full rule set
92 violating nodes across 7 rules, 737 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 70 nodes -
serious
link-in-text-block— Links must be distinguishable without relying on color 10 nodes -
critical
image-alt— Images must have alternative text 4 nodes -
serious
link-name— Links must have discernible text 4 nodes -
moderate
landmark-one-main— Document should have one main landmark 2 nodes -
serious
frame-title— Frames must have an accessible name 1 node -
moderate
heading-order— Heading levels should only increase by one 1 node
Accessibility failures 6 of 13 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.
-
image-alt— Image elements do not have `[alt]` attributes 30 nodes -
color-contrast— Background and foreground colors do not have a sufficient contrast ratio. 16 nodes -
frame-title— `<frame>` or `<iframe>` elements do not have a title 1 node -
html-has-lang— `<html>` element does not have a `[lang]` attribute 1 node -
meta-viewport— `[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5. 1 node -
landmark-one-main— Document does not have a main landmark. 1 node
Hygiene
Changes rarely — which is exactly why a change is worth noticing.
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 | Perf | LCP | CLS | TBT | Weight | Runs | Spread | Bench | Took |
|---|---|---|---|---|---|---|---|---|---|
| Aug 21, 2026, 1:19 AM UTC | 33 | 9.81 s | 0 | 1.61 s | 2.42 MB | 3/3 | ±1 | 2,461 | 60.8s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
jeremyswinnen.com'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://jeremyswinnen.com/"></speedlify-score>