Product Page · SSR 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 | SSR | Client | Δ |
|---|---|---|---|
| Performance score | 99 | 100 | +1% |
| First Contentful Paint | 391 ms | 458 ms | +17% |
| Largest Contentful Paint | 682 ms | 583 ms | -14% |
| Total Blocking Time ★ | 90 ms | 69 ms | -23% |
| Cumulative Layout Shift | 0.0 | 0.0 | +0% |
| Speed Index | 898 ms | 503 ms | -44% |
| Script Bootup | 342 ms | 314 ms | -8% |
| Total Transfer | 801 KB | 809 KB | +1% |
★ 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%).
product_ssr-desktop
product_client-desktop