#Routing too slow
1 messages · Page 1 of 1 (latest)
Hi @abstract oriole. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
Based on the knowledge sources provided, it appears that slow routing and navigation issues have been reported by some users in Next.js 15. Here's a summary of the relevant information:
-
Some users have reported that client-side navigation using the Link component in Next.js 15 is slower compared to previous versions. This issue was mentioned in Github Issue #72383 (https://github.com/vercel/next.js/issues/72383), where users experienced full page reloads (hard navigations) instead of the expected soft navigations when clicking on internal links.
-
In Github Issue #61259 (https://github.com/vercel/next.js/issues/61259), users reported that the App Router in Next.js 14.1.0 (which is a precursor to version 15) was slower than previous versions. This issue might still be present in version 15.
-
The Next.js team is aware of these performance concerns and has been working on optimizations. In Github Issue #48748 (https://github.com/vercel/next.js/issues/48748), it was mentioned that Turbopack for development is now available as a release candidate in Next.js 14.2 and is stable in Next.js 15. Turbopack is designed to improve development performance.
To address slow routing issues in Next.js 15, you could try the following:
-
Ensure you're using the latest patch version of Next.js 15, as performance improvements may have been released.
-
Consider using Turbopack in development mode, which might improve performance.
-
Review your application for potential performance bottlenecks, such as heavy components or unnecessary re-renders.
-
If the issue persists, it would be helpful to create a minimal reproduction of the problem and report it on the Next.js GitHub repository, as the team is actively working on addressing performance concerns.