Slooooooooooooooooooooow!

Is anyone else having this problem? When I load pages on LB (and it is only on LB this happens), the pages are very slow to complete loading. Often I can read a lengthy post, but the circle thingy (I think that's the technical word) is still going round and round in the URL bar.

Other sites load within about one second, LB pages take about 20-30 seconds. Any ideas anyone? :beagleThis reply is still going round a full minute or more after posting, though I can read the reply fine)

[Tools]

Re: Slooooooooooooooooooooow!

Logout and clear cookies

[Wombats]

Re: Slooooooooooooooooooooow!

I run C Cleaner every night, so all cookies and cache are cleared daily. It still does it. The odd thing is it doesn't affect what I can do, but the circle keeps spinning so the page has clearly not finished loading.

I'd put it down to my ancient laptop if it happened on any other site, but it doesn't. :beagle:

[Tools]

Re: Slooooooooooooooooooooow!

Even so, hit LOGOUT wait for the "cookies have been cleared" message and close your browser, reopen and log back in. Then come back to this thread and hit F5, see how long it takes to load.

[Nibbler]

Re: Slooooooooooooooooooooow!

The main part of the page load is fairly fast here, but some laginess preventing it loading fully that quickly is coming from the usual suspects. twitter images, scripts, widgets etc.

[Tools]

Re: Slooooooooooooooooooooow!

Also update to Firefox v33, you are running v32

[Wombats]

Re: Slooooooooooooooooooooow!

Even so, hit LOGOUT wait for the "cookies have been cleared" message and close your browser, reopen and log back in. Then come back to this thread and hit F5, see how long it takes to load.

Taking about 8 seconds on average.

[Tools]

Re: Slooooooooooooooooooooow!

The main part of the page load is fairly fast here, but some laginess preventing it loading fully that quickly is coming from the usual suspects. twitter images, scripts, widgets etc.

Yes Nibbler, the Twitter Feed and Latest News Feed do slow it down, however it shouldn't be causing load times of over a minute as reported

[Wombats]

Re: Slooooooooooooooooooooow!

Also update to Firefox v33, you are running v32

That could WELL be something to do with it. v32 was not good; 32.1 resolved a lot of bugs; I didn't realise v33 was out - thank you.

[Tools]

Re: Slooooooooooooooooooooow!

LB pages take about 20-30 seconds. (This reply is still going round a full minute or more after posting, though I can read the reply fine)

8 second average is a massive improvement then :thumb:

[Nibbler]

Re: Slooooooooooooooooooooow!

Yes Nibbler, the Twitter Feed and Latest News Feed do slow it down, however it shouldn't be causing load times of over a minute as reported

I was getting some lag on other sites earlier where some twitter elements were timing out completely, but no, it's not usually on quite that scale.

[Wombats]

Re: Slooooooooooooooooooooow!

Long time logging in having upgraded to FFv33. Took about a minute again. Now acceptable - will run with it and see how things go - thanks a lot.

[ComputerGuru]

Re: Slooooooooooooooooooooow!

Just adding to this, we find that LB is very much affected by comms speed as there is sooooo much going on! The new IE11 has a bit of a problem with the site as well (we think it is a memory leak as it only happens after hours on LB even on idle). This one is not fixed by restarting IE but needs a full reboot, but then it is an MS product so...

[Amethyst]

Re: Slooooooooooooooooooooow!

That doesn't sound good.

The site does log you out after a certain period of inactivity and occasionally on IE I have an issue of my cookies getting wonked out and logging in just clicks back to non logged in.

[ComputerGuru]

Re: Slooooooooooooooooooooow!

The IE thing is caused by the number of objects on the page (we think) so a long thread with lots of sigs and smilies and so on eventually kills the machine just leaving the page open. Symptom is seen in task manager on the performance tab, low free memory and high "available" memory (another piece of fabulous MS incorrect labelling as available memory is NOT actually available). When you kill the offending page (LB) available drops and free increases showing you have found the culprit. This is but one of the interesting ways the MS memory model falls over (dis)gracefully.

Solution for LB would be to reduce the number of interesting replies to each thread. Hmmm perhaps there is a flaw in this suggestion