Tools & Wizards About Us
reso.ru screenshot

Report Summary

  • 2

    Performance

    Renders faster than
    20% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 96

    SEO

    Google-friendlier than
    90% of websites

reso.ru

РЕСО-Гарантия - страхование физических и юридических лиц

Page Load Speed

5.1 sec in total

First Response

726 ms

Resources Loaded

3.9 sec

Page Rendered

521 ms

reso.ru screenshot

About Website

Click here to check amazing Reso content for Russia. Otherwise, check out these important facts you probably never knew about reso.ru

РЕСО-Гарантия - один из лидеров страхового рынка России. Страхование автомобилей, недвижимого имущества, жизни и здоровья. Оформление полисов онлайн и удобные калькуляторы расчета стоимости.

Visit reso.ru

Key Findings

We analyzed Reso.ru page load time and found that the first response time was 726 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

reso.ru performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value15.7 s

0/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value3,130 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.878

3/100

15%

TTI (Time to Interactive)

Value28.7 s

0/100

10%

Network Requests Diagram

reso.ru

726 ms

libs.site.min.js_2002.js

279 ms

common-functions-site.min.3.84.js

376 ms

components.umd.min.0.js

387 ms

components.umd.min.22.js

448 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 90% of them (73 requests) were addressed to the original Reso.ru, 2% (2 requests) were made to Vk.com and 2% (2 requests) were made to Mc.yandex.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Reso.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 173.7 kB (18%)

Content Size

958.8 kB

After Optimization

785.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Reso.ru main page is 958.8 kB. 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. Javascripts take 467.0 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 46.9 kB

  • Original 60.6 kB
  • After minification 56.6 kB
  • After compression 13.7 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 46.9 kB or 77% of the original size.

Image Optimization

-5%

Potential reduce by 15.3 kB

  • Original 325.2 kB
  • After minification 309.9 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. Reso images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 42.2 kB

  • Original 467.0 kB
  • After minification 467.0 kB
  • After compression 424.8 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.

CSS Optimization

-65%

Potential reduce by 69.3 kB

  • Original 106.0 kB
  • After minification 75.8 kB
  • After compression 36.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. Reso.ru needs all CSS files to be minified and compressed as it can save up to 69.3 kB or 65% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (59%)

Requests Now

75

After Optimization

31

  • Images
  • JavaScript
  • CSS

The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 26 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

reso.ru

reso.ru

726 ms

libs.site.min.js_2002.js

libs.site.min.js_2002.js

279 ms

common-functions-site.min.3.84.js

common-functions-site.min.3.84.js

376 ms

components.umd.min.0.js

components.umd.min.0.js

387 ms

components.umd.min.22.js

components.umd.min.22.js

448 ms

components.umd.min.26.js

components.umd.min.26.js

449 ms

components.umd.min.28.js

components.umd.min.28.js

496 ms

components.umd.min.1.js

components.umd.min.1.js

505 ms

components.umd.min.2.js

components.umd.min.2.js

524 ms

components.umd.min.4.js

components.umd.min.4.js

542 ms

components.umd.min.5.js

components.umd.min.5.js

568 ms

components.umd.min.7.js

components.umd.min.7.js

706 ms

components.umd.min.33.js

components.umd.min.33.js

627 ms

components.umd.min.45.js

components.umd.min.45.js

632 ms

components.umd.min.js

components.umd.min.js

1034 ms

api.js

api.js

42 ms

bootstrap.min.3.1.css

bootstrap.min.3.1.css

677 ms

main_site_styles.min.3.32.css

main_site_styles.min.3.32.css

712 ms

jquery-ui.base.core.min.3.9.css

jquery-ui.base.core.min.3.9.css

750 ms

datepicker.min.3.4.css

datepicker.min.3.4.css

756 ms

ResoActionForm-Calculation.min.3.15.css

ResoActionForm-Calculation.min.3.15.css

821 ms

resoEvents.min.3.1.css

resoEvents.min.3.1.css

846 ms

