Summary
There is no client-side visibility into page load performance across different routes. A structured log using the Navigation Timing API should emit load metrics on each full page navigation so slow routes can be identified from production logs.
Scope
- After each route change, read
PerformanceNavigationTiming for the current page
- Emit a debug-level log with fields:
route, dom_content_loaded_ms, load_event_ms, time_to_first_byte_ms
- Log should only fire after the load event has completed, not during navigation
- Skip logging on routes where the timing data is not available
Acceptance Criteria
ETA: 12 hours
Coordinate on Telegram
Summary
There is no client-side visibility into page load performance across different routes. A structured log using the Navigation Timing API should emit load metrics on each full page navigation so slow routes can be identified from production logs.
Scope
PerformanceNavigationTimingfor the current pageroute,dom_content_loaded_ms,load_event_ms,time_to_first_byte_msAcceptance Criteria
ETA: 12 hours
Coordinate on Telegram