nextjs - 💡(How to fix) Fix Server requests and latency increased after upgrading from Next.js 15 to 16 [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#85469Fetched 2026-04-08 02:15:35
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×2closed ×1commented ×1issue_type_added ×1

Fix Action

Fix / Workaround

Upgrade to Next.js version 16

Code Example

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.0.0: Wed Sep 17 21:41:45 PDT 2025; root:xnu-12377.1.9~141/RELEASE_ARM64_T6000
  Available memory (MB): 65536
  Available CPU cores: 10
Binaries:
  Node: 24.10.0
  npm: 11.6.1
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  next: 15.5.5 // An outdated version detected (latest is 16.0.0), upgrade is highly recommended!
  eslint-config-next: N/A
  react: 19.1.1
  react-dom: 19.1.1
  typescript: 5.9.3
Next.js Config:
  output: N/A
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

N/A

To Reproduce

Upgrade to Next.js version 16

Current vs. Expected behavior

After upgrading from Next.js 15 to Next.js 16, I noticed that the number of requests effectively doubled. This has resulted in increased server strain and higher response latency. It also seems to require more resources and therefore higher server costs $$$ (good for Vercel?) compared to v15.

Server request patterns and performance should remain consistent (or improve) after upgrading.

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.0.0: Wed Sep 17 21:41:45 PDT 2025; root:xnu-12377.1.9~141/RELEASE_ARM64_T6000
  Available memory (MB): 65536
  Available CPU cores: 10
Binaries:
  Node: 24.10.0
  npm: 11.6.1
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  next: 15.5.5 // An outdated version detected (latest is 16.0.0), upgrade is highly recommended!
  eslint-config-next: N/A
  react: 19.1.1
  react-dom: 19.1.1
  typescript: 5.9.3
Next.js Config:
  output: N/A

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

Performance

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

Other (Deployed)

Additional context

The screenshot shows the ops/s after deploying v16 around 3:30 PM, I then proceeded to revert back my changes:

<img width="1920" height="526" alt="Image" src="https://github.com/user-attachments/assets/e522ce93-79ac-46a2-a0a8-0dee4a17ff64" />

extent analysis

TL;DR

The most likely fix is to investigate and optimize the changed behavior in Next.js 16 that is causing the doubling of requests.

Guidance

  • Review the Next.js 16 release notes and documentation to understand the changes that may be causing the increased number of requests.
  • Check the application code for any areas that may be triggering additional requests, such as unnecessary re-renders or fetches.
  • Use performance monitoring tools to identify the specific requests that are being duplicated and optimize their handling.
  • Consider opening an issue with the Next.js team or seeking community support to understand the expected behavior and potential workarounds.

Example

No specific code snippet can be provided without more information about the application code, but an example of how to monitor performance in Next.js using the next/next.js module and a performance monitoring library like web-vitals could be:

import { reportWebVitals } from 'web-vitals';

// Report performance metrics to analytics service
reportWebVitals((metrics) => {
  console.log(metrics);
});

Notes

The issue may be specific to the application code or configuration, and more information would be needed to provide a definitive solution. The provided environment information and package versions may also be relevant to the issue.

Recommendation

Apply workaround: The best course of action would be to investigate and optimize the application code to mitigate the increased number of requests, rather than downgrading to Next.js 15. This will allow the application to take advantage of any performance improvements and new features in Next.js 16.

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