Menu

1 / 5

Next.js Prefetching in App Router: How `<Link>` Partial Prefetch Works and Why Your Pages Still Feel Slow

DEV Community·jsmanifest·18 days ago
#yRmUGJ5y
#dev#prefetch#next#cache#loading
Reading 0:00
15s threshold

Next.js Prefetching in App Router: How <Link> Partial Prefetch Works and Why Your Pages Still Feel Slow

This article was written with the assistance of AI, under human supervision and review.

Developers adopt Next.js App Router expecting server components to eliminate client-side waterfalls and prefetching to deliver instant navigation. The reality surprises them: links feel sluggish, dynamic routes block for seconds, and the DevTools network tab shows requests firing only after the user clicks. The prefetch happened, the data arrived, but the navigation still waits.

The confusion stems from three behaviors that collide in production: partial prefetch stops at the first Suspense boundary instead of loading the full page, the router cache expires prefetched data after 30 seconds for dynamic routes, and the client cannot render anything until the server responds with the missing pieces.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.