Performance
Built for fast profile pages
A profile page is often opened from a tap or a scan, on a phone, somewhere with patchy signal. So SwfTap is built to keep that first load short. Here's how, and a speed test you can run yourself.
How it's built
- •Hosted in Sydney, in the same region as its database, so pages aren't waiting on a round trip to another continent.
- •Static files on a global CDN. Scripts, styles and images are served from the Vercel Edge Network close to each visitor.
- •Streamed, server-rendered pages (Next.js), so the page starts arriving before it's finished, and public profiles ship only the code they need.
We'll publish measured figures for the live site here once we've collected enough independent checks to stand behind them.
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 an average across visitors. See the “Independent check” section below for daily-measured lab data.
Independent check: the real deployed site
Checked once a day via Google PageSpeed Insights against the actual live site, not our own CI, and not a number we compute ourselves.
LCP (lab)
2476ms
TTFB (lab)
8ms
Performance score
89/100
Most recent successful check: 1 Nov 2026, 6:00 pm AEDT.