October 28, 2014 at 08:15Control the speed of your site
We bring to your attention a new function of the service "HostTracker - Monitoring Response Time" . This value, like uptime, is also very important. Everyone knows from personal experience how annoying the long page loading is. Therefore, website optimization is now paying more and more time. And the first step to fixing the problem is to detect it.
You can distinguish certain time intervals and labels associated with the transfer protocol:
1. DNS location time - how quickly the physical address is located by the domain name of the site.
2. Connection time - how long it takes for the request to reach the web server and be processed there.
3. Download start time - how quickly the site starts loading.
4. Download end time - it depends on how fast this download takes place.
Sites that use SSL also require additional time for authentication.
All this together makes up the response time. Each of these points, under certain circumstances, may be a “weak link”.
Site response time depends on many things. Long loading may be due to both the site and hosting.
1. Third party scripts used on the site. These can be various buttons and information collection services that cause javascript at each load. And although the most advanced services, such as Google Analytics, do this asynchronously and practically do not affect the load time, many of these services can significantly increase the page load time.
2. Information from third sources. First of all, a variety of multimedia files that are stored in some kind of file storage. You can optimize by choosing the most suitable file storage service for use.
3. Actually, problems with the site itself. As a rule, these are either problems with the site logic (as an option - an unsuccessful choice of technology for the implementation of a specific task), or with loaded data from local repositories (for example, a database). In the case of the database, this issue is solved by optimizing the database queries, which is a separate huge topic.
1. DNS - the time taken for the site to “stay” on the network depends on the choice of DNS servers.
2. The location of the data center also plays a role. It is advisable to choose a hosting that is closer to the main audience. But “closer” does not always mean territorially; it concerns more the network infrastructure scheme in your region of the world. If the site is positioned as a global resource, then the solution may be to use CDN (content delivery network). Currently, there are also a number of interesting cloud solutions to this issue.
3. The quality of the services provided. If monitoring shows frequent timeouts or disconnections, which the hosting support does not explain in any way, this is only the tip of the iceberg. At other times, a site that seems to be working can load extremely slowly for a large number of customers, which will negatively affect the number of subscriptions.
It consists in setting an additional parameter - timeout - when creating a task.
This is a critical value, exceeding which leads to the generation of alerts. Thus, it is possible to track not only the fall of the site, but also the time periods when it “slows down”. Statistics and audit history are saved and presented in a convenient form, as in the figure above.
What is the response time?
You can distinguish certain time intervals and labels associated with the transfer protocol:
1. DNS location time - how quickly the physical address is located by the domain name of the site.
2. Connection time - how long it takes for the request to reach the web server and be processed there.
3. Download start time - how quickly the site starts loading.
4. Download end time - it depends on how fast this download takes place.
Sites that use SSL also require additional time for authentication.
All this together makes up the response time. Each of these points, under certain circumstances, may be a “weak link”.
What exactly can “slow down” a site?
Site response time depends on many things. Long loading may be due to both the site and hosting.
If the site itself slows down, then the reasons are as follows:
1. Third party scripts used on the site. These can be various buttons and information collection services that cause javascript at each load. And although the most advanced services, such as Google Analytics, do this asynchronously and practically do not affect the load time, many of these services can significantly increase the page load time.
2. Information from third sources. First of all, a variety of multimedia files that are stored in some kind of file storage. You can optimize by choosing the most suitable file storage service for use.
3. Actually, problems with the site itself. As a rule, these are either problems with the site logic (as an option - an unsuccessful choice of technology for the implementation of a specific task), or with loaded data from local repositories (for example, a database). In the case of the database, this issue is solved by optimizing the database queries, which is a separate huge topic.
There may also be a number of questions regarding hosting:
1. DNS - the time taken for the site to “stay” on the network depends on the choice of DNS servers.
2. The location of the data center also plays a role. It is advisable to choose a hosting that is closer to the main audience. But “closer” does not always mean territorially; it concerns more the network infrastructure scheme in your region of the world. If the site is positioned as a global resource, then the solution may be to use CDN (content delivery network). Currently, there are also a number of interesting cloud solutions to this issue.
3. The quality of the services provided. If monitoring shows frequent timeouts or disconnections, which the hosting support does not explain in any way, this is only the tip of the iceberg. At other times, a site that seems to be working can load extremely slowly for a large number of customers, which will negatively affect the number of subscriptions.
Monitoring Monitoring HostTracker
It consists in setting an additional parameter - timeout - when creating a task.
This is a critical value, exceeding which leads to the generation of alerts. Thus, it is possible to track not only the fall of the site, but also the time periods when it “slows down”. Statistics and audit history are saved and presented in a convenient form, as in the figure above.