SsrMode::OutOfOrderthe only route that streams this way
Out-of-order streaming
The frame of this page left the server at once. Each block below followed when its read finished, in whatever order that was, and a small inline script moved it into place. The badge on each block is the order the server finished it in.
Simulated latency is off: every read answers at once. Turn it on to see the blocks arrive out of order.
Reload and watch againStream with the deals failingBack to the tour
current_catalog()home_rail(Deals)This section didn't load. Everything else on the page still works.
home_rail(Featured)
Prada Galleria Medium Saffiano Leather Bag — CelesteEGP ١٩٩٬٠٠٠٫٠٠
Rolex Cellini Moonphase 39 mm — Everose GoldEGP ١٬٣٤٩٬٠٠٠٫٠٠
Apple MacBook Pro 14-inch (M5) — Space BlackEGP ١٠٤٬٩٩٩٫٠٠
home_rail(New)- Apple MacBook Pro 14-inch (M5) — Space BlackEGP ١٠٤٬٩٩٩٫٠٠
Apple iPad mini (A17 Pro) — StarlightEGP ٣٠٬٩٩٩٫٠٠
Nintendo Switch 2EGP ٢٨٬٩٩٩٫٠٠
home_rail(Bestsellers)
Coca-Cola OriginalEGP ٢٩٫٠٠
Farm Brown EggsEGP ٦٩٫٠٠
Nescafé Clásico Instant CoffeeEGP ٣٥٩٫٠٠
- First byte
- —
- Last byte (the slowest block)
- —
- Streamed blocks placed by script
- —
- Without JavaScript the streamed blocks stay skeletons: each one arrives as a <template> that only a script can place.
- The status code and headers left with the frame, before any read finished: a failure later in the stream can't turn the page into a 500.
- A router that fetches this page as HTML gets it only when the slowest block is done, so the shop's pages render in order and the router swaps complete pages.