The load test result does not match the http request number limit in the web application, it simply indicates that the load test tool simulates these requests per second. The test result may be affected by the simultaneous customer number, App service plan level, number of instances and URLs, etc.
Here is the test result (web application with S1 application service plan, 250 simultaneous clients, URL on a static html page)

CPU and memory usage

From the above screenshots, we could find that it just uses a little CPU and memory resources during the load testing. And the result of 226.49 req / sec is not the actual maximum number of queries that the web application can process.
Also, if the App Service plan you are using now cannot meet the requirements of your application, try scaling up the App Service plan .
source share