🔗 Stop mounting your LiveView twice

Every LiveView mounts twice on the first page load—once for the static HTTP "dead render" and again when the WebSocket connects. This can lead to unnecessary database queries and performance hits. The recommended fix is to use connected?/1 to conditionally load data during the connection, but this approach has its drawbacks. It still results in duplicate processing when mounting and can hinder SEO and user experience by leading to an empty first paint.

The article outlines the limitations of this conventional solution and highlights ongoing efforts by the Phoenix team to improve LiveView's handling of mounts via the adoption of LiveViews. This new approach aims to keep the LiveView process alive across connections, avoiding the need for multiple mounts altogether, enhancing performance and reliability. By addressing these challenges, developers can create more efficient LiveViews without compromising on initial page load quality or SEO prioritization.