Search bar optimization - by Shezad - on WordPress WooCommerce support

This topic has 4 replies, 2 voices, and was last updated 2 years, 10 months ago ago by Olga Barlow

  • Avatar: Shezad
    Shezad
    Participant
    July 5, 2021 at 22:11

    Hello,

    I am having an issue with the search bar taking awhile to display results of a search. If I type something like “iphone” into the search bar, the magnifying glass spins for quite sometime before displaying results. I wanted to speed up the user’s search options and only wanted to use search by product name as an option (do not need to search by sku or any other methods)

    Please, contact administrator
    for this information.
    3 Answers
    Avatar: Olga Barlow
    Olga Barlow
    Support staff
    July 6, 2021 at 14:09

    Hello,

    1) That animation appears if Ajax search option is enabled and system searches results to display in the Ajax search window. If you don’t need Ajax search you can disable it in the Search element settings.
    2) Go to Theme Options > Header builder > Search > keep Search by SKU disabled if you don’t need that https://prnt.sc/190pv06 Also you can disable search by posts if you don’t need that.

    Regards

    Avatar: Shezad
    Shezad
    Participant
    July 6, 2021 at 19:38

    Hello,

    1) I do need some sort of drop down option, but I was wondering if it is possible to only search by the product name and not by anything else (basically filter everything else out so that there is less to search, and therefore reduce the search time overall).
    2) I have disabled the search by posts as well, it makes a very small difference.

    Avatar: Olga Barlow
    Olga Barlow
    Support staff
    July 7, 2021 at 14:32

    Hello,

    1) If you disable all the other additional options (search by posts, by sku etc) then it searches by product title and description only, like default WooCommerce search.

    Regards

  • Viewing 4 results - 1 through 4 (of 4 total)

The issue related to '‘search bar optimization’' has been successfully resolved, and the topic is now closed for further responses

We're using our own and third-party cookies to improve your experience and our website. Keep on browsing to accept our cookie policy.