I've noticed that sometimes when I go to start up my app in development mode (next dev --turbopack) and then I navigate to the homepage, the page refreshes a lot and I see so many duplicate requests in my console output, like this:

 GET /en 200 in 4.8s (next.js: 1985ms, proxy.ts: 5ms, application-code: 2.8s)
 GET /en 200 in 459ms (next.js: 43ms, proxy.ts: 10ms, application-code: 406ms)
 GET /en 200 in 365ms (next.js: 5ms, proxy.ts: 4ms, application-code: 356ms)
 GET /en 200 in 389ms (next.js: 24ms, proxy.ts: 3ms, application-code: 361ms)
 GET /en 200 in 372ms (next.js: 4ms, proxy.ts: 8ms, application-code: 360ms)
 GET /en 200 in 419ms (next.js: 38ms, proxy.ts: 5ms, application-code: 376ms)
 GET /en 200 in 356ms (next.js: 6ms, proxy.ts: 5ms, application-code: 346ms)
 GET /en 200 in 395ms (next.js: 5ms, proxy.ts: 7ms, application-code: 383ms)
 GET /en 200 in 370ms (next.js: 7ms, proxy.ts: 5ms, application-code: 358ms)
 GET /en 200 in 383ms (next.js: 5ms, proxy.ts: 4ms, application-code: 374ms)
 GET /en 200 in 394ms (next.js: 49ms, proxy.ts: 7ms, application-code: 337ms)
 GET /en 200 in 371ms (next.js: 36ms, proxy.ts: 3ms, application-code: 333ms)
 GET /en 200 in 335ms (next.js: 4ms, proxy.ts: 4ms, application-code: 327ms)
 GET /en 200 in 358ms (next.js: 4ms, proxy.ts: 3ms, application-code: 351ms)
 GET /en 200 in 354ms (next.js: 6ms, proxy.ts: 3ms, application-code: 345ms)
 GET /en 200 in 418ms (next.js: 47ms, proxy.ts: 3ms, application-code: 368ms)
 GET /en 200 in 357ms (next.js: 5ms, proxy.ts: 4ms, application-code: 348ms)
 GET /en 200 in 366ms (next.js: 6ms, proxy.ts: 4ms, application-code: 356ms)
 GET /en 200 in 388ms (next.js: 6ms, proxy.ts: 9ms, application-code: 373ms)

I'm using Next.js 16.2.11 and the app also connects to a Neon database. I don't see this behavior when I build the app and then start it. Anyone know what could be causing this or how I could try to understand what's happening better?