> Make sure http2 is activated HTTP/2 suffers from Head-of-Line blocking, which may impede rather than help speed up the connection. In most cases, this doesn'

> Make sure http2 is activated HTTP/2 suffers from Head-of-Line blocking, which may impede rather than help speed up the connection. In most cases, this doesn't happen, but when they do happen it's consistent. Testing is required, because there are cases where HTTP/2 backfires spectacularly. > That assets that never change are cached Fair point, I also strongly recommend this. Plus, if your server supports statically compressing resources ahead of time it pays serious dividends (and activating Brotli, if you can custom compile applications or lucky to use a distribution that built it). > And if possible use a hosting provider in the same country your users are located. In Europe, this is relatively easy. In the US and Russia, probably two servers (for East and West coast/okrugs). In Asia? Surprisingly difficult, unless you're in East Asia (I'm not discussing why here since there's plenty of resources to learn more about why it's a pain in the rear). Africa? Actually, despite improvements in connectivity I strongly recommend to make the pages small and simple (as the requirements allow).