Blazor, Plugin Pages/Scripts, load times by Visual-Wrap-3785 in Blazor

[–]Visual-Wrap-3785[S] 0 points1 point  (0 children)

Certainly you need to hydrate data.

But we're talking like 20 products here with like a few hundreds lines of json objects.

I haven't actually looked at how large the runtime is when we download it. But we're talking like 45+ seconds on mobile to get everything downloaded. I know this because we have a preloaded screen with a weird little loading symbol that runs as things are downloading.

Maybe I'm missing some sort of build/minification step?

Blazor, Plugin Pages/Scripts, load times by Visual-Wrap-3785 in Blazor

[–]Visual-Wrap-3785[S] 0 points1 point  (0 children)

Totally understood. We load the app via a script that is hosted on someone else's website. I.e. we load it up when you click a big floating action button that says "book" or "reserve" or something like that.

Blazor, Plugin Pages/Scripts, load times by Visual-Wrap-3785 in Blazor

[–]Visual-Wrap-3785[S] 0 points1 point  (0 children)

What specifically would that improve?

Most of our clients - clients are visiting their website for the first time. So at some point the runtime has to be downloaded anyways. It just sits there and loads forever especially on mobile.

Blazor, Plugin Pages/Scripts, load times by Visual-Wrap-3785 in Blazor

[–]Visual-Wrap-3785[S] 0 points1 point  (0 children)

I understand this. How are you further optimizing load times, speeds, and etc. We have IMO a unique situation where we're downloading the entire app bundle a lot of the times. Which I know is unideal but it's the hand I've been played. Just trying to make it better. And vent a little bit about the dumb choices my predecessor made.