|
| News | Profile | Code | Photography | Looking Glass | Projects | System Statistics | Uncategorized |
Blog |
Is anyone else getting tired of web analytics causing page loads to never complete?
Stuff like this is a common occurrence for me:
It seems to be getting worse, too. Sites like Juniper Networks and VMware's pages just fail to load, and sit there chewing up browser threads due to unresponsive web analytics. Twitter seems to suffer from this, as well.
It wouldn't be such a nuisance, but most pages have some sort of JavsScript code that's only executed when the page is completely loaded. Like, scripts that change focus or populate certain input fields may be necessary for correct functionining of the page. It's annoying when you've already started to fill in forms, then the page finishes loading and JavaScript code clears out all the input elements for you.
I'm thinking of just starting up a local resolver on my workstation and have it be authoritative for the following:
Then, I figure adding a wildcard record pointing to 127.0.0.1, and possibly running Apache locally might speed things up. It'll also give me an idea of who's using what.
I don't like being a statistic, anyway!
New comments are currently disabled for this entry.
     |
This HTML for this page was generated in 0.001 seconds. |
I do this to analytics servers, ad servers, and all known spyware sites.
I do have to get used to giant white spaces that end up never loading anything, but boy, those pages sure load fast- could point it to a local nginx server that just spits out the appropriate blank files, but it's not really worth the effort.
What is worth the effort is getting the webserver to run mod_rewrite of some sort so that clickthrus aren't broken, when possible (like when the destination url is passed to the analytics or ad server as the url or a url parameter). That would be the not-too-rare occasion when adsense does gets it right and I actually do want to try out a vendor in the google ads, or some supposed awesome deal on fatwallet that happens to be doing the crazy quadruple referrer redirect thing.