Restaurant Detail · RSC vs Client · Desktop
Desktop reports use 50 ms artificial DB delay to emulate real-world load
This demo app is small and fast — under normal conditions all three rendering strategies score similarly on desktop.
PageSpeed Insights does not throttle CPU or network on desktop, so it cannot surface the performance differences
that matter in production. Adding ?delay=50 to every
page injects a 50 ms sleep after each database query, simulating the heavier queries and higher latency of a real-world application.
This makes the RSC streaming advantage clearly visible in Lighthouse scores. The 50 ms delay emulates typical database latency
and API response times seen in production applications under load.
| Metric | RSC | Client | Δ |
|---|---|---|---|
| Performance score | 98 | 83 | -15% |
| First Contentful Paint | 441 ms | 414 ms | -6% |
| Largest Contentful Paint | 912 ms | 1.19 s | +31% |
| Total Blocking Time ★ | 11 ms | 335 ms | +2943% |
| Cumulative Layout Shift | 0.0 | 0.0 | +0% |
| Speed Index | 1.28 s | 730 ms | -43% |
| Script Bootup | 168 ms | 642 ms | +282% |
| Total Transfer | 425 KB | 782 KB | +84% |
★ Blocking Time has the biggest impact on Google's performance score (30%) — it measures how long users wait before they can tap, scroll, or type (LCP 25%, CLS 25%, FCP 10%, SI 10%).
restaurant_1_rsc-desktop
restaurant_1_client-desktop