400 ms
Profile
The reader and their plan. Fetched in 400 ms, so it lands almost with the shell.
Ada · Pro
Streaming
Four sections, four clocks.
The page is a synchronous component, so the shell never waits. Each card below is its own StreamBoundary: it shows a skeleton immediately and is replaced the moment its own data resolves — in whatever order that happens.
900 ms
Recent activity
A slower query. Its skeleton holds the card while the three sections around it are already done.
12 events
1.6 s
Recommendations
A third-party call, the slowest part of the page. It never delays a sibling, only its own slot.
5 suggestions
2.4 s
Totals
The last to arrive. By the time it swaps in the other three have been on screen for a second.
87% complete
How it works
- 1. The response starts and the layout, header and footer stream immediately.
- 2. Each StreamBoundary writes its skeleton between two comment markers.
- 3. When a section resolves, its markup is appended in a template and swapped in.
- 4. The order on the wire is the order the sections finish, not the order they appear.
View source: each section's HTML arrives later, inside a <template> tag, moved into place by a few lines of JavaScript. Nothing a page returns is ever written into a script.