That USA Today experience is sadly typical. The requests aren't all for "tracking" per se; some of them are for audience analytics, some for ads, some for performance monitoring, etc. Then you run into the situation where your browser makes one request and it turns into a long chain of redirects, each of which counts as a separate request and necessitates a separate DNS lookup, possibly negotiating a new SSL connection, getting the content and parsing it, etc.Jadagul wrote: ↑26 May 2018, 19:29I mean, I knew there was a lot of tracking stuff. I didn't think that the tracking stuff added up to multiple megabytes. (I'm still a bit confused about what all those megabytes are actually doing---why do you need that much data to do tracking?)
Basically, I don't mind being tracked at all. Or getting fed ads. I mind the performance hit that the tracking and the ads cause.
For example, when you load usatoday.com, there's a request for https://match.adsrvr.org/track/cmf/gene ... &ttd_tpi=1, which redirects you to https://match.adsrvr.org/track/cmb/gene ... &ttd_tpi=1, which redirects you to https://sync.go.sonobi.com/us.gif?nw=td ... c227eb7c25.