usually I factor cost of data plan into the decision of where I go next for the reasons you mentioned. Since you say you're doing UI and frontend I think this i

usually I factor cost of data plan into the decision of where I go next for the reasons you mentioned. Since you say you're doing UI and frontend I think this is a big challenge when fetching and pushing binary data like static assets. To reduce your data consumption and improve load times as well as security/privacy you may consider a /etc/hosts blocklist[1]. It's not going to help with reducing data in zoom calls, Netflix and podcasts but it adds up. Also don't forget application/service specific settings like switching all preferred resolution in video to the lowest quality etc. DNS traffic can be reduced (and sped-up) with a local cache (dnsmasq - or better yet dnscrypt-proxy[2]). [1] https://github.com/StevenBlack/hosts https://github.com/StevenBlack/hosts [2] https://github.com/DNSCrypt/dnscrypt-proxy https://github.com/DNSCrypt/dnscrypt-proxy