Vovy times your live app from your Mac, splits the delay into server, database and network, and shows you the one fix worth doing first.
Check my app latency and tell me what's making it slow
How it works
- Time your live URL from Terminal: Vovy runs curl against your homepage and main API route five times and records TTFB, time to first byte, the wait before your server answers at all.
- Record a page load in Chrome: It opens DevTools, reloads with the Network tab recording, and sorts requests by time so the slowest call is on top instead of buried.
- Compare your server and database regions: It checks your Vercel function region and your Supabase project region. A function in Washington talking to a database in Frankfurt adds roughly 100ms to every query.
- Check slow queries in Supabase: Vovy opens the Query Performance report and lists the queries eating the most total time, so you know if the database is the bottleneck.
- Show the latency breakdown: You get a card with a waterfall chart: network, server, database and front end, each in milliseconds, plus the single change that saves the most.
What you provide
- Your live app URL
- Access to your Vercel and Supabase dashboards
What you get
- Real response times from your Mac
- A waterfall showing where time goes
- Region mismatch check
- The top fix, ranked by impact
FAQ
What counts as fast?
Aim for a server response under 200ms and a page that shows its main content in under 2.5 seconds. Anything over a second on an API call is worth fixing.
Will this slow down my app for real users?
No. Vovy sends a handful of normal requests, the same as one visitor clicking around.
Can I move my Supabase region if that's the problem?
Not in place. Supabase regions are set when a project is created, so the easier fix is usually moving your Vercel functions to the matching region in project settings.
Related tasks
All tasks