5.7 sec in total
507 ms
4.5 sec
675 ms
Welcome to travel.reso.ru homepage info - get ready to check Travel Reso best content for Russia right away, or after learning these important things about travel.reso.ru
Оформить и купить туристическую страховку для выезда за рубеж. Страхование путешественников онлайн в Москве, СПБ и по всей России. Электронный полис ВЗР с защитой от невыезда
Visit travel.reso.ruWe analyzed Travel.reso.ru page load time and found that the first response time was 507 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
travel.reso.ru performance score
name
value
score
weighting
Value7.6 s
0/100
10%
Value11.0 s
0/100
25%
Value16.2 s
0/100
10%
Value3,770 ms
1/100
30%
Value0
100/100
15%
Value28.2 s
0/100
10%
507 ms
1050 ms
362 ms
570 ms
493 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Travel.reso.ru, 87% (81 requests) were made to Reso.ru and 3% (3 requests) were made to Mc.yandex.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Reso.ru.
Page size can be reduced by 266.8 kB (16%)
1.6 MB
1.4 MB
In fact, the total size of Travel.reso.ru main page is 1.6 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. 50% of websites need less resources to load. Images take 870.8 kB which makes up the majority of the site volume.
Potential reduce by 103.4 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 103.4 kB or 81% of the original size.
Potential reduce by 47.2 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. Travel Reso images are well optimized though.
Potential reduce by 52.7 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 63.5 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. Travel.reso.ru needs all CSS files to be minified and compressed as it can save up to 63.5 kB or 65% of the original size.
Number of requests can be reduced by 45 (54%)
84
39
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Travel Reso. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
travel.reso.ru
507 ms
1050 ms
66ba13a395f5735911fffc0f.js
362 ms
libs.site.min.js_2002.js
570 ms
common-functions-site.min.6.98.js
493 ms
api.js
65 ms
components.umd.min.0.js
515 ms
components.umd.min.22.js
513 ms
components.umd.min.26.js
515 ms
components.umd.min.28.js
647 ms
components.umd.min.js
1176 ms
bootstrap.min.6.1.css
652 ms
main_site_styles.min.6.50.css
658 ms
resoLinks-Downloads.min.6.1.css
716 ms
resoLinks-FaqList.min.6.1.css
751 ms
resoExtendedCard-RegionStat.min.6.1.css
806 ms
resoCard-Banner.min.6.1.css
806 ms
resoCard-UsefulOptions.min.6.5.css
863 ms
slick.min.6.11.css
870 ms
resoSlider.min.6.2.css
939 ms
resoCard-Background.min.6.9.css
939 ms
resoSlider-Program.min.6.2.css
935 ms
resoLinks-ManyButtons.min.6.1.css
1006 ms
resoContainer.min.6.2.css
1005 ms
jquery-ui.base.core.min.6.9.css
1067 ms
datepicker.min.6.4.css
1071 ms
ResoActionForm-Calculation.min.6.34.css
1077 ms
libs.forms.min.js_2002.js
1133 ms
common-functions-forms.min.6.189.js
1152 ms
popUp.js
1206 ms
slick.min.6.2.js
1206 ms
ResoActionForm-Calculation.min.6.60.js
1208 ms
travel-new.min.6.45.js
1269 ms
travel.min.6.37.css
1298 ms
auth.min.6.2.js
1217 ms
captcha.min.6.2.js
1228 ms
recaptcha__en.js
22 ms
tag.js
857 ms
gtm.js
58 ms
logo.svg
151 ms
search.svg
149 ms
turist.png
434 ms
travel-mob.png
364 ms
icon-casco-contactdata.svg
249 ms
icon-casco-result.svg
251 ms
doctor-krest.svg
295 ms
bed-krest.svg
294 ms
reso-03.svg
345 ms
age.svg
386 ms
callcentr.svg
397 ms
neviezd.svg
398 ms
stomatology.svg
477 ms
hospital-with-child.svg
507 ms
death.svg
517 ms
samolet-death.svg
528 ms
karantin.svg
532 ms
sport-risks.png
567 ms
ns-risks.png
608 ms
trip-cancel.png
655 ms
lost-baggage.png
651 ms
go-travel.png
655 ms
download.svg
663 ms
main-agent.png
694 ms
main-map.png
780 ms
ambulator.svg
804 ms
clients.svg
787 ms
day.svg
807 ms
coin.svg
822 ms
iconix.svg
887 ms
ellipse.svg
889 ms
SFProDisplay-Regular.woff
1012 ms
SFProDisplay-Semibold.woff
998 ms
SFProDisplay-Bold.woff
985 ms
Raleway-Bold.woff
843 ms
Raleway-SemiBold.woff
866 ms
input-valid.svg
899 ms
favicon.ico
20 ms
favicon.ico
21 ms
5ae258dae014b7c686aff59dc49ee1d7
1015 ms
Icon.svg
848 ms
delete.svg
887 ms
advert.gif
539 ms
vk.svg
983 ms
tg.svg
981 ms
41fa767fe6c108b739687c5c2aabf518.gif
910 ms
openapi.c340c125c61ec5745ebb2a98626e46ab.js
256 ms
target.svg
648 ms
rtrg
139 ms
1
269 ms
1
165 ms
blog-choose-travel.jpg
203 ms
ios.png
248 ms
android.png
228 ms
travel.reso.ru accessibility score
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
travel.reso.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
travel.reso.ru SEO score
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
![]()
RU
![]()
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Travel.reso.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 Travel.reso.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.
travel.reso.ru
Open Graph description is not detected on the main page of Travel Reso. 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: