Interesting post – I bet most people don’t understand that they can take measures to speed up their browsing. But let me as you something – in a world were most people aren’t savvy with the guts of their systems, or where mobile devices have limited bandwidth, should it really be the responsibility of the end user (consumers) to optimize?

I personally believe it’s the responsibility of website owners to take it upon themselves to bring the optimization to you. The problem is that most of them either don’t know how or simply neglect the practice.

My team released a tool recently that helps site owners find all their performance issues and walks them through fixing them. That’s the first step in speeding a website up. Even better, our proxy caches website content making sites 3x to 4x faster.

The goal here is to remove the burden from both the end users and web ‘masters’ so we can all get on with what we’re trying to do online without slow downs.

If you’re interested, give http://www.pagelabs.com a look – it’s our solution to this common and wide spread problem.

FuzzyJedi
Thanks for your comment, I understand that QoS is a function at the network protocol level that allocates bandwidth to competing online connections. Residing in the transmitting machine, it determines how many packets are handed to each connection (each flow) at a given time. A packet scheduler makes its determinations by observing the packet flows from the applications or by request from a quality of service (QoS) protocol such as RSVP or Diffserv and I don’t see why it’ll be screwing up.
Please, let us all know the reason for it, I’ll be more than happy to delete my entry and publish yours (that’s all about constant learning)
Thanks again,
Cheers
Lucio