# One Roundtrip Per Navigation

DevFeed: [One Roundtrip Per Navigation](<https://devfeed.tech/articles/one-roundtrip-per-navigation-36184.md>)

Original publisher: [Read original article](<https://overreacted.io/one-roundtrip-per-navigation/>)

Published: 2025-05-29T00:00:00Z

Content type: article

Language: en

Sources: [Dan Abramov](<https://devfeed.tech/sources/dan-abramov.md>)

Topics: [HTML](<https://devfeed.tech/topics/html.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [API](<https://devfeed.tech/topics/api.md>), [browser](<https://devfeed.tech/topics/browser.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [browser](<https://devfeed.tech/tags/browser.md>), [client](<https://devfeed.tech/tags/client.md>), [html](<https://devfeed.tech/tags/html.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>), [server](<https://devfeed.tech/tags/server.md>), [web-development](<https://devfeed.tech/tags/web-development.md>)

## AI overview

The article examines how many network roundtrips navigation should require. It contrasts traditional HTML applications, where the server returns the page and its data in one response, with client-side applications that may need multiple API fetches.

## Source excerpt

What do HTML, GraphQL, and RSC have in common?