We know if the content is heavy in website then it will take a much time than website having content in lower.
Suppose, if we have 1mb page size then the site will load slower than the page size having 1kb.
But I am trying to understand how can we consider the loading speed if the page size is just 1kb and url is hit by millions of user simultaneously.
Hitting url by one user will be faster enough. But hitting the same url simultaneously by millions of user will be time consuming?
Here I would like to know if the speed depends on page size or it also depends the url hit by simultaneous users.
I use the tool from Google - thinkwithgoogle.com/intl/en-gb/feature/testmysite But it can't do a proper test for millions simultaneous connections of course
Bruce
CEO
"But hitting the same url simultaneously by millions of user will be time consuming?"
Oh, yes, indeedy! It's the entire basis for DDoS attacks.
Yes, page speed depends on your page size as well as no. simultaneous users.
Each client has a bandwidth. So if your page size is high, the client will take some time to download all. Suggestion: Try to optimize images, css, js, everything you have
Each server has a limit on processor and ram. For every request, resources like this are used. Each server has an RPS - requests per second, it can handle. As soon as RSP increases, the server become busier and will be slow to send responses Suggestion: Do horizontal scaling
Both, but it's not that easy to just take those two values into account. Basically, the page size determines how much traffic the user is creating. Example given: page size is 1kb and 1 million users accessing your website. Means your server has to deliver about 1 GB (1kb * 1000000 users) at the same time. If your server only can deliver let's say 250 MB per second it takes at least 4 seconds to deliver the whole page to all users (very simple calculation here). However, it's more important to know how many concurrent users the server itself is able to handle. Usually and with default configuration the most setups can deliver between a few hundred to a few thousand responses per second (example: help.dreamhost.com/hc/en-us/articles/215945987-We…). Let's say your server is able to serve your site to 5000 users at the same time. That means that it takes at least 200 seconds (1000000 / 5000) to server everything, because only the first 5000 users will get an answer, all others have to wait in line for the page.
Another more important metric you should take into account is the time it takes for your server to respond to a user request, also known as TTF (time to first byte). It could be described as the delay between your server getting the user request and the start of the delivery of the website. This time should be as low as possible but usually takes a few dozen to a few hundred milliseconds. This delay pushes the users waiting in line even further because for the time of the delay the server is not able to process any new user.
But, if you speak of such a high user amount you have to build a better infrastructure with load balancing and multiple servers responding to your users, as one server will not be enough.
Sharma Manish
If you want to consider website speed . you can check following factors: Factors That Affect Website Speed Connection Speed. The type of internet connection you have will directly affect the speed at which any website loads. ... Server/Hosting. ... File Types and Sizes. ... Plugins Browser PC Cache Traffic Volume Checking your website speed. There are many tools to check website speed with following tools. Website Speed Concepts. List of Website Speed Test Tools. KeyCDN Website Speed Test. Google PageSpeed Insights. Pingdom Speed Test. GTmetrix. WebPageTest.
But i will recommended Google PageSpeed Insights tools. There are many website developers use this tool to consider website speed.