Skip to content

How fast is your website, really?

Enter a URL and we load your page in a real browser, up to eight times: three cold runs each on emulated mobile and desktop, plus a repeat visit per profile. You get Core Web Vitals, page weight, third-party cost, and the fixes, worst first.

Loads the page up to eight times in a real browser; slow pages shorten the run budget. Usually 30 to 60 seconds. Nothing stored.

What this measures

Real browser, real loads

No estimates: headless Chromium loads your page cold, three runs per profile, and the report shows the median.

Core Web Vitals

LCP, CLS, and total blocking time, measured the way Google defines them, against the official thresholds.

Mobile and desktop

Mobile runs on an emulated 9 Mbit/s connection with a 4× slower CPU, because that is where pages actually fail.

Where the bytes go

Page weight, request count, and which third-party scripts cost the most, plus the concrete fix for each finding.

Slow pages lose leads

We fix performance at the source: caching and server setup, image pipelines, third-party cleanup, and frontends that pass Core Web Vitals.

Contact

What eats your team's time?

Two or three sentences are enough. Philipp reads every message himself and usually replies within two business days.

Philipp Kant

Philipp Kant
Software & AI Architect, Krefeld

What is it about?

Opens your email app with the message to philipp@kant.dev, ready to send. You see everything before it goes out. Privacy policy

  • No sales call unless you ask for one.
  • No newsletter, no automated follow-ups.
  • Your message goes to one inbox: philipp@kant.dev.

Rather talk? Pick a 30-minute slot

Or write directly: philipp@kant.dev