Help - App Router in Next v14.1.0 slower than v13.4.6
Unanswered
Azure Gallinule posted this in #help-forum
Azure GallinuleOP
Hi everyone,
when upgrading one of my projects in v13.4.6 using App Router to latest next v14.1.0, I noticed some serious performance issues when changing routes in production.
I reproduced the issue here:
https://next13-test-teal.vercel.app/ - repo: https://github.com/amavisse/next13-test
https://next14-test-delta.vercel.app/ - repo: https://github.com/amavisse/next14-test
Both projects are exactly the same except different Next versions
In the first one, everything is going smoothly, while the second upgraded one is very slow when changing routes
Inspecting the dev console, inside the network tab, you can see the routes are correctly pre-fetched but when moving to the route, it's fetching it again, making it extremely slower.
Any idea why? Am I doing anything wrong? Any recommendations?
I'm open to all kinds of feedback
Thank you for your time
when upgrading one of my projects in v13.4.6 using App Router to latest next v14.1.0, I noticed some serious performance issues when changing routes in production.
I reproduced the issue here:
https://next13-test-teal.vercel.app/ - repo: https://github.com/amavisse/next13-test
https://next14-test-delta.vercel.app/ - repo: https://github.com/amavisse/next14-test
Both projects are exactly the same except different Next versions
In the first one, everything is going smoothly, while the second upgraded one is very slow when changing routes
Inspecting the dev console, inside the network tab, you can see the routes are correctly pre-fetched but when moving to the route, it's fetching it again, making it extremely slower.
Any idea why? Am I doing anything wrong? Any recommendations?
I'm open to all kinds of feedback
Thank you for your time
4 Replies
Toyger
probably a bug, it for some reason it use different RSC id, to fetch other pages, even it prefetched with different one.
@Toyger probably a bug, it for some reason it use different RSC id, to fetch other pages, even it prefetched with different one.
Azure GallinuleOP
so nothing i can do about it? i can only wait for a patch or not use newer version of next?
@Azure Gallinule so nothing i can do about it? i can only wait for a patch or not use newer version of next?
Toyger
you better create new issue at nextjs repo https://github.com/vercel/next.js/issues with problem description.
Azure GallinuleOP
thanks will try that