posted on Sep, 2 2009 @ 05:06 PM
reply to post by tothetenthpower
Sorry my friend, but you're incorrect.
You connect to ATS, which begins serving content in a linear fashion. Before the actual page content is served, ATS relays third party content such
as tracking scripts and advertisement, then the page content is sent, and the client browser renders the page.
sometimes its fast, sometimes its slow. There are indeed times when an ATS user may have to wait several
minutes for a single page to load.
The worst part is that most of the time, its' nothing that ATS can do anything about. If the quantcast servers, for example, are having some sort of
difficulty serving the requested script to a particular client, that client's going to have to wait for it to either load or time out before the rest
of the page is rendered.
As a web developer, I deal with this all the time. Trust me, it's a very real issue, and those that haven't experienced it should consider
themselves lucky instead of spouting that the user doesn't know what they're talking about and that it's their internet connection. ATS is
extremely well written, and performs exceptionally well given the workload. This issue is confined to data served by third party servers.
So, in summation, it's not ATS that's slow, it's ads.doubleclick.net (by far the worst offender), or quantserve.com etc.