[Max Taxable]

Originally Posted by tbworld

Seems to load just fine, I am wondering, if on some browsers they are seeing the page not complete due to the AJAX call in comet chat, until the second AJAX call. I have seen this kind of behavior before.

Here's how that call played, on the test I ran earlier. It was a IE 10 browser.

URL: http://cafe-flirt.com/cometchat/cometchat_receive.php?callback=jqcc171050211963855 38795_1381008467828&buddylist=1&initialize=1?ttime =1381008467?tamp=0&typingto=0&status=&basedata=nul l&_=1381008467981
Host: cafe-flirt.com
IP: 50.116.122.156
Location: Houston, TX
Error/Status Code: 200
Client Port: 58768
Start Offset: 2.420 s
Time to First Byte: 331 ms
Content Download: 5 ms
Bytes In (downloaded): 1.4 KB
Bytes Out (uploaded): 0.7 KB

Here it is in firefox:

URL: http://cafe-flirt.com/cometchat/cometchat_receive.php?callback=jqcc171080906285181 36633_1381028926933&buddylist=1&initialize=1?ttime =1381028927?tamp=0&typingto=0&status=&basedata=nul l&_=1381028927183
Host: cafe-flirt.com
IP: 50.116.122.156
Location: Houston, TX
Error/Status Code: 200
Client Port: 55397
Start Offset: 2.759 s
Time to First Byte: 277 ms
Content Download: 4 ms
Bytes In (downloaded): 1.0 KB
Bytes Out (uploaded): 0.7 KB

Here's Chrome (Safari):

URL: http://cafe-flirt.com/cometchat/cometchat_receive.php?callback=jqcc171091298161423 76512_1381029050414&buddylist=1&initialize=1?ttime =1381029050?tamp=0&typingto=0&status=&basedata=nul l&_=1381029050593
Loaded By: http://cafe-flirt.com/cometchat/cometchatjs.php:3
Host: cafe-flirt.com
IP: 50.116.122.156
Location: Houston, TX
Error/Status Code: 200
Client Port: 49469
Start Offset: 2.820 s
Time to First Byte: 157 ms
Content Download: 5 ms
Bytes In (downloaded): 1.0 KB
Bytes Out (uploaded): 0.7 KB

Can't imagine anyone human using IE6 but pretty sure it wouldn't handle this call very well. These three more modern browsers handled it with aplomb.

To the OP: Might be helpful to you if you ask the folks having problems, what OS and browser they're on.