7.9 sec in total
340 ms
6.9 sec
735 ms
Visit 2r.ru now to see the best up-to-date 2 R content for Russia and also check out these interesting facts you probably never knew about 2r.ru
Сетевое издание по туризму, отдыху и путешествиям. Туры, маршруты и достопримечательности. Календарь событий. Бронирование отелей и билетов. Новости туриндустрии. Отзывы туристов.
Visit 2r.ruWe analyzed 2r.ru page load time and found that the first response time was 340 ms and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
2r.ru performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value13.0 s
0/100
25%
Value25.4 s
0/100
10%
Value2,780 ms
3/100
30%
Value0.142
78/100
15%
Value16.0 s
6/100
10%
340 ms
1926 ms
179 ms
184 ms
186 ms
Our browser made a total of 142 requests to load all elements on the main page. We found that 48% of them (68 requests) were addressed to the original 2r.ru, 30% (43 requests) were made to Img.2r.ru and 4% (6 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain 2r.ru.
Page size can be reduced by 1.1 MB (38%)
3.0 MB
1.8 MB
In fact, the total size of 2r.ru main page is 3.0 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 1.6 MB which makes up the majority of the site volume.
Potential reduce by 183.0 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 183.0 kB or 84% of the original size.
Potential reduce by 75.6 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. 2 R images are well optimized though.
Potential reduce by 399.4 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 399.4 kB or 67% of the original size.
Potential reduce by 476.2 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. 2r.ru needs all CSS files to be minified and compressed as it can save up to 476.2 kB or 87% of the original size.
Number of requests can be reduced by 65 (49%)
134
69
The browser has sent 134 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 2 R. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 30 to 1 for CSS and as a result speed up the page load time.
2r.ru
340 ms
www.2r.ru
1926 ms
locker.css
179 ms
window.css
184 ms
jquery-ui-datepicker-fix.css
186 ms
lightbox.css
187 ms
jquery.bxslider.css
187 ms
a_main.css
188 ms
jquery.min.js
12 ms
jquery-ui.min.js
31 ms
locker.js
362 ms
window.js
365 ms
jquery.mCustomScrollbar.js
456 ms
jquery.slider.js
276 ms
jquery.flexslider.js
464 ms
lightbox.min.js
278 ms
bootstrap.min.js
18 ms
bootstrap3.js
370 ms
core.js
562 ms
main.js
451 ms
site_calendar.js
454 ms
310 ms
jstree.min.js
834 ms
style.min.css
542 ms
map.css
543 ms
watch.js
229 ms
z_bootstrap.css
730 ms
z_bootstrap_responsive.css
376 ms
z_font-awesome.css
450 ms
z_font-awesome-ie7.css
453 ms
jquery.ui.1.9.2.ie.css
467 ms
jquery.ui.1.10.0.ie.css
466 ms
jquery-ui-1.9.2.custom.css
721 ms
jquery-ui-1.10.0.custom.css
631 ms
jquery.mCustomScrollbar.css
559 ms
z_flexslider.css
557 ms
u_responsive.css
744 ms
b_global.css
651 ms
b_size.css
734 ms
b_indent.css
737 ms
b_colors.css
746 ms
m_1_head.css
807 ms
m_2_menu.css
809 ms
m_3_showcase.css
899 ms
m_4_body.css
921 ms
m_5_footer.css
833 ms
css
26 ms
css
36 ms
watch.js
741 ms
513 ms
close.png
96 ms
loading.gif
96 ms
prev.png
95 ms
next.png
132 ms
jquery.mousewheel.min.js
6 ms
6655162ea7e76dcb973b71eada97feca.jpg
569 ms
top100.cnt
257 ms
banner-88x31-rambler-blue.gif
248 ms
cycounter
266 ms
logo_base.png
114 ms
logo_400.png
112 ms
670-100-b2b.gif
165 ms
noimg.jpg
163 ms
rea_w300.jpg
168 ms
logow.jpg
259 ms
logo-souvenir.jpg
274 ms
user.png
186 ms
49343e64c293cddf06ed1b0388e719dc.jpeg
565 ms
fbd8918575b0296e72693a79f1dd5262.jpg
565 ms
8c759cd31b6cf40f143b4e574fcd0c59.jpg
664 ms
cdc358ea116fc9a2abe485edfe8eb3f4.jpg
571 ms
6ed9218da367f09c898a0a17b2bc5899.jpg
572 ms
6f2a2967d0025a4854a19cde4a470b0d.jpg
745 ms
2c106e6f24e019564e6ecf8fa74e0918.jpg
838 ms
98457cde0d2193beaf00c63e1c824d4a.jpg
747 ms
6023f0f1ea44c0615f8168d0d460df0e.jpg
758 ms
67864cb0c63bb1e93b56c733a1644e9f.jpg
853 ms
3f4e99c340c1249d64584b13954ca8e4.jpg
849 ms
d9471ee7fb1da4cef79388df0bf96333.jpg
927 ms
61c253969fd01877b8ca5d11daf74c76.jpg
838 ms
0c2acbeb5fa0c9711f6f0687bb15025d.jpg
850 ms
61c253969fd01877b8ca5d11daf74c76.jpg
927 ms
7462af238e905bf96fe6c376f1e614ba.jpg
930 ms
4ab0e95402802556e0a2c2b44902393a.jpg
943 ms
5ec9314c19f457f2a5b90a4963a075b7.jpg
944 ms
72fc91f1e0bb114cbee447e180c32e9a.jpg
943 ms
f52b2a2296a711ffc3d1a7dcaa47cc0f.jpg
1042 ms
5cf7084bc296c3c7c012fc4835f9f881.jpg
1043 ms
a949e52b51762cb0830ce2ee2e6cc36d.jpg
1043 ms
7b819bfb306d238978063151c4dd30c4.jpg
1044 ms
1f94afda487b48ac6b980810dc84e7d2.jpg
1044 ms
d8e01b15545f3c079282839fc5a5d086.jpg
1043 ms
3641080ae84b1e6995c660369048a646.jpg
1109 ms
49f77bbe9896a310173797b8b271de32.jpg
1110 ms
87be42a793f4dcecd67474b1538dfa69.jpg
1111 ms
62af8fe7cded074b32e887276e380a5d.jpg
1127 ms
6ca3e91eb08aa0c0787f3e42eaacea99.jpg
1128 ms
de0a91e389d6dfb287cca6ca2214c706.jpg
1130 ms
5a433e78f37c30bd1f1cb1e8da9d0c28.jpg
1199 ms
18656c1646a93264132db3233a15ce38.jpg
1200 ms
0c2acbeb5fa0c9711f6f0687bb15025d.jpg
1203 ms
434866ad1777a151e4ca6b48d758a6bd.jpg
1220 ms
russia_op.png
239 ms
home_hover.png
240 ms
news.png
244 ms
calendar.png
265 ms
route.png
329 ms
rf.png
330 ms
region.png
337 ms
master.png
338 ms
arrow_r.png
337 ms
arrow_l.png
343 ms
fontawesome-webfont.woff
407 ms
context.js
226 ms
context_static_r1065.js
673 ms
f7950c06c2942b5b86a0f42ec453b918.jpg
665 ms
d67909c41792c80e83b41397ae470fa1.jpg
667 ms
432b30eb3eb98271dc7284eb0b99359f.jpg
732 ms
bd556b27ffd849e290809ed4cc0d3903.jpg
725 ms
6198e4b0e9e415d2eba888b90b79dec9.jpg
727 ms
5232ed2916155430d78181357c3655d7.jpg
657 ms
78fb096833479ab028ec6394ed1c2973.jpg
576 ms
counter
313 ms
60375
210 ms
advert.gif
119 ms
x90
8 ms
cnt
568 ms
1
117 ms
hit
256 ms
script.js
488 ms
60375
141 ms
1612717
119 ms
hit
132 ms
cachedscriptxy.js
126 ms
u6868.24.spylog.com
247 ms
openapi.js
404 ms
loader_1.gif
186 ms
loader_2.gif
98 ms
loader_3.gif
95 ms
icons.png
97 ms
cnt
246 ms
rexdot.gif
126 ms
2r.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
button, link, and menuitem elements do not have accessible names.
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
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
2r.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
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
2r.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 2r.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 2r.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.
2r.ru
Open Graph description is not detected on the main page of 2 R. 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: