Slow pages in CMS

[IpponSeionage]

Hi

One of my clients have a CMS where a request of a page takes about 8 sek. befor the page is shown in the browser.

My question is about google bot ( and other bots ). Will gb wait 8 sek. to get a page, or will it just go away, and dont take the page to the index.

hope you understand my poor english...

[jeremy goodrich]

Welcome to WebmasterWorld [webmasterworld.com]

Sorry for the delay in a reply, your post probably just got lost in the shuffle as this forum is incredibly busy!

I don't know how much of a lag they have to get a page...it should be OKAY, but I don't know for sure. Do you have any entries in your logs for Googlebot?

If so, what was the http status code that it got?

[WebGuerrilla]

GB will probably crawl some of it, but it will have an impact on how much content they will grab. There is only so much time avaialble to crawl the web. If you can't server pages at the normal rate that a bot tends to request them (about 1 page per second) then the bot will eventually give up and leave.

[IpponSeionage]

jeremy goodrich/WebGuerrilla - Thanks :-)

I do not have any logs by now. It is a new CMS and they havent used it on a "live" website.

I am realy worried about the time it is to serve pages to the bots. And it seems to be a problem.

I will inform my client about it.

[bobriggs]

I'm curious, what is a CMS?

[rogerd]

I'd be concerned about users, too. For a user with a broadband connection, 8 seconds may seem like a long time to wait, and is certainly a disincentive to browsing or scanning multiple pages.

[jatar_k]

Content Management System

[bobriggs]

jatar_k:

Oh, well, that would be me! ;) ;)

[tedster]

It is a new CMS and they havent used it on a "live" website.

Sounds like this time lag is because of CMS functionality, as it keeps the content versions and authorizations straight and all that.

When the pages are published "live", I don't think any CMS time-lag should come into play. Then it should just be server hits with no reason to engage the CMS (since a web visitor can't change any content anyway.)

[IpponSeionage]

The problem with the CMS was the URL - like www.firm.com/default.asp?id=234&page=default etc.

They had no god SERP with the system, and made some changes and got a URL like www.firm.com/site2.asp etc.

But the speed after a request is now 8 sek. But not if the page is in the cache of the server then it comes in about 1 sek. The popular pages come fast, and the not popular pages are 8 sek. to get to the client.

The problem is bad programming - i think. And the client dont get all pages in the index.