By requests per second or request per minute I mean the clicking on a link and the loading of a complete new page, or any kind of request a user often makes on a social networking website.
Not sure if bounce rate is the right metric.
You might want to look at "Actions Per Minute" by each user of the website. This metric varies largely by the domain one is in - games, webapp, social network - all have different actions. The other dimension that you will also need to consider is how many requests are made by the client (browser) on behalf of the user. An AJAX / Long Polling / Asynchronous Request based app might be going a lot more requests on behalf of the user even without any user interaction.
Assuming each scroll makes a call to the webservice and considering that the scroll might happen every 30 secs to 1 minute, you are looking a 2 reqs per user per min. If you already have a website doing something similar, that would be a great metric to follow.
For instance, in one of our apps, with 1000 people online on a website, but few playing games, others just browsing, the requests we saw were just a fraction - ~5 - 10 reqs per second. But again, your mileage may vary.
Atul Sharma
Full Stack Developer | Cloud Native Applications
It depends upon the bounce rate (How much time the user spends on website before closing the website or opening another). A bounce rate of 25 Sec means on average user will spend min of 25 sec on website.
So, 30,000 hits a minute with 25 sec of bounce rate mean an Average of 15,000 users online at any particular moment.
Time consumed while the website is loaded into the browser can be neglected once you consider bounce rate.