Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

Page Load Speed

5.7 sec in total

First Response

125 ms

Resources Loaded

4 sec

Page Rendered

1.5 sec

About Website

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

Рег.ру🔷 Российский хостинг-провайдер и регистратор доменов ➤➤ ✔️ Домены ✔️ Хостинг сайтов и DNS-серверов ✔️ Облачные VDS/VPS ✔️ Выделенные серверы в аренду ✔️ Конструктор сайтов и CMS ✔️ Продажа SSL-с...

Visit reg.ru

Key Findings

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

Performance Metrics

reg.ru performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value17.5 s

0/100

25%

SI (Speed Index)

Value15.0 s

1/100

10%

TBT (Total Blocking Time)

Value6,070 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.076

95/100

15%

TTI (Time to Interactive)

Value27.5 s

0/100

10%

Network Requests Diagram

reg.ru

125 ms

www.reg.ru

758 ms

manifest.8dbdc1d1b895a8c0b553.js

244 ms

head-scripts.2ff7329da5c555107564.js

366 ms

design-system.f9109ea855c264937c47.js

611 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 65% of them (46 requests) were addressed to the original Reg.ru, 20% (14 requests) were made to Img.reg.ru and 6% (4 requests) were made to Files.reg.ru. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Img.reg.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 233.2 kB (65%)

Content Size

356.5 kB

After Optimization

123.2 kB

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

HTML Optimization

-85%

Potential reduce by 233.2 kB

  • Original 273.0 kB
  • After minification 204.9 kB
  • After compression 39.8 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 68.1 kB, which is 25% 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 233.2 kB or 85% of the original size.

JavaScript Optimization

-0%

Potential reduce by 43 B

  • Original 83.5 kB
  • After minification 83.5 kB
  • After compression 83.4 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.

Requests Breakdown

Number of requests can be reduced by 34 (67%)

Requests Now

51

After Optimization

17

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

Accessibility Review

reg.ru accessibility score

75

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

Links do not have a discernible 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.

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

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

Missing source maps for large first-party JavaScript

SEO Factors

reg.ru SEO score

100

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Reg.ru can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Russian. Our system also found out that Reg.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

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