Next.js app deployed on Vercel runs terribly slow
Unanswered
Black and yellow mud dauber posted this in #help-forum
Black and yellow mud dauberOP
https://neatreads.vercel.app/
https://github.com/mgrabka/neatreads
Could someone help me identify the issue behind my app taking 5 seconds every page to load? It's deployed on the free hobby plan, I don't think it changes much tho?
I'd really appreciate your help ðŸ™
https://github.com/mgrabka/neatreads
Could someone help me identify the issue behind my app taking 5 seconds every page to load? It's deployed on the free hobby plan, I don't think it changes much tho?
I'd really appreciate your help ðŸ™
16 Replies
Black and yellow mud dauberOP

When building the app, it should show a distribution of stuff like first load js
Check that out if its big, also the files like assets may be too large, meaning they take longer to load.
Also not sure how your assets are hosted
@Clown When building the app, it should show a distribution of stuff like first load js
Black and yellow mud dauberOP
That looks good to me
Also its loading quite fast for me rn
@Clown Also its loading quite fast for me rn
Black and yellow mud dauberOP
Yes, it is definitely better, even in when comparing pure numbers from Lighthouse
Another guy actually reported this btw, so it could be a vercel side thing
Or maybe thats just how it is and i dont notice it
Cause it works quite well after warm up
@Clown Another guy actually reported this btw, so it could be a vercel side thing
Black and yellow mud dauberOP
I kind of hope it is, it would be a bit of a shame if my code was so bad to the point pages load 4 (now 2 fortunately) seconds ðŸ«
It's definitely a little bit slow. I wonder if it's something to do with the way you have your (home) group set up? It's also preventing the route from being cached
@Marchy It's definitely a little bit slow. I wonder if it's something to do with the way you have your (home) group set up? It's also preventing the route from being cached
Black and yellow mud dauberOP
Is there a better way to do it though? I didn't want my auth screens to inherit the layout that's made for core app
@Black and yellow mud dauber Is there a better way to do it though? I didn't want my auth screens to inherit the layout that's made for core app
That means you’ll need to shift your layout down the route segment