Access rostatus.ru. Услуги специализированного регистратора АО «СТАТУС» - ведение реестра владельцев ценных бумаг и акци...

rostatus.ru screenshot

18

Performance

Renders faster than
34% of other websites
80

Accessibility

Visual factors better than
that of 49% of websites
67

Best Practices

More advanced features
available than in
24% of websites
83

SEO

Google-friendlier than
46% of websites

First Response

488 ms

Resources Loaded

5.1 sec

Page Rendered

706 ms

rostatus.ru screenshot

About Website

Visit rostatus.ru now to see the best up-to-date Rostatus content for Russia and also check out these interesting facts you probably never knew about rostatus.ru

Регистраторское общество «СТАТУС» - профессиональный специализированный регистратор, осуществляющий услуги по ведению реестров владельцев именных ценных бумаг и акционеров.

Visit rostatus.ru

Key Findings

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

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value25.1 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value3,540 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value25.3 s

0/100

10%

rostatus.ru

488 ms

rostatus.ru

1109 ms

aos.css

222 ms

bootstrap4.min.css

438 ms

bootstrap.min.css

445 ms

Our browser made a total of 159 requests to load all elements on the main page. We found that 87% of them (139 requests) were addressed to the original Rostatus.ru, 4% (7 requests) were made to Youtube.com and 1% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Mc.yandex.ru.

Content Size

10.0 MB

After Optimization

9.0 MB

In fact, the total size of Rostatus.ru main page is 10.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. Only a small number of websites need less resources to load. Images take 8.7 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 374.0 kB

Original 417.4 kB
After minification 386.4 kB
After compression 43.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 374.0 kB or 90% of the original size.

Image Optimization

-6%

Potential reduce by 542.4 kB

Original 8.7 MB
After minification 8.2 MB

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. Rostatus images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 38.1 kB

Original 705.9 kB
After minification 705.8 kB
After compression 667.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

-10%

Potential reduce by 14.3 kB

Original 149.6 kB
After minification 149.6 kB
After compression 135.3 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. Rostatus.ru has all CSS files already compressed.

Requests Now

148

After Optimization

110

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

Accessibility Issues

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.

High

ARIA input fields do not have accessible names

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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.

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

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

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

RU
Language Claimed

N/A
Encoding

UTF-8

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

rostatus.ru

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