Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

Page Load Speed

7.1 sec in total

First Response

478 ms

Resources Loaded

6.5 sec

Page Rendered

182 ms

re-born.ru screenshot

About Website

Welcome to re-born.ru homepage info - get ready to check Re Born best content for Russia right away, or after learning these important things about re-born.ru

Visit re-born.ru

Key Findings

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

Performance Metrics

re-born.ru performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

4/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value1,480 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.291

41/100

15%

TTI (Time to Interactive)

Value16.0 s

6/100

10%

Network Requests Diagram

re-born.ru

478 ms

www.re-born.ru

2209 ms

css

26 ms

Common.min.css

487 ms

Site.min.css

474 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 70% of them (51 requests) were addressed to the original Re-born.ru, 11% (8 requests) were made to Poulart.ru and 5% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Re-born.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 869.0 kB (74%)

Content Size

1.2 MB

After Optimization

307.3 kB

In fact, the total size of Re-born.ru main page is 1.2 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. 60% of websites need less resources to load. Javascripts take 954.9 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 38.2 kB

  • Original 50.8 kB
  • After minification 39.1 kB
  • After compression 12.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 11.7 kB, which is 23% 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 38.2 kB or 75% of the original size.

Image Optimization

-22%

Potential reduce by 3.7 kB

  • Original 17.4 kB
  • After minification 13.6 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. Obviously, Re Born needs image optimization as it can save up to 3.7 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-74%

Potential reduce by 702.1 kB

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

CSS Optimization

-82%

Potential reduce by 125.0 kB

  • Original 153.3 kB
  • After minification 125.3 kB
  • After compression 28.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. Re-born.ru needs all CSS files to be minified and compressed as it can save up to 125.0 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (70%)

Requests Now

66

After Optimization

20

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

Accessibility Review

re-born.ru accessibility score

76

Accessibility Issues

ARIA

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.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

button, link, and menuitem elements do not have accessible names.

High

[role]s are not contained by their required parent element

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

re-born.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

re-born.ru SEO score

77

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

High

Page is blocked from indexing

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Re-born.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Re-born.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 Re Born. 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: