Even a blog should be served over HTTPs. There's opportunity to inject JS for a MITM attack. Greyhound wifi does this all the time. Something more interesting:

Even a blog should be served over HTTPs. There's opportunity to inject JS for a MITM attack. Greyhound wifi does this all the time. Something more interesting: if your site provides something like a code snippet, a MITM could change it. A lot of download sites serve downloads on http. A MITM could change out the binary. This is especially bad if you're downloading something like a library (example: zeptojs, foundation by zurb) So yeah. There's a lot of attack vectors. Do your best to minimize it even if you can't think of anything.