Turkiyenin en sevilen filmlerinin yer aldigi porno internet sitemiz olan ve sex tarzi bir site olan sitemiz gercekten dillere destan bir durumda herkesin sevdigi bir site olarak tarihe gececege benziyor. Sitenin en belirgin ozelliklerinden birisi de Turkiyede gercekten kaliteli ve muntazam, duzenli siteleri olmamasidir. Bu yuzden iste. Ayrica en net goruntu kalitesine sahip adresinde yayinlanmaktadir.
Gelmiş geçmiş en büyük porno sitemiz olan 2pe de her zaman en kaliteli pornoları sunmayı hedefledik. Diğer video sitemiz olan vuam da ise hd porno ağırlıklı çalışmalara başladık.
I'm getting reports from multiple customers that when they have Norton 360's BHO enabled and try to load my site under IE9 they are seeing long delays prior to the page even beginning to render (10+ seconds). Looking at the network trace from these customers, I can see that it's not download time for the JS files that is the issue. After the JS is downloaded, there is a long delay before JS processing starts and I'm guessing it is related to the Norton BHO scanning the JS. This happens on both my site and on the EXTJS samples. When I have the affected customers disable the Norton BHO, the delay goes away.
Is anyone else seeing this? Any ideas about how to get around this?
Thanks for the response. The problem does not occur in Private Browsing mode or if the users manually disable just the Norton BHO. Any idea if it's just purely a function of how much JS is being loaded on the page and Norton scanning all of it before allowing execution? We do not see this problem on another page that uses jquery, but it was not loading the full library so the amount of code was only about a tenth of what I'm loading on the EXTJS pages.