Performance commitment
Sub-second profile delivery, by design
Every Swftap profile page is engineered to load in under a second, worldwide. This isn't a marketing line — it's a target our own build pipeline checks and can fail on.
The commitment
- •p75 LCP < 800ms — three quarters of real-world visitors see the page's main content finish painting in under 800 milliseconds.
- •TTFB < 200ms — the server starts responding in under 200 milliseconds, on a simulated 4G connection.
- •Globally — delivered via the Vercel Edge Network with Next.js 16 streaming SSR, not a single origin region.
How it's enforced: a Lighthouse CI check runs against a real production build on every single push and pull request, not a one-time benchmark taken at launch and never revisited. The TTFB budget hard-fails the build if it regresses; LCP is measured and logged on every run so any regression is visible immediately, even though the local CI environment can't itself prove the production, edge-cached 800ms figure — that needs real multi-region field data, which is the still-open WebPageTest work noted below.
Live benchmark: your connection, right now
The numbers below aren't canned — they're measured live in your browser, for this exact page load, using the standard Navigation Timing and PerformanceObserver APIs. No external service involved.
Your TTFB, right now
Measuring…
Time from your request to the first byte of this page's response — measured by your browser's own Navigation Timing API.
Your LCP, right now
Measuring…
When this page's largest visible element finished rendering for you — measured by your browser's own PerformanceObserver.
These two numbers are a single real sample of your device and connection loading this page just now — not the p75 global aggregate the commitment above describes. That aggregate is currently proven by our Lighthouse CI gate running on simulated 4G against every deploy; true multi-region field validation (WebPageTest across AU/US/EU) is on the roadmap and not yet wired up.
What's not covered yet
Independent multi-region field validation (WebPageTest across AU/US/EU, testing the real deployed site from outside our own CI) is planned but not yet built — it requires a WebPageTest API key we don't currently have. Everything on this page today is either our own CI-enforced check or a genuine live measurement from your own browser.