Something that caches dynamic responses will certainly work as well. Usually those are situations where you want content changed on every reload, though. My sit

Something that caches dynamic responses will certainly work as well. Usually those are situations where you want content changed on every reload, though. My site is actually dynamic as well, but it's just C code that concatenates three files together, and does just a tiny amount of metrics at the end. I'm not going to say my design is maximally efficient, because it definitely isn't. It's just that 'modern' dev creates sites that are orders of magnitude more expensive to construct pages with. That stuff works for major corporations with data centers. It doesn't work so much when you're one of 256 instances on a single blade server inside a single data center hosting 20,000+ servers. Also, when it comes to HTTPS, my site also uses that. HTTP redirects to HTTPS, and the TLS used is very strong 256-bit ECC. The biggest cost to crypto is definitely for people living overseas from the server location. The added round-trip inherent in TLS v1.2 and below slows things down for international visitors. But ... I kind of lost it when my own ISP started injecting falsified HTTP responses to redirect me to their "maintenance notifications." I don't have the luxury of switching ISPs, so instead I'm moving everything possible to HTTPS.