[qasdfdsaq]

Sorry misread. My brain's been fried of late.

My previous understanding was speedtest.net's speedtests didn't use normal HTTP requests to fetch data and had something proprietary. Either I was misinformed or things have changed, so now it uses standard browser requests.

Still, the browser shouldn't be caching it, any browser storing said data in cache is faulty.

Not familiar enough with ESET to know what it does - all the involvement I've had through my job has been removing it - but as it has a firewall, filtering, and interception capabilities I'd hazard it could contribute in the same way as Kaspersky. Anything that intercepts, analyses, then decides what to do with incoming data is likely to add delays or changes to speed in which that data is delivered.

I don't actually believe AV "caching" is actually caching at all, simply redelivering it at fluctuating rates that confuses the speedtest application. I always see the speedtest data correctly being delivered through the network interface at the correct speeds, then delivered to the browser at strange ones, but the data definitely gets downloaded over the internet, not delivered from cache. Besides, cache would give you several hundred megabits to gigabits per second, not 50-200 meg like we're commonly seeing.