Problem
During Blazor WebAssembly startup, root/layout components (AppShell, Header, NavBar, HomePage, AppAiChatPanel) receive a burst of StateHasChanged calls, and each one triggers a full subtree re-render. On the WASM UI thread this startup rendering is a measurable bottleneck, and most of these intermediate renders are discarded almost immediately.
Impact
- Avoidable render CPU during the most latency-sensitive window (time-to-interactive).
- Slower perceived startup on Blazor WebAssembly specifically.
Area
Boilerplate template — Boilerplate.Client.Core components.
Problem
During Blazor WebAssembly startup, root/layout components (
AppShell,Header,NavBar,HomePage,AppAiChatPanel) receive a burst ofStateHasChangedcalls, and each one triggers a full subtree re-render. On the WASM UI thread this startup rendering is a measurable bottleneck, and most of these intermediate renders are discarded almost immediately.Impact
Area
Boilerplate template —
Boilerplate.Client.Corecomponents.