Week performance in Runet
Some time ago, co-owner Openstat Leonid Filatov presented a report in one of the boarding houses of the Leningrad region in a narrow circle of hosting providers, which became a kind of feast for meta-analysis. We managed to combine a lot of heterogeneous data using the example of a topic that most webmasters and hosters care about - the performance (speed) of web pages on various hosting sites and depending on different engines.
An example of such a report.
')
As you can see, there is so much data that I want to do their decompression.
But first, a couple of paragraphs about how they are received.
One of their sources is the special developer interface adopted on December 17, 2012 - the Navigation Timing API. It provides access to a set of parameters characterizing the speed of loading and preparing a page for work — the time in milliseconds that has passed from the beginning of the epoch to a specific event. Based on it, Openstat provided a little more than a month for a new standard report, which allows to find out the performance of page rendering in real time and estimate the speed of page assembly for various users.
In addition to Openstat in the world there are several web analyst with similar functionality: New Relic, Google Analytics, Yandex. Metric, Piwik. They allow you to work with the performance of sites, as with the traces of people in the virtual space, in other words, with Big Data. Other tests, for example, the well-known WebPagetest, measure the speed of loading pages not for live visitors, but for programs that communicate with the server.
Another source of data is the crawler Openstat, which since last summer has been indexing the entire Runet, as well as Bynet, Uanet, and the sites of other domain zones where Russian users go in large numbers. The main purpose of this “spider” is to collect signatures of meters, advertising systems, online consultants and similar systems. But along the way, he captures the available tekhnometriki sites.
Crawler works with all second-level domains that give the answer "200", and the counter with all sites where it is installed. Therefore, meta-analysis using both tools was often carried out only for second-level domains.
However, the simplest report was received for a single, but very large, Runet site.
It is easy to guess that desktop browsers were faster than mobile (so this is not marked on the histogram specifically).
And if you think about this picture, then the first immature thoughts:
1. It is necessary that Yandex Browser was done with the goal (not counting the competitive struggle in the search market) to optimize the speed of loading pages, but it still does not surpass the competition!
2. The top three includes browsers for geeks, and already they have provided themselves and the last mile with good bandwidth.
But such conclusions are not rich in meaning, and Crome has long been a browser for everyone, since it is worth every fifth Internet user.
So here it is more appropriate to draw conclusions to analysts of a specific Internet resource.
And here is the first special study “performance dependence for 57 popular CMS”. A sample of 24 thousand sites. Results for May 2014. In April, tested 38 CMS and the top five was exactly the same, albeit with different values.
In the case of Bitrix, the speed depends on whether the site acceleration (CDN) service was used, as well as the “Composite site” technology. Such nuances were not tracked.
One of the central reports was in search of himself for a long time. Five times updated (in the sense of grouped) data on hosting providers. The selection criterion for the central slide was changed twice.
In the end, when choosing defendants, we stopped at statistics on the hosting providers StatOnline.ru (from there the shares in the group were also taken). And after rough calculations using Excel tools, the final report was generated using SQL tools.
And although there is no limit to perfection, you should treat the following diagram as data related to the actual situation in May 2014.
And a little bit about the vulnerability of hosting providers on the example of SSL certificates collected by the same Openstat crawler on second-level domains on port 443.
This completely separate study was conducted on the scale of the entire Runet (4.93 million domains). 1.6 million certificates were found, of which 760 thousand are self-signed; completely normal (status 200) - 4 thousand; vulnerable to Heartbleed (vulnerable version of OpenSSL) - 133 thousand (8%).
HeartBleed can be, if not already, the biggest information vulnerability at all.
According to Habrahabrow analysts, approximately â…“ of the Runet websites were vulnerable to this day. Exact calculation showed that this, to put it mildly, is not so.
"Week of performance in Runet" turned out to be non-calendar. It began on Friday, May 23, when at the Failover conference, Andrei Travin (Openstat) and Sergey Ryzhikov (1C-Bitrix) spoke about the performance of the sites - the first two reports. The first of these included the dependence of site performance on CMS for April. And Sergey had about his "Composite site".
On May 27, the same was succeeded in reporting to St. Petersburgites at the SPIK conference.
And on May 30, Leonid Filatov on “Host Review” showed the dependence of the speed of sites on the largest providers and at the same time on the CMS they use.
Almost at the same time, a Bitrix survey on the performance of 100 domestic online stores appeared, as if in response to a similar survey from 500 Radware stores.
You will have to rake the results obtained not only in June, but also in general before the autumn conferences.
An example of such a report.
')
As you can see, there is so much data that I want to do their decompression.
But first, a couple of paragraphs about how they are received.
One of their sources is the special developer interface adopted on December 17, 2012 - the Navigation Timing API. It provides access to a set of parameters characterizing the speed of loading and preparing a page for work — the time in milliseconds that has passed from the beginning of the epoch to a specific event. Based on it, Openstat provided a little more than a month for a new standard report, which allows to find out the performance of page rendering in real time and estimate the speed of page assembly for various users.
In addition to Openstat in the world there are several web analyst with similar functionality: New Relic, Google Analytics, Yandex. Metric, Piwik. They allow you to work with the performance of sites, as with the traces of people in the virtual space, in other words, with Big Data. Other tests, for example, the well-known WebPagetest, measure the speed of loading pages not for live visitors, but for programs that communicate with the server.
Another source of data is the crawler Openstat, which since last summer has been indexing the entire Runet, as well as Bynet, Uanet, and the sites of other domain zones where Russian users go in large numbers. The main purpose of this “spider” is to collect signatures of meters, advertising systems, online consultants and similar systems. But along the way, he captures the available tekhnometriki sites.
Crawler works with all second-level domains that give the answer "200", and the counter with all sites where it is installed. Therefore, meta-analysis using both tools was often carried out only for second-level domains.
However, the simplest report was received for a single, but very large, Runet site.
It is easy to guess that desktop browsers were faster than mobile (so this is not marked on the histogram specifically).
And if you think about this picture, then the first immature thoughts:
1. It is necessary that Yandex Browser was done with the goal (not counting the competitive struggle in the search market) to optimize the speed of loading pages, but it still does not surpass the competition!
2. The top three includes browsers for geeks, and already they have provided themselves and the last mile with good bandwidth.
But such conclusions are not rich in meaning, and Crome has long been a browser for everyone, since it is worth every fifth Internet user.
So here it is more appropriate to draw conclusions to analysts of a specific Internet resource.
And here is the first special study “performance dependence for 57 popular CMS”. A sample of 24 thousand sites. Results for May 2014. In April, tested 38 CMS and the top five was exactly the same, albeit with different values.
| Name CMS | Average, ms | Min., Ms | Max. Ms | Sites |
| A5 | 491 | 175 | 1213 | 7 |
| Melbis shop | 898 | 632 | 1462 | 7 |
| RBC Contents | 961 | 463 | 1377 | eight |
| ImageCMS | 980 | 437 | 1748 | five |
| Abo | 996 | 457 | 1834 | 12 |
| DJEM | 1130 | 901 | 1425 | 7 |
| Aquilon | 1183 | 961 | 1405 | 2 |
| Twilight | 1189 | 1024 | 1359 | 3 |
| TYPO3 | 1453 | 426 | 3708 | nineteen |
| S.Builder | 1474 | 281 | 3475 | eight |
| Taberna eCommerce | 1505 | 784 | 2482 | 3 |
In the case of Bitrix, the speed depends on whether the site acceleration (CDN) service was used, as well as the “Composite site” technology. Such nuances were not tracked.
One of the central reports was in search of himself for a long time. Five times updated (in the sense of grouped) data on hosting providers. The selection criterion for the central slide was changed twice.
In the end, when choosing defendants, we stopped at statistics on the hosting providers StatOnline.ru (from there the shares in the group were also taken). And after rough calculations using Excel tools, the final report was generated using SQL tools.
And although there is no limit to perfection, you should treat the following diagram as data related to the actual situation in May 2014.
| organization | bitrix | drupal | joomla | setup_en | dle | wordpress | ucoz |
| Agava | 1541 | 1444 | 2230 | 2422 | 3313 | ||
| Beget | 2023 | 2684 | 2949 | 4093 | 3967 | ||
| Compubyte Limited | 4662 | ||||||
| FirstVDS | 2163 | 2384 | 2846 | 3667 | 3679 | ||
| Garant-park-telecom | 1404 | 2885 | 2030 | 2203 | 3430 | ||
| Hetzner | 2861 | 2591 | 2990 | 4228 | 4213 | ||
| Hosting Telesystems network | 2245 | 3918 | 2681 | 4865 | 2636 | ||
| Insolve | 1397 | 2036 | 2576 | 4116 | 2205 | ||
| Infobox | 1859 | 1493 | 6970 | 2636 | 2857 | ||
| Jino avguro | 1779 | 4746 | 3271 | 4714 | 4966 | ||
| LeaseWeb | 1814 | 2459 | 2775 | 4075 | 3512 | ||
| Majordomo | 1812 | 2806 | 2776 | 3788 | 4640 | ||
| McHost.RU | 1518 | 13923 | 2846 | 3598 | 4456 | ||
| RU-CENTER | 980 | ||||||
| RU-NIC | 2476 | 2836 | 2747 | 4964 | 3615 | ||
| Reg.Ru | 1753 | 1658 | 2633 | 3359 | 4855 | ||
| SEDO Parking | |||||||
| SPRINTHOST.RU | 1047 | 2210 | 2723 | 5847 | 6091 | ||
| Setup.ru | 3499 | ||||||
| Spaceweb | 1815 | 1740 | 2301 | 2494 | 3126 | ||
| Timeweb | 1719 | 2183 | 2949 | 2520 | 4390 | ||
| ihc.ru | 2043 | 1649 | 2502 | 3217 | 3562 | ||
| masterhost | 2179 | 1702 | 2178 | 2631 | 2751 |
And a little bit about the vulnerability of hosting providers on the example of SSL certificates collected by the same Openstat crawler on second-level domains on port 443.
This completely separate study was conducted on the scale of the entire Runet (4.93 million domains). 1.6 million certificates were found, of which 760 thousand are self-signed; completely normal (status 200) - 4 thousand; vulnerable to Heartbleed (vulnerable version of OpenSSL) - 133 thousand (8%).
HeartBleed can be, if not already, the biggest information vulnerability at all.
According to Habrahabrow analysts, approximately â…“ of the Runet websites were vulnerable to this day. Exact calculation showed that this, to put it mildly, is not so.
| org | cnt |
| FirstVDS | 49248 |
| Reg.Ru | 14838 |
| Hetzner | 12279 |
| Not determined | 9231 |
| Majordomo | 6220 |
| LeaseWeb | 3359 |
| Closed Joint Stock Company "RuWeb" | 3274 |
| SIA “Network of data-centers“ Selectel ” | 2027 |
| Timeweb | 2016 |
| E-Planet Hosting Provider | 1651 |
| masterhost | 1614 |
"Week of performance in Runet" turned out to be non-calendar. It began on Friday, May 23, when at the Failover conference, Andrei Travin (Openstat) and Sergey Ryzhikov (1C-Bitrix) spoke about the performance of the sites - the first two reports. The first of these included the dependence of site performance on CMS for April. And Sergey had about his "Composite site".
On May 27, the same was succeeded in reporting to St. Petersburgites at the SPIK conference.
And on May 30, Leonid Filatov on “Host Review” showed the dependence of the speed of sites on the largest providers and at the same time on the CMS they use.
Almost at the same time, a Bitrix survey on the performance of 100 domestic online stores appeared, as if in response to a similar survey from 500 Radware stores.
You will have to rake the results obtained not only in June, but also in general before the autumn conferences.
Source: https://habr.com/ru/post/225267/
All Articles