SSRLive on request

This route renders on the server for every visit.

The loader runs on each request, forwards timing metadata, and can read Hono context before the page reaches the browser.

The current response came from the server.

These values are generated during the request, then serialized into the rendered HTML and response headers.

01

Live response

Request-specific data produced by the SSR loader before the page is delivered.

Timestamp
2026-09-16T04:15:32.008Z
Render time
0.00ms
User agent
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)
Message
This page is rendered on the server on EVERY request!
02

Hono context

Data forwarded from the Hono request context into the React Router loader through `RouterContextProvider`.

Request URL
https://hono-react-router-vite-canary.motss.fyi/en-US/ssr
Request ID
e857ad77-32f1-471b-8b17-39fce7a1fae5

How to verify the page is really SSR.

The route is meant to be inspected, not just viewed. These checks make the rendering mode obvious.

03

Verification steps

Use the browser and network tooling to confirm the response is generated at request time.

Refresh the route
The timestamp changes on every request because the loader runs server-side each time.
Inspect response headers
Open the Network tab and check `Server-Timing` to verify the loader duration.
Compare rendering modes
Unlike `/` or `/about`, this route is not SSG. Unlike CSR-only UI, its first HTML already contains the server response.