Tools & Wizards About Us
otr.ru screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

otr.ru

ОТР - Организационно-технологические решения, ИТ-компания

Page Load Speed

23.6 sec in total

First Response

543 ms

Resources Loaded

22.2 sec

Page Rendered

839 ms

otr.ru screenshot

About Website

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

OTR - ИТ-проекты для государства и бизнеса. 22 года на рынке. Разработка ПО, ИТ-инфраструктура, системная интеграция, информационная безопасность, облачные решения.

Visit otr.ru

Key Findings

We analyzed Otr.ru page load time and found that the first response time was 543 ms and then it took 23.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

otr.ru performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value7.9 s

22/100

10%

TBT (Total Blocking Time)

Value1,200 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value11.2 s

20/100

10%

Network Requests Diagram

otr.ru

543 ms

otr.ru

1087 ms

template_b1f07e7c1c27f1c346d8da5fa7986998_v1.css

413 ms

core.min.js

688 ms

kernel_main_v1.js

550 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 64% of them (25 requests) were addressed to the original Otr.ru, 13% (5 requests) were made to Mc.yandex.com and 5% (2 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source Widgets.mos.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 294.2 kB (31%)

Content Size

947.9 kB

After Optimization

653.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Otr.ru main page is 947.9 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. 45% of websites need less resources to load. HTML takes 409.7 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 273.1 kB

  • Original 409.7 kB
  • After minification 353.8 kB
  • After compression 136.6 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. This page needs HTML code to be minified as it can gain 55.9 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 273.1 kB or 67% of the original size.

Image Optimization

-7%

Potential reduce by 17.5 kB

  • Original 239.9 kB
  • After minification 222.4 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. Otr images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 658 B

  • Original 274.9 kB
  • After minification 274.9 kB
  • After compression 274.3 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

-13%

Potential reduce by 3.0 kB

  • Original 23.4 kB
  • After minification 23.4 kB
  • After compression 20.4 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. Otr.ru needs all CSS files to be minified and compressed as it can save up to 3.0 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (45%)

Requests Now

29

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Otr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

otr.ru

otr.ru

543 ms

otr.ru

otr.ru

1087 ms

template_b1f07e7c1c27f1c346d8da5fa7986998_v1.css

template_b1f07e7c1c27f1c346d8da5fa7986998_v1.css

413 ms

core.min.js

core.min.js

688 ms

kernel_main_v1.js

kernel_main_v1.js

550 ms

dexie3.bundle.min.js

dexie3.bundle.min.js

560 ms

core_ls.min.js

core_ls.min.js

426 ms

core_frame_cache.min.js

core_frame_cache.min.js

428 ms

396d150244cdd185.css

396d150244cdd185.css

550 ms

swiper-bundle.min.css

swiper-bundle.min.css

28 ms

swiper-bundle.min.js

swiper-bundle.min.js

32 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

26 ms

template_265cb536701e99052fb39f5c363b9aba_v1.js

template_265cb536701e99052fb39f5c363b9aba_v1.js

726 ms

global.js

global.js

302 ms

lazysizes.min.js

lazysizes.min.js

33 ms

ls.native-loading.min.js

ls.native-loading.min.js

53 ms

ba.js

ba.js

280 ms

34d5ehlwbkg80uyuld0qw73y3vwmi3pe.png

34d5ehlwbkg80uyuld0qw73y3vwmi3pe.png

164 ms

9jvUhHXC3t.svg

9jvUhHXC3t.svg

166 ms

phone.svg

phone.svg

165 ms

mbbu7im7shm1qckd5tshkr103c9uw289.png

mbbu7im7shm1qckd5tshkr103c9uw289.png

162 ms

qmfexx6ttsed9rejf1sjt3v82x7fqt6o.png

qmfexx6ttsed9rejf1sjt3v82x7fqt6o.png

162 ms

iylw70qp94whtmr3q20z44cv32lh53xt.png

iylw70qp94whtmr3q20z44cv32lh53xt.png

163 ms

wotbgm5hlqiaom7bb5l5jui0yykqfdbh.png

wotbgm5hlqiaom7bb5l5jui0yykqfdbh.png

274 ms

f4lkfyynd361r0bq4thowxjxuj6v330b.png

f4lkfyynd361r0bq4thowxjxuj6v330b.png

419 ms

Manrope-Regular.woff

Manrope-Regular.woff

157 ms

Manrope-Medium.woff

Manrope-Medium.woff

303 ms

Manrope-Light.woff

Manrope-Light.woff

157 ms

Manrope-SemiBold.woff

Manrope-SemiBold.woff

139 ms

Manrope-Bold.woff

Manrope-Bold.woff

254 ms

Manrope-ExtraBold.woff

Manrope-ExtraBold.woff

303 ms

citywidgets.js

citywidgets.js

19900 ms

tag.js

tag.js

905 ms

bx_stat

bx_stat

183 ms

advert.gif

advert.gif

723 ms

sync_cookie_image_decide

sync_cookie_image_decide

186 ms

1

1

139 ms

tag_phone.js

tag_phone.js

232 ms

1

1

269 ms

Accessibility Review

otr.ru accessibility score

74

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

otr.ru best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

otr.ru SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Otr.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed English language. Our system also found out that Otr.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

otr.ru

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