In a support thread titled “New loading splash has been disappeared?”, Jagster reports that the new loading splash screen — which appears when Discourse takes longer than 2 seconds to load — is no longer visible on their forum or the Discourse meta site after a recent upgrade. They question whether the threshold for showing the splash is too high or if it’s simply not appearing at all. Falco clarifies that the splash appears only if loading exceeds 2 seconds, meaning faster sites won’t show it. Jagster confirms they don’t see it at all, even though their loading times exceed 3 seconds, and jokes about needing to slow down their connection to test it. Falco suggests using browser DevTools (Firefox/Chrome) to throttle network speed for testing. Finally, Jagster notes the splash does appear when using Safari (a slower browser), suggesting the issue may lie in their own setup rather than a global bug. The discussion ends on a lighthearted note, acknowledging that Discourse may have gotten faster — making the splash less necessary.
That new spash when loading time is too long… how long is too long? Just wondering because after the newest upgrade I haven’t seen it here or either on my own forum. It worked earlier.
Colors will now follow colors of a forum — that means default color set I reckon? What if colors are mainly black and white will those blinking balls be black and white too?
So it’s showing for too long or not at all? 
The current behavior is that it starts showing when you are waiting for 2s until Discourse loads.
If the site loads under 2s on your device you will never see it
If the site loads in 3s you will see it for 1s
If the site loads in 20s you will see it for 18s
Not at all.
But that 2-3 secs limit may be enough. That means you guys made Discourse a little bit faster then 
Any ideas how can I slow down my connections 
edit
Well, here and on my own loading times are defenetly over 3 secs. But of course I don’t know if splash is on here. It was, though.
Firefox and Chrome have a Throttling option on the DevTools Network tab.
I got it here when using Safari (it is slower browser than others…), but not on my own — so, the issue — if I can even call it that way — must be on my setup. Good to know.