I am noticing that my boot time to Rocket Chat (hosted by you) from Australia is really slow.
Here are some notes on what I am noticing on reload.
On my desktop I am seeing about 6 seconds or so on reload into our #general channel.
I am only noticing 2 or so seconds of JS execution and evaluation.
There is a huge “gap” between the first evaluation (that results in a white screen) to the second evaluation that brings up the content. During the big gap no CPU work appears to be happening, it is all on the network.
In the Network Tab I see a huge number of websocket frames, worst of which is a 157K frame.
Since Web Sockets do not carry any compression AND there are a huge amount of frames sent the huge gap is likely either a result of just too much uncompressed data being sent combined with a bunch of round trips.
Additionally, a bunch of sound assets that should not have been delivered till way later and should be cached properly but are not:
Given the large duration here I would recommend a loading screen like slack has, cause the white screen is not great
Amend it so the initial data payload is delivered with the initial request as opposed to trickled through via web sockets
Do a full asset audit, confirming you are delivering assets people really need on initial page load and that they are cached correctly.
Happy to open multiple issues on GitHub if you wish.