What the author fails to mention is that these are on-demand instances, and what's seen is the 'environment provisioning' delay, not some sort of 'loading screen'.
I'm getting the feeling this article is written from the viewpoint of a long-suffering Windows/Microsoft ecosystem user.
When I started, the provisioning delay was about 7 minutes and the loading screen was actually first just a 404 error and then just a static page saying something like "please wait while this gets set up" (no progress bar and no redirect on completion).
It's funny knowing that has been one of the biggest onboarding advancements and it's still being seen as a flaw.