[BUG] Slow navigation between dashboard and inventory pages

[priymavani]

🐛 Bug Description

Navigation inside the authenticated app feels noticeably slow, especially when switching from Dashboard to Inventory Management and other internal sections. There is a visible delay before the next page renders, which makes the app feel less responsive than expected.

Steps to Reproduce

1. Log in to FlipTrack.
2. Open the Dashboard.
3. Click Inventory Management or another protected section.
4. Observe the delay during the route change.

Expected Behavior

Route transitions inside the app should feel fast and immediate, with minimal pause between pages.

Actual Behavior

There is a noticeable wait before the destination page appears, particularly on data-heavy pages.

Additional Context

The slowdown seems more pronounced on pages that load auth state plus database data on navigation, such as Dashboard and Inventory Management. It feels like the app is doing a full data refresh on each route change instead of keeping navigation lightweight.

[priymavani]

Hi, I’d like to work on this issue as part of ECSOC 2026. Please assign it to me if it’s available. I’ve reviewed the problem and I’m ready to take it on

[github-actions]

Hi @priymavani! 👋

Thank you for your interest in contributing to this repository! Please wait until a maintainer officially assigns you to this issue before opening a Pull Request.

While you wait, please consider starring ⭐ this repository to show your support! We review requests regularly and will assign it as soon as possible if it's available. Happy coding! 🚀

[karrisanthoshigayatri]

Hi @rushikesh-bobade ,

I'd like to work on this issue as part of ECSOC 2026.

From the issue description, it looks like the slowdown is caused by unnecessary data fetching and auth revalidation during route transitions. My plan is to profile the navigation flow, identify the bottlenecks, and optimize route changes by reducing redundant requests, caching/reusing existing state where appropriate, and improving the loading strategy for data-heavy pages while preserving correctness.

If the issue is available, I'd appreciate being assigned. Thank you!

[rushikesh-bobade]

Hi @priymavani,

Since you opened the issue and your plate is currently clear, I am officially assigning this to you for ECSOC 2026!

@karrisanthoshigayatri - That is an incredibly sharp technical analysis! You hit the nail on the head regarding auth revalidation and redundant requests. Since this issue is assigned, I would love for you to tackle one of our other open performance or architecture issues—your analytical skills are exactly what we need!

Technical hints for @priymavani:
As @karrisanthoshigayatri correctly pointed out, the delay is caused by loaders blocking the route transition. There are two main culprits in our loaders (dashboard.tsx and inventory-management.tsx):

1. Auth Revalidation: We currently use await supabase.auth.getUser() in our loaders, which makes a network request to the Supabase server on every single route change. Investigate if we can optimize this.
2. Heavy DB Queries: The Prisma queries for dashboard metrics block the page from rendering until they finish. Look into React Router's defer API and <Suspense> boundaries to allow the page structure to render instantly while the heavy data streams in in the background.

Let me know if you have any questions while profiling the loaders! Happy optimizing!