There are plenty of use cases where a WordPress search function makes sense. In an online shop like Amazon, for example, hardly anyone will go through the individual categories to find something suitable. Rather, he will not search too specifically for product names or keywords. A search also makes sense on large websites, after all there are countless articles that are older but no less worth reading.
In a portfolio, a company website or similar publications, however, the search seems to be superfluous. After all, users should not be able to search freely here, but rather be redirected to the CTA and the subsequent conversion. A search function is therefore rather counterproductive in such examples.
You should also not underestimate the performance of the search. A search query always goes through the database of your WordPress blog and back again. Because the terms of a search are also very different, the WordPress search function is often an exception in the cache. Apart from the fact that all this depresses performance, WordPress search is often a vulnerability that can be actively exploited in attacks. The search therefore does not help performance in any case.
These are all reasons why I like to recommend that my customers disable the search function or set up a separate search plugin. In my article 8 WordPress search plugins for a better search function I will tell you a little more about it. So if you are interested, the post is the perfect complement to continue reading.