Forums Forums Search & Filter Pro Result load speed

Tagged: 

Viewing 6 posts - 1 through 6 (of 6 total)
  • Anonymous
    #269331

    Hi, how can I change load speed? When page loads, you need to wait couple seconds to see results. How see results instantly?

    See: http://mobont.lt/namai/

    Trevor
    #269385

    I do not think the speed could be improved much, as the results are being loaded using JavaScript and have to make direct calls to your database. The only improvement you could possibly make is to have a server highly optimized for speed in this type of operation.

    Traditional hosting servers are frequently not configured to handle the data requests between the CPU, various caches and the disk drive. This is not a criticism of such hosting, they meet a need for most users. But, when you are performing searches, you may need to consider (potentially) more expensive hosting if you wish/need to avoid the speed/response issues. I am loath to make recommendations, but can, privately, if you wish. There is only one specialist who operate at the very top end of performance though, and, not unexpectedly, they are also not inexpensive. That would be Kinsta.

    Because search results are dynamic, using a CDN for the results pages will also slow the process down, as they will not have a cache of the particular results requested.

    Anonymous
    #275807

    But server is normal, I try other server, other sites working perfect. Maybe in some way, I can improve load speed? Because it’s not normal..

    Trevor
    #275809

    Other than using caches and other server speed enhancements (such as memcache), there is nothing within our plugin that can be changed to make it faster, sorry.

    Anonymous
    #276735

    1 year later same issue here ! I think there is a problem with speed.
    My whole site and the 60 blocks load super fast but it is your filter that is slow.
    If everything loads so fast why would filter results make it slower?
    Well very disappointed 😔

    Trevor
    #276737

    I replied to your ticket in our support area, but I will copy that reply here also.

    The other content you mention is static, and so can be held in cache. However, search results have to be made using read/writes with your server hard drives, and this is where the bottleneck will be. Cached content will not have to do this, and so will be much faster.

    There is no way to avoid this where you have dynamic (uncached) content.

Viewing 6 posts - 1 through 6 (of 6 total)