[xiamenese]

Hi,
While I always look forward to finding new entries and comments in the blog, I have a problem ... It takes at least a minute for the blog page to load, and if I wish to look at any of the coment threads, those pages take well over a minute to load.

The problem? http://widgets.technorati.com/linkcount

OW sits there waiting for it to time out, with a blank page until that has happened. Safari displays the page, even though the linkcount is on the way to failure. I have the OW preference set to start drawing the page before fully loaded. And OW doesn't seem to cache that data, so it needs to try to reload it in relation to every new page I access. Makes reading the blog a vvveeerrryyy ssslllooowww ppprrroooccceeessssss.

Why does it time out? Well, I'm here in China and I guess the government's web-page checking system thinks it's politically dangerous ... or maybe it's some kind of pornography system ... just like http://www.qdea.org/ is blocked 'cos it must be politically suspect as it's a .org (It's the download site for Synchronize! Pro X amongst other apps!)

Anyone got any suggestions (other than changing to Safari, that is)? :(

Mark

[troyb]

Hmm, i'm not totally understanding. So you're seeing time outs in both browsers right?

Safari is working quicker for you because it's displaying cached content?

The link you provided above is just pointing at a script and not a blog which may be the cause of part of my confusion.

[xiamenese]

Originally Posted by troyb

Hmm, i'm not totally understanding. So you're seeing time outs in both browsers right?

Safari is working quicker for you because it's displaying cached content?

The link you provided above is just pointing at a script and not a blog which may be the cause of part of my confusion.

Thanks for the response Troy.

Yes, both browsers are timing out on the linkcount, but Safari displays the page as soon as the rest of the data is downloaded ... and not just stuff in the cache. OW doesn't start displaying anything until the linkcount has timed out. This means that with Safari I get to read the blog within a normal amount of time from clicking on the link. With OW for each new page on the blog I try to access I have to wait for the full amount of time set for timing out before I can start to read anything ... I'm not sure how long it is, and I'm not sure where to look, but it's at least a minute. I clink on a link within the blog and the basically have to go away and do something else for a bit, or sit twiddling my thumbs. So I wondered if there's any way round this.

The other point was merely to say that I know this is perhaps a minority interest in that I'm here in China and all sorts of things are blocked by the authorities, such as that script link for downloading software, or your linkcount ... which presumably tells you how many people have accessed your pages. With the Qdea script, I can only presume it's because of the .org ... with your linkcount, God only knows why!!

Cheers
Mark

[troyb]

Thanks mark. I know that since moving to WebKit page rendering works a little differently. The fact that Safari does do show content prior to the load finishing and OmniWeb waiting for the extra content to time out may have something to do with the different versions of WebKit that we're using but it may also be due to something OmniWeb is doing differently. I'll look into this and see if there is anything that can be improved on our end.

Thanks!

[troyb]

Just to add... if it's the same url that times out for you every time in OmniWeb, you might try adding this address to the black list. After doing that OmniWeb wont even try loading it and hopefully this will result in snappier response times for the content that doesn't have a problem loading. I don't know if this will defeat the purpose for you.

[xiamenese]

Originally Posted by troyb

Just to add... if it's the same url that times out for you every time in OmniWeb, you might try adding this address to the black list. After doing that OmniWeb wont even try loading it and hopefully this will result in snappier response times for the content that doesn't have a problem loading. I don't know if this will defeat the purpose for you.

Thanks for your responses Troy.

Blacklisting the URL sounds like exactly the kind of solution I was looking for. I was trying to check the blog again last night, and watched the Network Activity window ... OW doesn't even begin downloading the content until after the linkcount has timed out. I'll have a look how to do it as soon as I have a moment--time to go to work now--and see what happens.

Cheers
Mark

[xiamenese]

Thanks Troy,

I've put the URL in the blocked list and it's working perfectly. Comments pages on blog threads, for instance are now opening virtually instantly.

Mark

[troyb]

Glad to hear that worked for you :)