If I want to download a particularly big file, I use tethering via my phone. Seriously, about 90Mbit/s download on the phone, that's faster than most places I've worked and also faster than my home connection.
It was so obviously better, that I switched home to be on 4G instead of ADSL, because the 4G was both cheaper and faster. It's working out well, but the phone still manages to be faster than the router.
I tether my iPad to my 4G phone because the latency/bandwidth is much higher than my home internet (40mbps).
I ran Speedtest on my phone vs my desktop with a wired connection to the router and learned that my 4G wireless connection was faster.
enterprise connections pay a premium, and smallish employers often don't want to spend money on monthly expenditures, so mostly ~50-200mbit shared between all people at the office
You can get 1g down, 50mbit up for less than a tenth of that with cable for example. We used that line heavily and I loved it, but I'm still unsure if I should rather have spent the money differently.
We've moved now to a WeWork Style Location ( Studio from Tishman Speyer ) and are down to 100/100, have put our vpn equipment in a datacenter for 70€/m and nobody complains.
The most efficient way is probably to get consumer cable through the CEO(for "private" access to YouTube etc) combined with a smallish business vdsl connection for everything company related.
if your business relies on connectity, best to avoid it.
They do know that consumer internet is asymmetrical and not practicable for real work.
FYI ELM (ethernet last mile) at 70Mbs in the UK costs about £70 pm
Also there is no need for the kind of language. It definitely isn't helping your argument so you might just as well drop it.
Office work does not require fast Internet access and does not require that your Youtube videos load instantly.
We did some research and it seems broadband Internet access does not improve productivity and may actually reduce it.
Any minuscule increase in productivity (I mean a total of 5 minutes of loading times per employee per day) is meaningless. People can't focus on their real work for 8 hours straight. When Internet works faster, people just use more of it and are less selective about how they use it. People also get quickly used to increased performance and will be complaining at almost any performance point.
Another research on build times showed that hugely increased build times don't improve productivity either. At first yes -- people get excited. But then, when build times are very short (say 5s compared to 10m) most (but not all) developers just stop staring constantly at their IDE and thinking about how to structure their code and instead reduce their iteration to a minimum (say couple of lines of code) and just restart to see if it works. This seems to actually reduce quality of produced code.