Tuesday, November 05, 2013

Slow Burnin' Blog Turnin' Solution Yearnin'

If, like my friend Jeff, you find The Earliad has slowed down to a crawl, give this a try: activate compatibility view on your browser - that is, if you're using Microsoft Internet Explorer. According to scientific tests run by Jeff, this seems to speed things up. Give it a shot and let me know if it works in the comments. If not, I'll have to take more...drastic measures.


Totty said...

Better yet, don't use IE.

"Jeffics" said...

Thanks for that informed advice! Of course, in an ideal world, that would be the answer for everyone. However, I don't think you did the testing that I did, so now I have to expand on Earl's comment.

The slowdown issue occurs regardless of the browser. I've tested on IE, Chrome, Firefox and even Mac using a variety of computers. I found that two things happened. 1) Earl's label list is a contributor to the slowdowns. 2) Older OS's/computers aren't as likely to slow down as newer ones.

The compatibility mode fix only works when the page is not stalling, so you will have to press the button several times to get the page to refresh and not stall. Once it locks in on the setting, then you don't have to touch it again.

Part of the issue is that Blogger is getting less and less support, and lags behind OS development cycles. Sooner or later we Bloggers are going to have to deal with a reckoning.

So far, the one thing that had worked is the Compatibility Mode. Maybe there are other work arounds, but I hope you can appreciate that I am busy and that troubleshooting is not my primary function. I was pretty excited to get Earl's blog running again because for a few weeks the only way I could access it was on an incredibly creaky laptop that takes a couple minutes to load a page on a good day.

So, if you want to help by testing out workarounds on the other OS's and systems, that would be a tremendous help. It turns out to be a time-consuming chore.

I think it's a big step forward that we have at least this one solution. Frankly, I don't care which browser I use, as long as it works. So far, the fix is for IE. If you have a better tested solution, don't be shy. If you're just beaking off, though, we need help with testing more than we need browser partisans.