Vercel`s first load is heavier than local

[jaaja321]

Summary

Local build

Vercel build

I wonder if i can reduce its size because its like two times more than local
or im hoping that it will not disrupt performance that much

Additional information

No response

Example

No response

[marcusvramos]

The ~110kB difference you're seeing is likely coming from one of these sources:

Most common causes:

1. Vercel Analytics/Speed Insights - If enabled in your project settings, these add significant JS to the bundle (~45-60kB combined)
2. Environment-specific code - Different NEXT_PUBLIC_* env vars between local and Vercel can cause different code paths to be bundled
3. Source maps - Check if Vercel is including source maps in production (shouldn't, but worth checking)

Quick fixes to try:

1. Disable Vercel Analytics/Speed Insights temporarily in your project settings to see if that's the culprit
2. Make sure your local build uses the same env vars as Vercel: NEXT_PUBLIC_VERCEL_ENV=production npm run build
3. Check your next.config.js for any production-only configurations

To debug further:
Run this locally and compare with Vercel's build output:

NODE_ENV=production npm run build

The bundle analyzer can also help identify what's adding the extra weight:

npm install @next/bundle-analyzer

Can you share your next.config.js? That would help pinpoint the issue.

[jaaja321]

Thanks for the fast response and i solved it.It was coming from Sentry(service for monitoring errors) initializer.I made it load dynamic when code needs it and so it gone

Thanks