For the last couple of days, I've been trying to improve the rendering speed of my Blazor WASM ASP.NET Core Hosted application. I have looked at the following references:

https://github.com/dotnet/runtime/issues/40386

Blazor WebAssembly deserializing is much slower than even the download? What is wrong?

https://docs.microsoft.com/en-us/aspnet/core/blazor/webassembly-performance-best-practices?view=aspnetcore-5.0#optimize-rendering-speed

There has been very little success in improvements by following the above suggestions and since it's been a while I figured I'd see if anyone had any other answers.

Basically, there is always a "lag" when going to a new page. You click the link, wait a few seconds, and then the page loads. The strange part is even if there are no API calls, there is still a delay. The strangest part though, is when I DO make an API call, the API calls themselves say they take less than a half a second but the actual rendering of the page takes 3-4 seconds. I've been using virtualization and for the most part the pages are fairly trivial (Cards, Grids, etc)... so I'm quite confused at what, if anything, I could be doing wrong to where there is such slow performance. I am new to Web Dev in general so any insight would be much appreciated. For what it's worth, below is a picture of the actual performance where the vast majority of it is "Scripting". Also for what it's worth, I'm using Radzen Components. Ideally, it would be where you click and the page loads right away and the components load as they render but I'm not sure if that's possible with Blazor.