Let me say right away that my internet is fine, and my phone runs Snapdragon 8 Elite.
This is often very annoying, I press the button, but it doesn’t work and sometimes even resets or then asks for a captcha, the search works very slowly, so much so that the button and the keyboard do not close…
*I did this for a video, but even with normal use, the search button is very slow and poorly functioning.
I actually rarely use search, but every time it’s unbearable, even those couple of seconds when the keyboard seems unresponsive or even resets, turns me off using Brave search.
@Funduk What your video shows is that everything responds quickly at first, then starts slowing down once you begin rapidly firing off requests. Even your DuckDuckGo comparison starts to struggle at the same point, right after the request volume spikes.
That pattern is expected. From the website’s perspective, this does not look like normal use. It looks like sustained strain rather than genuine interaction with the content. In practical terms, what you are triggering is:
Search flooding, repeatedly hitting a search engine with queries until it slows down, rate-limits, or temporarily blocks access.
Rate-limit abuse, which is how the service itself would describe exceeding allowed request thresholds and triggering delays or captchas.
Denial-of-service-like behavior, informally speaking, where the effect is overwhelming the service even if it is not a formal DoS attack.
When requests are sent continuously without allowing time to process or even read the responses, throttling is the normal and expected outcome. The slowdown is not a failure of the search engine, it is the system doing exactly what it is designed to do under that kind of load.
I did this for a video, but even with normal use, the search button is very slow and poorly functioning.
I actually rarely use search, but every time it’s unbearable, even those couple of seconds when the keyboard seems unresponsive or even resets, turns me off using Brave search.
