Last post 5 hours 55 min ago

Posts last week 89

Average response time last week 30 min

All time posts 67735

All time tickets 10467

All time avg. posts per day 21

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.

Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!

All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#4394 – url very slow to load

Posted in ‘sh404SEF’

This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Wednesday, 06 December 2017 19:20 UTC

businesstraveller

Hello,

We have a website with around 15000 urls. Old urls load very slow like 2 or 3 minutes to open.

It seems SH404 has problem managing so many urls.

Could you help us?

regards.

Thursday, 07 December 2017 19:24 UTC

wb_weeblr

Hi

sh404SEF is very optimized, and 15,000 URLs is definitely not a large number. Many users have more than 100,000 and I've seen some with more than a million.

Old urls load very slow like 2 or 3 minutes to open.

There is no difference between "old" URLs and new ones, they can't be slower or faster just because they are old. The question is how much power has your server to manage what sh404SEF does. One important thing is not how old URLs are (once they are in the database, they can be read as fast as possible), but how many links are on a page. If you have pages with hundreds of links on them, then these can take a long time (but not 2-3 minutes, unless your server is really slow). This is, of course, assuming that sh404SEF is the actual cause for this problem.

Rgds

Friday, 22 December 2017 05:34 UTC

system

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.