"The user is only going to see the loading screen for a second anyway".

Tell me more about poor internet connections, Mr. CBD-residing, office-wifi developer. I'm all ears.

Here is an argument : Put your social security number on a loading screen. Since the user is going to see it for a second , it shouldn't be a problem right?

Instead of slapping a loading screen on a slowly loading pile of shit, the proper solution is to fix the performance problems.

@Fast-Nop there actually are times when code can't really be optimized further without going lower level, like using Node-made TensorFlow-abusing libraries piled on top of each other.

@Fast-Nop

There will always be a time when the loading screen is needed no matter who much you tune the performance due to client hardware and network connectivity.

The recommend way is to tune the performance as best as you can but also be aware of client side problem.

@Parzi Superfluous crap can just be removed. No code is fastest.

@mr-user The client-side problems especially on mobile are because the average website is a bloated piece of shit that not only clocks in at 3MB, but also 90 requests (latency problem!), which is why it takes more than 7 seconds to load even on desktop.

@Fast-Nop that's actually a smart idea - i never considered that I should just delete my code...

@j2k4 You'd be surprised how far KISS and YAGNI go. Ancient engineering principles that brought people to the moon with an onboard computer on C64 level.