3 ms·
This is exactly the sort of site HN readers complain about whenever there's a thread about frontend dev. 24MB over the network and 22.7s before the page is inte
by onion2k 6y ago
This is exactly the sort of site HN readers complain about whenever there's a thread about frontend dev. 24MB over the network and 22.7s before the page is interactive from a cold cache start. Even with the page cached it takes 3s to start. All for a 3-screens-tall page with a few light animations. There's been literally no attempt to optimize some of the assets. For example, https://wavechat.tech/assets/img/matthew.JPG https://wavechat.tech/assets/img/matthew.JPG is a 2732x2733 JPG that's displayed at 384x384 resolution. Putting it through https://squoosh.app/ https://squoosh.app/ and optimizing it for the right size and better JPEG encoding reduced the size by 97%. That website should be 200Kb and displaying in 500ms at most.
Obviously this is a criticism of the website rather than the application, but I don't even want to try it if the marketing site is that poor.