Tools & Wizards About Us
r2d2.by screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

r2d2.by

Welcome to R2D2.BY

Page Load Speed

4.5 sec in total

First Response

1.6 sec

Resources Loaded

2.8 sec

Page Rendered

145 ms

r2d2.by screenshot

About Website

Click here to check amazing R2D2 content. Otherwise, check out these important facts you probably never knew about r2d2.by

Функции календаря, математические функции, полезные утилиты. Мобильно. Онлайн

Visit r2d2.by

Key Findings

We analyzed R2d2.by page load time and found that the first response time was 1.6 sec and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

r2d2.by performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value6,330 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.157

74/100

15%

TTI (Time to Interactive)

Value19.0 s

3/100

10%

Network Requests Diagram

r2d2.by

1628 ms

bootstrap.min.css

829 ms

font-awesome.min.css

172 ms

ionicons.min.css

420 ms

jquery-jvectormap-1.2.2.css

425 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 46% of them (16 requests) were addressed to the original R2d2.by, 11% (4 requests) were made to Fonts.gstatic.com and 9% (3 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain R2d2.by.

Page Optimization Overview & Recommendations

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

Content Size

741.8 kB

After Optimization

193.8 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of R2d2.by main page is 741.8 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. 55% of websites need less resources to load. CSS take 407.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 19.6 kB

  • Original 24.4 kB
  • After minification 17.3 kB
  • After compression 4.9 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 7.1 kB, which is 29% 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 19.6 kB or 80% of the original size.

JavaScript Optimization

-56%

Potential reduce by 174.4 kB

  • Original 310.2 kB
  • After minification 285.9 kB
  • After compression 135.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 174.4 kB or 56% of the original size.

CSS Optimization

-87%

Potential reduce by 354.1 kB

  • Original 407.2 kB
  • After minification 406.0 kB
  • After compression 53.1 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. R2d2.by needs all CSS files to be minified and compressed as it can save up to 354.1 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (88%)

Requests Now

26

After Optimization

3

  • AJAX
  • JavaScript
  • CSS

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

Network Requests Diagram

r2d2.by

r2d2.by

1628 ms

bootstrap.min.css

bootstrap.min.css

829 ms

font-awesome.min.css

font-awesome.min.css

172 ms

ionicons.min.css

ionicons.min.css

420 ms

jquery-jvectormap-1.2.2.css

jquery-jvectormap-1.2.2.css

425 ms

AdminLTE.min.css

AdminLTE.min.css

797 ms

_all-skins.min.css

_all-skins.min.css

751 ms

app.css

app.css

417 ms

weather-icons.min.css

weather-icons.min.css

747 ms

weather-icons-wind.min.css

weather-icons-wind.min.css

1017 ms

app-weather.css

app-weather.css

750 ms

adsbygoogle.js

adsbygoogle.js

154 ms

adsbygoogle.js

adsbygoogle.js

266 ms

jquery-2.2.3.min.js

jquery-2.2.3.min.js

1021 ms

bootstrap.min.js

bootstrap.min.js

842 ms

fastclick.js

fastclick.js

813 ms

app.min.js

app.min.js

744 ms

jquery.slimscroll.min.js

jquery.slimscroll.min.js

823 ms

demo.js

demo.js

866 ms

helper.js

helper.js

1019 ms

show_ads_impl.js

show_ads_impl.js

120 ms

zrt_lookup.html

zrt_lookup.html

428 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

127 ms

cookie.js

cookie.js

151 ms

integrator.js

integrator.js

178 ms

ads

ads

119 ms

css

css

92 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

81 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf

82 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

92 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

131 ms

integrator.js

integrator.js

36 ms

ads

ads

75 ms

analytics.js

analytics.js

30 ms

watch.js

watch.js

20 ms

Accessibility Review

r2d2.by accessibility score

72

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

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

<frame> or <iframe> elements do not have a title

Internationalization and localization

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

Impact

Issue

High

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

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

r2d2.by 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

r2d2.by 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

    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 R2d2.by 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 R2d2.by 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

r2d2.by

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