Answer the question
In order to leave comments, you need to log in
What is the normal-optimal site loading speed?
Greetings!
Tell me how long the page of the site should load, for example, the main one. It is the most optimal time - of course, that the sooner the better.
On my site it shows 1 second on average. I look at pr-cy.ru/speed_test
Answer the question
In order to leave comments, you need to log in
If suddenly someone sees this question and answers in 2020-2021, then know.
Your site is fast if it loads from 0 to 3 seconds.
Page weight should not exceed 1000 kilobytes.
The number of HTTP requests from 50 to 100 per page.
How to measure all this. The main thing is not to measure in one service. There are a lot of them now.
Here I described them all:
https :
//vc.ru/services/72263-20-instrumentov-dlya -... loading.express - there will be a squeeze quickly and briefly.
Then I measure in https://www.webpagetest.org/ to understand the weight of the page and how many requests.
Well, in the end I look at Google PageSpeed Insights.
Site speed strongly depends on the amount of content on the page: text, pictures, videos, maps, etc.
Several good articles on this topic:
https://devaka.ru/articles/pagespeed-tools
https://habrahabr.ru/ company/hosting-cafe/blog/324504/
https://www.sparta-marketing.com/blog/13-sposobov-...
Most often, the user experience is affected not by how fast your scripts run (unless, of course, there is a frankly incorrect interaction with the database), but by the fact how the frontend loads. The guys from Yahoo figured out this issue well
https://developer.yahoo.com/performance/rules.html (in
Russian webo.in/articles/habrahabr/15-yahoo-best-practices )
will allow you not to think about how it is loaded.
150 ms if memory serves, there is approximately a packet from Europe to America. Within 100 ms per page generation is considered normal in all Yandex and Mail.ru. Total 0.4 sec per request. Plus, after that, you still have to load CSS, images and JS. This is done in parallel - a total of 0.7 seconds is OK. If more, then you need to figure out what you are running into.
Don't look at the average. Average means nothing . You need to look only at the worst time in this case. Or at least percentiles.
The faster the better, that's all. Well, again, there is a subjective assessment.
Check your site for example here . There you can also see recommendations for acceleration.
toster.ru shows 3-7 seconds.
What kind of nonsense?.. How do you measure time? Just do not say that this is the response time of the site to localhost.
In fact: connecting (sending and returning a request) via http takes an average of 2 seconds. The rest of the time is actually spent processing the request by the server. Drawing on the client can be neglected, because it is very short in time. The request processing time on the server depends directly on the load on the server (linear dependence).
You need to get the average execution time of scripts (for example, using tracing) multiplied by the expected load of requests per second and add 2 seconds. As a result, you will get the response time to the request in real conditions. If it is within 4 seconds, then it is quite acceptable.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question