After reviewing many Next.js codebases, I keep seeing the same performance killers. Most of the t...After reviewing many Next.js codebases, I keep seeing the same performance killers. Most of the t...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Daniil's avatar
Daniil Novikov
pro
• Dec 23
After reviewing many Next.js codebases, I keep seeing the same performance killers.
Most of the time it’s not the framework. It’s small choices that add up.
Common mistakes too
many client components instead of server components
large images without proper sizing or lazy loading
heavy data fetching on the client
no caching or revalidation strategy
too many third party scripts on first load
no pagination or virtualization for long lists
Each issue looks minor alone. Together they cause slow pages, higher bounce rate and poor mobile experience.
When I optimize a Next.js app, I start simple. Reduce client JavaScript, fix images, move data fetching to the server, then measure again.
What’s the biggest performance issue you’ve seen in a Next.js project?
Post image
Kristina's avatar
Kristina Kyrychenko
• Dec 23
Absolutely. It’s often the small decisions that quietly kill performance. Reducing client JS, optimizing images, and moving data fetching server-side usually makes the biggest impact. Those little fixes really add up.
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started