An alternative application level protocol that is easily overlooked is CoAP (RFC 7252).
A protocol designed for constrained devices (low memory or power, etc) that follows HTTP's REST interface, and also includes a observe (subscribe) method for watching sensor values.
It's a nice alternative to HTTP since it's a binary protocol, with little processing overhead. Supports UDP and works over 6LowPAN which MQTT and HTTP struggle with. Ideal for Bluetooth, ZigBee or Z-Wave
Disable Javascript for that site and it reads normally. I've found that most news sites become much more readable (and chew through far less of my CPU, and stop autoplaying loud videos, and skip paywalls) with JS disabled.
The Chrome plugin I'm using (Quick Javascript Switcher) disables on a per-domain basis and remembers the setting for each.
I'm a huge fan of SPAs and JS in the browser and yet I'm quickly blocking JS out of large swaths of the internet simply because it improves the browsing experience. I'm not quite sure what this lesson is teaching me.
Just a note that YesScript isn't compatible with my Firefox Nightly now (due to the move to WebExtensions) and will probably stop working with Firefox in general in the future.
It's a nice alternative to HTTP since it's a binary protocol, with little processing overhead. Supports UDP and works over 6LowPAN which MQTT and HTTP struggle with. Ideal for Bluetooth, ZigBee or Z-Wave