Open
Feature
1 of 1 issue completed
Description
We've been hearing reports from users that load performance of Blazor WebAssembly apps on low-end mobile devices can be very slow. For example, this user on Twitter reported "bootstrapping is very slow on low-end mobile devices (~10s), caching doesn't help this". We should investigate where the time is being spent on these devices and evaluate options for improvement.
- If the issue is WASM compilation time, that's on the browser to improve.
- If the issue is .NET runtime startup time, preinitialization might help.
- Perhaps we could also cache the preinitialized results with a snapshot of the memory.
- Or maybe these apps are doing something dynamic on startup that's slow.
The first step is to collect some performance profiles. Any help is appreciated! 🙏