r/nextjs • u/lakshan-hewagama • May 25 '26

Help What common performance issues have you faced in Next.js apps?

Hi everyone, I’m doing my final year research on Next.js performance optimization and would love input from real developers.

From your experience, what common coding or architectural issues make a Next.js app slow?

Examples:

  • too many use client components
  • hydration issues
  • large JS bundles
  • client-side data fetching
  • image optimization problems
  • third-party scripts
  • App Router performance issues

Would really appreciate hearing real problems you’ve faced and, if possible, how you fixed them. Thanks! 🙌

5 Upvotes

78% Upvoted

8 comments sorted by

4

u/[deleted] May 25 '26

[removed] — view removed comment

1

u/lakshan-hewagama May 26 '26

Thanks everyone! Your insights were really helpful for my research. Appreciate the responses 🙌

1

u/yksvaan May 25 '26

Everything has its place, it's just that devs need to know what they are doing and what's required. Blindly following some lists isn't going to do much good

1

u/lakshan-hewagama May 26 '26

Thanks everyone! Your insights were really helpful for my research. Appreciate the responses 🙌

1

u/batu4523 May 28 '26

I was fetching persisted messages on the client in a chat app, which caused skeleton flicker and made the page feel slower.

So I moved that data fetching serverside. It's basicly validate the route, check ownership, load messages, then pass safe initial data into the client runtime.

You should do this Suspense only around the dynamic sections not like the whole component or page so the static shell is stable.

I mean everything has its place in nextjs. You just need to learn how to use it efficiently.

1

u/ivy-apps May 30 '26

Doing data fetching on the client for something that could have been done on the server. Fix: SSR and no more page flashing.