nextjs - ๐Ÿ’ก(How to fix) Fix Turbopack slow [1 comments, 2 participants]

Official PRs (โ€ฆ)
ON THIS PAGE

Recommended Tools

ร—6

Utilities matched from this issueโ€™s tags and category โ€” try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful ยท Quick feedback

Loadingโ€ฆ
GitHub stats
vercel/next.js#86706โ€ขFetched 2026-04-08 02:09:41
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ร—2closed ร—1commented ร—1issue_type_added ร—1

Code Example

Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 21.6.0: Mon Jun 24 00:56:10 PDT 2024; root:xnu-8020.240.18.709.2~1/RELEASE_X86_64
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 22.14.0
  npm: 11.4.1
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 16.0.6
  eslint-config-next: N/A
  react: 19.2.0
  react-dom: 19.2.0
  typescript: 5.9.3
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://i-cant-create-reproduction-works-fine-on-small-project.com

To Reproduce

  1. Upgrade from Next.js 15 to 16
  2. Build
  3. Run

Current vs. Expected behavior

What is happening

  1. Open app
  2. Load first page - fast
  3. Click on link to go to another page - 5/6 seconds delay
  4. Click on link to go to 3rd page - 5/6 - seconds delay
  5. Click on link to go to 4th page - fast from this moment on

What should be happening

  1. Open app and pages load lightning fast

So after I upgraded to nextjs 16, I can see turbopack is enabled by default, but docker image went from 2 GB to 1.3 but in production the first few pages, until caching is done are super slow. Like waiting for 5/6 sometimes 10 seconds. Then it goes on and works fast

And it happens only if I go to a page via next/router. If I open via url it opens instantly again.

There are no network requests, simply it lags.

Provide environment information

Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 21.6.0: Mon Jun 24 00:56:10 PDT 2024; root:xnu-8020.240.18.709.2~1/RELEASE_X86_64
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 22.14.0
  npm: 11.4.1
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 16.0.6
  eslint-config-next: N/A
  react: 19.2.0
  react-dom: 19.2.0
  typescript: 5.9.3

Which area(s) are affected? (Select all that apply)

Redirects

Which stage(s) are affected? (Select all that apply)

next build (local), Other (Deployed)

Additional context

No response

extent analysis

TL;DR

  • The most likely fix is to configure or disable Turbopack, which is enabled by default in Next.js 16, to improve page loading performance.

Guidance

  • Verify that the issue is indeed related to Turbopack by checking the Next.js documentation for any known issues or configuration options that can be adjusted for better performance.
  • Investigate the next.config.js file for any Turbopack-related settings that can be tweaked to improve page loading times.
  • Test loading pages directly via URL instead of using next/router to see if the issue persists, as the problem seems to be specific to router-based navigation.
  • Consider temporarily disabling Turbopack to see if page loading performance returns to normal, which can help confirm if Turbopack is the root cause.

Example

No specific code example is provided due to the lack of detailed code context in the issue.

Notes

  • The issue seems to be related to the upgrade from Next.js 15 to 16 and the default enablement of Turbopack, but without more specific details about the project's configuration and code, it's challenging to provide a precise solution.
  • The performance issue is inconsistent, affecting only the first few pages loaded via next/router, which suggests a potential caching or initialization issue with Turbopack.

Recommendation

  • Apply workaround: Temporarily disable Turbopack or adjust its configuration to mitigate the performance issue until a more permanent solution or fix is available from Next.js.

Vote matrix ยท Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loadingโ€ฆ

Still need to ship something?

ร—6

Another batch ranked right after the header list โ€” different links, same matching logic.

Back to top recommendations

TRENDING

nextjs - ๐Ÿ’ก(How to fix) Fix Turbopack slow [1 comments, 2 participants]