15.6 sec in total
462 ms
14.5 sec
605 ms
Click here to check amazing Rusch content for Russia. Otherwise, check out these important facts you probably never knew about rusch.ru
Туристическая компания "Русь-Тревел" предлагает разнообразный отдых в Росии и за рубежом. Выгодные цены и различные акции, обращайтесь, мы подберем Вам тур по вашему желанию
Visit rusch.ruWe analyzed Rusch.ru page load time and found that the first response time was 462 ms and then it took 15.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
rusch.ru performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value8.2 s
2/100
25%
Value12.1 s
4/100
10%
Value5,250 ms
0/100
30%
Value0.142
78/100
15%
Value24.1 s
0/100
10%
462 ms
895 ms
41 ms
115 ms
56 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 85% of them (82 requests) were addressed to the original Rusch.ru, 3% (3 requests) were made to Fonts.googleapis.com and 2% (2 requests) were made to Tourvisor.ru. The less responsive or slowest element that took the longest time to load (11.9 sec) belongs to the original domain Rusch.ru.
Page size can be reduced by 350.9 kB (5%)
7.4 MB
7.0 MB
In fact, the total size of Rusch.ru main page is 7.4 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. 65% of websites need less resources to load. Images take 6.7 MB which makes up the majority of the site volume.
Potential reduce by 41.2 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 41.2 kB or 74% of the original size.
Potential reduce by 281.0 kB
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. Rusch images are well optimized though.
Potential reduce by 23.0 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 5.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. Rusch.ru has all CSS files already compressed.
Number of requests can be reduced by 42 (49%)
86
44
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rusch. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
rusch.ru
462 ms
www.rusch.ru
895 ms
css
41 ms
styles.css
115 ms
css
56 ms
font-awesome.min.css
230 ms
slick.css
324 ms
slick-theme.css
324 ms
owl.carousel.min.css
326 ms
owl.theme.default.min.css
334 ms
all.css
353 ms
jquery.fancybox.css
430 ms
jquery-1.8.0.js
33 ms
jquery.fancybox-1.2.1.pack.js
431 ms
superfish.js
434 ms
jquery.flexslider-min.js
444 ms
jquery.easing.1.3.js
463 ms
jquery.elastislide.js
538 ms
jquery.ui.totop.js
538 ms
scripts.js
541 ms
jquery.jqtransform.js
555 ms
masked.input.js
575 ms
jquery.anythingslider.js
645 ms
slick.js
758 ms
owl.carousel.min.js
652 ms
ui.design-tokens.min.css
668 ms
ui.font.opensans.min.css
685 ms
main.popup.bundle.min.css
754 ms
page_0f232b7913a6a3603502d5fbd7d7319e_v1.css
765 ms
template_8e0c8b65a0258a73dd02e0cbfe10a4a6_v1.css
779 ms
core.min.js
913 ms
main.popup.bundle.min.js
865 ms
page_44b1e0713bc989fb3e3aa5ae8638372c_v1.js
866 ms
init.js
685 ms
reset.css
764 ms
skeletons.css
782 ms
superfish.css
863 ms
forms.css
867 ms
flexslider.css
872 ms
ui.totop.css
892 ms
css
19 ms
ba.js
287 ms
gtm.js
70 ms
039cd5a354c4c041f1c32e0ceaf2b7ba.jpg
226 ms
icon-vk.png
115 ms
icon-ok.png
116 ms
icon-fb.png
115 ms
insta.png
116 ms
3d4416a0d953d3f8159f0d124c0fc24d.png
218 ms
e77fc52366b846aa3f6c593482479037.png
218 ms
dfa72cd51cc3e7a106dc09eb3ee6d815.jpg
542 ms
b52e2daf93943fe3cff0effcb0873333.jpg
891 ms
6e876b19f26da01ec56c51f2b67425cc.jpg
540 ms
1761a5acedb1b7b629ac9ec786f77000.jpg
539 ms
5978485c1b68245a41bf2c906ec9c495.jpg
687 ms
957853eb7bbc13a07e8fbe2c2ee5add5.jpg
11937 ms
4a4a9aac721fdecdb4a23d07b638aa18.jpeg
754 ms
dde3578cbe0a20e647410f916f78c5ea.jpeg
686 ms
f3675b2b1975d3f40ea850be53dd35fb.jpeg
686 ms
f9028bc9ad96cb2071d8da296b2654fa.jpg
758 ms
a2314291f98db042def7381153af2a30.jpeg
762 ms
c50927d27b1ae506e44adfa7efe952c5.png
893 ms
bfcb52c4ef9b1618c7bdff44f708ea23.jpg
863 ms
a921b8e5fd11da96c180c812c5f75690.jpg
865 ms
0ad8c17d3f28d46e91555c722f39a669.jpg
874 ms
72f6480dd51127e2741fdc9c099eb907.jpg
1078 ms
logotip.jpg
973 ms
logo_prural.png
983 ms
BngRUXNadjH0qYEzV7ab-oWlsbCLwRs.woff
59 ms
BngRUXNadjH0qYEzV7ab-oWlsbCGwRs.woff
60 ms
core.min.js
617 ms
border-horiz1.gif
970 ms
d038b0a7a2c4130199258ab7bbe67ea8.jpg
974 ms
208bd4dc37b50ef091b57e6c8196783e.jpeg
1159 ms
5c7fcb6e0168386c7ff0868b3ffdca1f.jpg
1061 ms
0faa4c805e227f8c296173e916308bf3.jpg
1081 ms
c67a12e4427d8c007888ced965b49b5c.jpeg
1196 ms
3a083494b25f5b225dc22e9f3270c83c.jpg
1154 ms
f69e6692b340d4d9309d70517f4b6972.jpg
1172 ms
vlnvq63kou55vqglx3x47le7gzw03ws3.jpg
1194 ms
dc3389237ea6affdab5ba18ad5b39c27.jpg
1262 ms
87fc0d3336dadce80a2039bb24432b0a.jpg
1267 ms
watch.js
19 ms
fa-v4compatibility.ttf
1203 ms
fa-regular-400.ttf
1228 ms
fa-brands-400.ttf
1231 ms
fa-solid-900.ttf
1291 ms
fontawesome-webfont.woff
1196 ms
c3935afc2526682f95d4dfb4d11d5e25.jpg
1210 ms
7bqmbfeufe4tg20b1lj2upu4uh9su4ix.jpg
1341 ms
bx_stat
184 ms
marker-1.png
918 ms
openapi.a2ed73393cad04481c1dfb3f7794921f.js
232 ms
rtrg
133 ms
qebbMnZtMN
193 ms
prev.png
112 ms
next.png
109 ms
rusch.ru accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
rusch.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
rusch.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 Rusch.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 Rusch.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.
rusch.ru
Open Graph description is not detected on the main page of Rusch. 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: