Frontend & browser·State, data and re-rendering
the second request could not start until the first finished, because the component that made it had not rendered yet.
Request waterfall
Also calledfetch waterfall, sequential fetching
Requests that run in sequence when they could have run in parallel, usually because a child component only mounts after its parent's data arrives. Each level adds a full round trip, so a three-deep component tree turns a 100ms API into a 300ms page. The fixes are hoisting the fetches, preloading at the route level, or letting the server render the whole tree at once.