> Counting a solitary log that an IP loaded a resource is hardly the tracking that is harmful. Well the thing is you don't know if it's a single log line. What

> Counting a solitary log that an IP loaded a resource is hardly the tracking that is harmful. Well the thing is you don't know if it's a single log line. What if the 3rd party script you loaded has been modified by a malicious attacker as happened with the great firewall DDOS on Github last year? As server operators, we have a responsibility to preserve the privacy and security of our users. This includes the possibility to leverage 3rd party services when we need it, as long as we make it clear to the users. Having 3rd party requests taking place on the backend means you take the security/performance measures to ensure your website operates properly. Loading these 3rd party resources on the client side means those operational costs/risks lie on your users. You are literally opening backdoors to the browsers of all your users. Also worth noting, 3rd party resources & client side rendering (among other recent silicon valley fashions) play very poorly with higher-latency links. It's a truly degrading experience for your users.