Tools & Wizards About Us
rtc.ru screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

rtc.ru

ГНЦ РФ ЦНИИ РТК - Центральный научно-исследовательский институт робототехники и технической кибернетики

Page Load Speed

16.5 sec in total

First Response

4.2 sec

Resources Loaded

8.3 sec

Page Rendered

4 sec

rtc.ru screenshot

About Website

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

ЦНИИ РТК – центр компетенции в области исследований и создания средств робототехники, технической кибернетики и мехатроники.

Visit rtc.ru

Key Findings

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

Performance Metrics

rtc.ru performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value7.8 s

24/100

10%

TBT (Total Blocking Time)

Value1,010 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.047

99/100

15%

TTI (Time to Interactive)

Value8.9 s

35/100

10%

Network Requests Diagram

rtc.ru

4199 ms

rokbox.css

452 ms

cards.css

315 ms

slideshow.css

320 ms

finder.css

321 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 85% of them (52 requests) were addressed to the original Rtc.ru, 10% (6 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Rtc.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 862.6 kB (41%)

Content Size

2.1 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rtc.ru main page is 2.1 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 955.8 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 43.0 kB

  • Original 52.4 kB
  • After minification 45.7 kB
  • After compression 9.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. This page needs HTML code to be minified as it can gain 6.7 kB, which is 13% 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 43.0 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 30.1 kB

  • Original 955.8 kB
  • After minification 925.7 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. Rtc images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 513.3 kB

  • Original 741.5 kB
  • After minification 726.4 kB
  • After compression 228.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 513.3 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 276.2 kB

  • Original 335.0 kB
  • After minification 309.7 kB
  • After compression 58.8 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. Rtc.ru needs all CSS files to be minified and compressed as it can save up to 276.2 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (69%)

Requests Now

52

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rtc.ru

rtc.ru

4199 ms

rokbox.css

rokbox.css

452 ms

cards.css

cards.css

315 ms

slideshow.css

slideshow.css

320 ms

finder.css

finder.css

321 ms

jquery.min.js

jquery.min.js

823 ms

jquery-noconflict.js

jquery-noconflict.js

465 ms

jquery-migrate.min.js

jquery-migrate.min.js

458 ms

caption.js

caption.js

463 ms

mootools-core.js

mootools-core.js

992 ms

core.js

core.js

599 ms

mootools-more.js

mootools-more.js

1674 ms

rokbox.js

rokbox.js

804 ms

jquery_v1.10.2.js

jquery_v1.10.2.js

1195 ms

jquery_bt_noconflict.js

jquery_bt_noconflict.js

781 ms

mootools-mobile.js

mootools-mobile.js

952 ms

rokmediaqueries.js

rokmediaqueries.js

986 ms

roksprocket.js

roksprocket.js

1189 ms

moofx.js

moofx.js

1180 ms

roksprocket.request.js

roksprocket.request.js

1198 ms

strips.js

strips.js

1198 ms

strips-speeds.js

strips-speeds.js

1198 ms

features.js

features.js

1283 ms

slideshow.js

slideshow.js

1306 ms

bootstrap.min.js

bootstrap.min.js

1306 ms

jquery.autocomplete.min.js

jquery.autocomplete.min.js

1304 ms

font-awesome.min.css

font-awesome.min.css

1322 ms

bootstrap.min.css

bootstrap.min.css

2202 ms

skin1.css

skin1.css

2344 ms

css

css

69 ms

css

css

95 ms

bootstrap.min.js

bootstrap.min.js

1384 ms

bt_gotop.js

bt_gotop.js

2080 ms

jquery.fitvids.min.js

jquery.fitvids.min.js

2081 ms

modernizr.custom.js

modernizr.custom.js

2081 ms

jquery.cbpQTRotator.min.js

jquery.cbpQTRotator.min.js

2096 ms

bt_fade_img.js

bt_fade_img.js

1930 ms

bt_waypoints.min.js

bt_waypoints.min.js

2006 ms

jquery.slicknav.min.js

jquery.slicknav.min.js

2012 ms

logo2015.jpg

logo2015.jpg

152 ms

im_1s.jpg

im_1s.jpg

2195 ms

im_2s.jpg

im_2s.jpg

1379 ms

im_3_2s.jpg

im_3_2s.jpg

813 ms

d4b73d57a0591ef66277236e30def99e_200_300.jpg

d4b73d57a0591ef66277236e30def99e_200_300.jpg

153 ms

5e1a5453b3783c562476a3048832a964_200_300.jpg

5e1a5453b3783c562476a3048832a964_200_300.jpg

708 ms

5329dda2c02d9bd4c952862f332eccb0_200_300.jpg

5329dda2c02d9bd4c952862f332eccb0_200_300.jpg

703 ms

5443af460056cd293da8aca55e003779_200_300.jpg

5443af460056cd293da8aca55e003779_200_300.jpg

718 ms

ico_%201.jpg

ico_%201.jpg

699 ms

ico_%202.jpg

ico_%202.jpg

718 ms

ico_%203.jpg

ico_%203.jpg

719 ms

ico_%204.jpg

ico_%204.jpg

719 ms

PK.jpg

PK.jpg

792 ms

gotop_fixed.png

gotop_fixed.png

277 ms

IgZJs4-7SA1XX_edsoXWog.ttf

IgZJs4-7SA1XX_edsoXWog.ttf

200 ms

DXI1ORHCpsQm3Vp6mXoaTS3USBnSvpkopQaUR-2r7iU.ttf

DXI1ORHCpsQm3Vp6mXoaTS3USBnSvpkopQaUR-2r7iU.ttf

282 ms

MTP_ySUJH_bn48VBG8sNSi3USBnSvpkopQaUR-2r7iU.ttf

MTP_ySUJH_bn48VBG8sNSi3USBnSvpkopQaUR-2r7iU.ttf

333 ms

k3k702ZOKiLJc3WVjuplzC3USBnSvpkopQaUR-2r7iU.ttf

k3k702ZOKiLJc3WVjuplzC3USBnSvpkopQaUR-2r7iU.ttf

332 ms

6tl3_FkDeXSD72oEHuJh4w.ttf

6tl3_FkDeXSD72oEHuJh4w.ttf

85 ms

JgXs0F_UiaEdAS74msmFNg.ttf

JgXs0F_UiaEdAS74msmFNg.ttf

123 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

630 ms

watch.js

watch.js

316 ms

Accessibility Review

rtc.ru accessibility score

82

Accessibility Issues

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.

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

rtc.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

rtc.ru SEO score

92

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

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

    RU

  • Encoding

    UTF-8

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

rtc.ru

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