The socket used in the front-end of the explorer gets initialized/modified three times during startup. This causes an approximately 2.6 second delay in loading the index page. In all the three invocations, the socket is ready (received a ledgerClosed message), however its component (or a parent component) has been re-rendered. Eliminating two of these wasteful calls will optimize all pages of the Explorer app.

This component has been initialized inside AppWrapper, hence it impacts all pages of the Explorer app.

Helpful logs for detecting the repeated initialization of the socket can be found in this Github branch. Look out for the following message in the web-browser console: rippled socket is online at timestamp: <appropriate timestamp>