> By using HTTPS my website increases it’s overhead by almost 100%. It should be mentioned that my personal website is also plain text based and tiny. Imagine t

> By using HTTPS my website increases it’s overhead by almost 100%. It should be mentioned that my personal website is also plain text based and tiny. Imagine the impact of a blog article or research paper with significantly more content. An extra kilobyte. Wow. Such data transfer. What a dealbreaker. No HTTPS means worse performance, because HTTP 2.0 requires it. HTTP 1.x doesn't have connection multiplexing. When I moved my blog to HTTP 2.0, I noticed that it loaded faster, even when on the same LAN as the server. > Helpful Tips: > If users are nervous of links set in standard http:// http:// format, they can add s themselves or better yet, use a browser extension like HTTPS Everywhere (highly recommend) HTTPS Everywhere won't be supported beyond 2022: https://www.eff.org/deeplinks/2021/09/https-actually-everywhere https://www.eff.org/deeplinks/2021/09/https-actually-everywh...