Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

rfe.by

TechTravelEdu — Технологии и Образование в Путешествиях

Page Load Speed

4.2 sec in total

First Response

829 ms

Resources Loaded

2.9 sec

Page Rendered

465 ms

rfe.by screenshot

About Website

Click here to check amazing Rfe content for Belarus. Otherwise, check out these important facts you probably never knew about rfe.by

Visit rfe.by

Key Findings

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

Performance Metrics

rfe.by performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value15.6 s

0/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value2,200 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value16.2 s

5/100

10%

Network Requests Diagram

rfe.by

829 ms

imports.css

158 ms

bootstrap1.min.css

511 ms

owl-carousel.css

322 ms

social.css

318 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 43% of them (32 requests) were addressed to the original Rfe.by, 5% (4 requests) were made to Mc.yandex.ru and 5% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Rfe.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 832.6 kB (36%)

Content Size

2.3 MB

After Optimization

1.5 MB

In fact, the total size of Rfe.by main page is 2.3 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. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 50.2 kB

  • Original 60.7 kB
  • After minification 49.2 kB
  • After compression 10.5 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.5 kB, which is 19% 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 50.2 kB or 83% of the original size.

Image Optimization

-7%

Potential reduce by 87.2 kB

  • Original 1.3 MB
  • After minification 1.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. Rfe images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 459.9 kB

  • Original 640.1 kB
  • After minification 557.0 kB
  • After compression 180.2 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 459.9 kB or 72% of the original size.

CSS Optimization

-83%

Potential reduce by 235.3 kB

  • Original 284.2 kB
  • After minification 274.3 kB
  • After compression 48.9 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. Rfe.by needs all CSS files to be minified and compressed as it can save up to 235.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (63%)

Requests Now

63

After Optimization

23

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

Accessibility Review

rfe.by accessibility score

65

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

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

rfe.by best practices score

58

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

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

SEO Factors

rfe.by SEO score

83

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rfe.by can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed English language. Our system also found out that Rfe.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

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