resoTabList.min.3.2.css

resoTabList.min.3.2.css

849 ms

slick.min.3.11.css

slick.min.3.11.css

872 ms

vue_components_styles.min.3.22.css

vue_components_styles.min.3.22.css

881 ms

resoSlider.min.3.2.css

resoSlider.min.3.2.css

940 ms

resoExtendedCard-RegionStat.min.3.1.css

resoExtendedCard-RegionStat.min.3.1.css

983 ms

main-slider.min.3.33.css

main-slider.min.3.33.css

983 ms

resoContainer.min.3.1.css

resoContainer.min.3.1.css

993 ms

libs.forms.min.js_2002.js

libs.forms.min.js_2002.js

1005 ms

common-functions-forms.min.3.170.js

common-functions-forms.min.3.170.js

1071 ms

ResoActionForm-Calculation.min.3.24.js

ResoActionForm-Calculation.min.3.24.js

1122 ms

slick.min.3.2.js

slick.min.3.2.js

1123 ms

script.min.3.372.js

script.min.3.372.js

1116 ms

agent-call-forma.min.3.66.js

agent-call-forma.min.3.66.js

1161 ms

captcha.min.3.2.js

captcha.min.3.2.js

1207 ms

recaptcha__en.js

recaptcha__en.js

29 ms

tag.js

tag.js

999 ms

gtm.js

gtm.js

61 ms

main_travel.png

main_travel.png

183 ms

slide-3.svg

slide-3.svg

182 ms

slide-3_active.svg

slide-3_active.svg

142 ms

slide-4.svg

slide-4.svg

145 ms

slide-4_active.svg

slide-4_active.svg

145 ms

slide-1.svg

slide-1.svg

183 ms

slide-1_active.svg

slide-1_active.svg

250 ms

slide-2.svg

slide-2.svg

271 ms

slide-2_active.svg

slide-2_active.svg

259 ms

main-agent.png

main-agent.png

282 ms

main-map.png

main-map.png

285 ms

Icon-done.svg

Icon-done.svg

376 ms

icon-warning.svg

icon-warning.svg

384 ms

auto.png

auto.png

402 ms

med-case.png

med-case.png

420 ms

prop.png

prop.png

407 ms

travel.png

travel.png

431 ms

clients-fact.svg

clients-fact.svg

502 ms

map.svg

map.svg

507 ms

trophy.svg

trophy.svg

574 ms

Group-2.svg

Group-2.svg

530 ms

qr_reso-mob.png

qr_reso-mob.png

559 ms

main-phone.png

main-phone.png

571 ms

iconix.svg

iconix.svg

708 ms

logo.svg

logo.svg

676 ms

search.svg

search.svg

679 ms

Raleway-Bold.woff

Raleway-Bold.woff

695 ms

Raleway-SemiBold.woff

Raleway-SemiBold.woff

683 ms

SFProDisplay-Semibold.woff

SFProDisplay-Semibold.woff

846 ms

SFProDisplay-Bold.woff

SFProDisplay-Bold.woff

861 ms

SFProDisplay-Regular.woff

SFProDisplay-Regular.woff

769 ms

vk.svg

vk.svg

782 ms

tg.svg

tg.svg

838 ms

target.svg

target.svg

689 ms

openapi.a2ed73393cad04481c1dfb3f7794921f.js

openapi.a2ed73393cad04481c1dfb3f7794921f.js

263 ms

ellipse.svg

ellipse.svg

293 ms

advert.gif

advert.gif

659 ms

main-school.png

main-school.png

167 ms

ios.png

ios.png

167 ms

android.png

android.png

185 ms

rtrg

rtrg

145 ms

sync_cookie_image_decide

sync_cookie_image_decide

140 ms

Accessibility Review

reso.ru accessibility score

90

Accessibility Issues

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

High

Buttons do not have an accessible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Best Practices

reso.ru best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

reso.ru SEO score

96

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 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 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.

Social Sharing Optimization

reso.ru

Open Graph description is not detected on the main page of 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: