7.5 sec in total
945 ms
6.5 sec
115 ms
Visit sorokin.ru now to see the best up-to-date Sorokin content for Russia and also check out these interesting facts you probably never knew about sorokin.ru
Купить
Visit sorokin.ruWe analyzed Sorokin.ru page load time and found that the first response time was 945 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
sorokin.ru performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value9.0 s
1/100
25%
Value6.1 s
45/100
10%
Value2,010 ms
7/100
30%
Value0.484
17/100
15%
Value12.7 s
14/100
10%
945 ms
287 ms
384 ms
520 ms
386 ms
Our browser made a total of 194 requests to load all elements on the main page. We found that 93% of them (181 requests) were addressed to the original Sorokin.ru, 2% (3 requests) were made to Code.jivo.ru and 2% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Sorokin.ru.
Page size can be reduced by 113.1 kB (2%)
4.7 MB
4.5 MB
In fact, the total size of Sorokin.ru main page is 4.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 4.1 MB which makes up the majority of the site volume.
Potential reduce by 108.5 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 108.5 kB or 88% of the original size.
Potential reduce by 804 B
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Sorokin images are well optimized though.
Potential reduce by 2.1 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.
Potential reduce by 1.7 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Sorokin.ru has all CSS files already compressed.
Number of requests can be reduced by 25 (13%)
188
163
The browser has sent 188 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sorokin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.sorokin.ru
945 ms
script.min.js
287 ms
bootstrap-treeview.min.css
384 ms
bootstrap.min.css
520 ms
jasny-bootstrap.min.css
386 ms
bootstrap-select.min.css
394 ms
turntable.min.css
395 ms
font-awesome.min.css
420 ms
style.css
513 ms
bootstrap.min.js
516 ms
bootstrap-treeview.min.js
556 ms
jasny-bootstrap.min.js
557 ms
filterForTable.min.js
558 ms
bootstrap-select.js
644 ms
bootstrap3-typeahead.min.js
642 ms
turntable.min.js
646 ms
723 ms
CatCard.js
657 ms
main_menu.js
679 ms
jquery.rwdImageMaps.min.js
770 ms
js
46 ms
owl.carousel.css
776 ms
owl.theme.css
776 ms
owl.carousel.min.js
788 ms
QYtTmi8nyy
321 ms
close.png
278 ms
loading.gif
320 ms
prev.png
364 ms
next.png
370 ms
logo_onred.svg
371 ms
C.svg
386 ms
73.jpg
681 ms
68.jpg
1364 ms
67.jpg
871 ms
69.jpg
1071 ms
65.jpg
1072 ms
46.jpg
1434 ms
56.jpg
947 ms
48.jpg
1253 ms
28.180.jpg
1078 ms
28.180-11.jpg
1133 ms
28.180-13.jpg
1136 ms
28.180-16.jpg
1209 ms
28.180-18.jpg
1259 ms
28.180-20.jpg
1263 ms
28.180-22.jpg
1344 ms
24.13.jpg
1379 ms
tag.js
973 ms
24.13-11.jpg
1370 ms
24.13-15.jpg
1372 ms
24.13-20.jpg
1456 ms
24.13-25.jpg
1439 ms
KFOmCnqEu92Fr1Mu5mxP.ttf
21 ms
KFOlCnqEu92Fr1MmSU5fABc9.ttf
26 ms
KFOlCnqEu92Fr1MmYUtfABc9.ttf
29 ms
glyphicons-halflings-regular.woff
1422 ms
24.13-30.jpg
1407 ms
24.13-35.jpg
1409 ms
24.13-38.jpg
1444 ms
24.13-42.jpg
1464 ms
24.13-70.jpg
1479 ms
24.13-80.jpg
1429 ms
24.13-99.jpg
1422 ms
35.802.jpg
1412 ms
35.802-10.jpg
1438 ms
QYtTmi8nyy
179 ms
fontawesome-webfont.woff
1479 ms
35.802-11.jpg
1467 ms
16.134.jpg
1429 ms
16.134-03.jpg
1423 ms
16.134-06.jpg
1424 ms
16.134-11.jpg
1443 ms
QYtTmi8nyy
622 ms
1
420 ms
16.134-22.jpg
1205 ms
16.134-26.jpg
1042 ms
16.58.jpg
979 ms
24.185.jpg
857 ms
24.185-35.jpg
852 ms
advert.gif
733 ms
24.185-38.jpg
881 ms
24.185-50.jpg
883 ms
24.185-60.jpg
902 ms
27.410.jpg
847 ms
27.410-11.jpg
801 ms
27.410-20.jpg
796 ms
27.410-88.jpg
826 ms
27.410-95.jpg
806 ms
35.830.jpg
805 ms
35.830-13.jpg
802 ms
35.830-14.jpg
797 ms
35.830-15.jpg
797 ms
35.830-25.jpg
789 ms
35.830-77.jpg
809 ms
35.400.jpg
800 ms
35.400-3.jpg
795 ms
35.400-5.jpg
793 ms
35.400-6.jpg
788 ms
35.400-7.jpg
788 ms
11.205.jpg
806 ms
16.115.jpg
764 ms
16.115-11.jpg
774 ms
16.115-15.jpg
773 ms
16.115-22.jpg
784 ms
1.340.jpg
788 ms
1.340-11.jpg
787 ms
sync_cookie_image_decide
185 ms
28.67.jpg
765 ms
28.67-0.jpg
774 ms
28.67-5.jpg
774 ms
33.44.jpg
787 ms
33.44-01.jpg
788 ms
33.44-02.jpg
791 ms
33.44-03.jpg
765 ms
33.44-04.jpg
766 ms
33.44-05.jpg
765 ms
33.44-06.jpg
785 ms
33.44-07.jpg
789 ms
33.44-08.jpg
790 ms
33.44-09.jpg
765 ms
33.44-11.jpg
764 ms
33.44-12.jpg
764 ms
33.44-17.jpg
787 ms
33.44-18.jpg
789 ms
1
142 ms
33.44-993.jpg
781 ms
33.44-996.jpg
770 ms
33.44-998.jpg
764 ms
33.44-999.jpg
764 ms
33.44-9.jpg
788 ms
3.694.jpg
788 ms
3.694-0.jpg
772 ms
3.694-1.jpg
774 ms
3.694-2.jpg
763 ms
3.694-3.jpg
764 ms
27.400.jpg
788 ms
27.400-11.jpg
788 ms
27.400-14.jpg
774 ms
27.400-17.jpg
778 ms
27.400-20.jpg
764 ms
27.400-23.jpg
763 ms
10.8.jpg
788 ms
10.8-0.jpg
788 ms
7.111.jpg
769 ms
7.111-11.jpg
788 ms
7.111-13.jpg
769 ms
7.111-15.jpg
770 ms
7.111-17.jpg
788 ms
7.111-19.jpg
788 ms
7.111-25.jpg
766 ms
7.111-27.jpg
786 ms
7.111-30.jpg
770 ms
7.111-40.jpg
774 ms
3.623.jpg
787 ms
3.623-22.jpg
787 ms
3.623-26.jpg
765 ms
3.623-30.jpg
784 ms
16.56.jpg
771 ms
16.56-11.jpg
777 ms
16.56-60.jpg
787 ms
16.56-70.jpg
788 ms
7.30.jpg
765 ms
7.30-12.jpg
780 ms
7.30-14.jpg
771 ms
7.30-17.jpg
781 ms
7.30-19.jpg
786 ms
7.30-77.jpg
789 ms
4.912.jpg
766 ms
4.912-5.jpg
777 ms
10.15.jpg
771 ms
27.90.jpg
785 ms
27.90-0.jpg
786 ms
27.90-1.jpg
796 ms
27.90-5.jpg
765 ms
27.90-6.jpg
773 ms
27.90-8.jpg
772 ms
9.64.jpg
788 ms
9.64-11.jpg
785 ms
9.64-15.jpg
796 ms
9.64-20.jpg
766 ms
3.700.jpg
764 ms
3.700-11.jpg
763 ms
3.700-30.jpg
785 ms
3.81.jpg
786 ms
3.81-22.jpg
795 ms
3.81-30.jpg
765 ms
3.81-32.jpg
764 ms
3.81-35.jpg
764 ms
3.81-40.jpg
800 ms
27.150.jpg
786 ms
27.150-0.jpg
795 ms
27.150-1.jpg
764 ms
27.150-2.jpg
763 ms
bundle_ru_RU.js
48 ms
sorokin.ru accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
sorokin.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
sorokin.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sorokin.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Sorokin.ru main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
sorokin.ru
Open Graph description is not detected on the main page of Sorokin. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: