Prefetching

To reduce loading skeletons in v0, the team combines Next.js Partial Prefetching with cache rules suited to public and personalized data. Playwright instant() tests check that priority content is ready at click time, and remain in the codebase as CI regression checks.

Prefetching also responds to user intent: in large grids, details load on hover, focus, or touch rather than for every visible card. That adjustment followed a 2.9× increase in prefetch requests. The overall comparison reports lower daily costs, while cautioning that the change cannot be attributed to this refactor alone.

Next.js 16.4 makes Cache Components the recommended approach, now enabled by default for new projects created with create-next-app. This model lets you declare cache behavior at the component level, with APIs to control static or dynamic rendering and fine-tune prefetching. The release also brings agent tooling for migration, Turbopack optimizations (cache size, HMR, smaller bundles), support for React 19.3, and several experimental features for build and development.

ForesightJS observes cursor movement, keyboard navigation and scrolling to estimate the next target. It can start loading before a click or touch interaction.