Have the most frequent searches been investigated and submited so that they are either cached or displayed to the user without sending unnecessary requests or clicks. ?
Is a list of the most requested services and "fail requests" provided? are the "power requests" specified?
Internat search engines usage in the service allow users to access information faster by limiting browsing on the service. These search engines are therefore an asset from the point of view of environmental efficiency and user assistance. On the other hand, they may not have all the answers and rely on remote resources that are expensive to consult. It is important to reduce the exchanges between your service and the remote servers so as not to cancel out the benefits acquired by the use of the search engine.
6 other criteria related to the recommendation: "Barebone Iteration": Iterate your solution until minimalism "acceptable" by your users
Is a systemic approach method implemented, handled by the actors and associated with tools ?
Has the solution been prototyped upstream, with the user journey and interactions ?
Have user's behavior and feedback been examined to best meet their needs ?
Is the design documented (functionally and technically), the design deliverables must be comprehensible by the project team and transferable to the development team ?
Is the path taken to access the service as quick and as simple as possible ?
Has a continuous improvement process been deployed ?