Tools & Wizards About Us
rdw.by screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    59% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

rdw.by

RDW.BY - Портал для поиска работы и сотрудников в Беларуси | Работа для Вас

Page Load Speed

5.7 sec in total

First Response

840 ms

Resources Loaded

4.7 sec

Page Rendered

227 ms

rdw.by screenshot

About Website

Welcome to rdw.by homepage info - get ready to check RDW best content for Belarus right away, or after learning these important things about rdw.by

Портал 'Работа для Вас' предлагает более 10.000 свежих вакансий и 7.000 актуальных резюме. RDW.by поможет найти работодателей и соискателей

Visit rdw.by

Key Findings

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

Performance Metrics

rdw.by performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

6/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value460 ms

61/100

30%

CLS (Cumulative Layout Shift)

Value0.073

96/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

rdw.by

840 ms

17e8fd0.css

1013 ms

css

33 ms

spcjs.php

489 ms

jquery.js

1012 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 52% of them (46 requests) were addressed to the original Rdw.by, 10% (9 requests) were made to Ads.rdw.by and 9% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Rdw.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (72%)

Content Size

2.2 MB

After Optimization

635.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rdw.by main page is 2.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 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 86.2 kB

  • Original 99.3 kB
  • After minification 84.1 kB
  • After compression 13.2 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 15.2 kB, which is 15% 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 86.2 kB or 87% of the original size.

Image Optimization

-48%

Potential reduce by 218.8 kB

  • Original 456.8 kB
  • After minification 238.0 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, RDW needs image optimization as it can save up to 218.8 kB or 48% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-75%

Potential reduce by 900.7 kB

  • Original 1.2 MB
  • After minification 1.0 MB
  • After compression 308.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 900.7 kB or 75% of the original size.

CSS Optimization

-84%

Potential reduce by 397.7 kB

  • Original 473.8 kB
  • After minification 472.2 kB
  • After compression 76.0 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. Rdw.by needs all CSS files to be minified and compressed as it can save up to 397.7 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (47%)

Requests Now

68

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rdw.by

rdw.by

840 ms

17e8fd0.css

17e8fd0.css

1013 ms

css

css

33 ms

spcjs.php

spcjs.php

489 ms

jquery.js

jquery.js

1012 ms

bootstrap.js

bootstrap.js

1015 ms

share.js

share.js

260 ms

odkl_share.js

odkl_share.js

321 ms

plusone.js

plusone.js

97 ms

a6d737f.js

a6d737f.js

1011 ms

a8bd9b4.js

a8bd9b4.js

1011 ms

odkl_share.js

odkl_share.js

316 ms

17e8fd0.css

17e8fd0.css

966 ms

jquery.js

jquery.js

1288 ms

bootstrap.js

bootstrap.js

647 ms

a6d737f.js

a6d737f.js

1603 ms

a8bd9b4.js

a8bd9b4.js

319 ms

f506d4d.css

f506d4d.css

170 ms

f506d4d.css

f506d4d.css

160 ms

spc.php

spc.php

173 ms

fl.js

fl.js

319 ms

016f792.jpg

016f792.jpg

162 ms

payment_demo_1.png

payment_demo_1.png

161 ms

payment_demo_2.png

payment_demo_2.png

165 ms

i33%5Epimgpsh_thumbnail_win_distr.jpg

i33%5Epimgpsh_thumbnail_win_distr.jpg

175 ms

563712821234c.jpg

563712821234c.jpg

174 ms

56bd9ffac30e9.png

56bd9ffac30e9.png

174 ms

56a71f83a1b6f.png

56a71f83a1b6f.png

561 ms

56c566ee56e90.png

56c566ee56e90.png

562 ms

562a603cdaf8a.jpeg

562a603cdaf8a.jpeg

559 ms

562a3457374ff.png

562a3457374ff.png

560 ms

562a31f92d1dc.jpg

562a31f92d1dc.jpg

559 ms

56cc3c1c74b38.png

56cc3c1c74b38.png

560 ms

562a559d0bb2c.png

562a559d0bb2c.png

877 ms

56a8d914863b5.jpg

56a8d914863b5.jpg

736 ms

56c971ba6bcc4.jpg

56c971ba6bcc4.jpg

735 ms

5632231c2f82d.png

5632231c2f82d.png

735 ms

5633236739074.jpg

5633236739074.jpg

734 ms

56d3e8cc60676.png

56d3e8cc60676.png

874 ms

56c5ad900db22.png

56c5ad900db22.png

879 ms

56c57d80acc5c.png

56c57d80acc5c.png

1034 ms

56cc56751f47d.png

56cc56751f47d.png

878 ms

EX9HKf2xXTk

EX9HKf2xXTk

129 ms

btn_icons.png

btn_icons.png

864 ms

icons.png

icons.png

1019 ms

employers_list_bg_desctop.png

employers_list_bg_desctop.png

1020 ms

share_icons.png

share_icons.png

1022 ms

ca856a1eb42e75110515e7ccb4d9a33e.gif

ca856a1eb42e75110515e7ccb4d9a33e.gif

165 ms

lg.php

lg.php

169 ms

dtpHsbgPEm2lVWciJZ0P-A.ttf

dtpHsbgPEm2lVWciJZ0P-A.ttf

59 ms

7MygqTe2zs9YkP0adA9QQQ.ttf

7MygqTe2zs9YkP0adA9QQQ.ttf

94 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

101 ms

Uxzkqj-MIMWle-XP2pDNAA.ttf

Uxzkqj-MIMWle-XP2pDNAA.ttf

111 ms

bdHGHleUa-ndQCOrdpfxfw.ttf

bdHGHleUa-ndQCOrdpfxfw.ttf

111 ms

H1vB34nOKWXqzKotq25pcg.ttf

H1vB34nOKWXqzKotq25pcg.ttf

110 ms

b0d8404727699f06064a3fd949794510.gif

b0d8404727699f06064a3fd949794510.gif

515 ms

lg.php

lg.php

514 ms

defedaff671e1bef228134cda14dd7db.jpg

defedaff671e1bef228134cda14dd7db.jpg

829 ms

lg.php

lg.php

514 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

27 ms

www-embed-player-vflQrT_sR.css

www-embed-player-vflQrT_sR.css

70 ms

www-embed-player.js

www-embed-player.js

92 ms

016f792.jpg

016f792.jpg

886 ms

payment_demo_1.png

payment_demo_1.png

885 ms

payment_demo_2.png

payment_demo_2.png

1035 ms

payment_demo_4.png

payment_demo_4.png

1036 ms

payment_demo_3.png

payment_demo_3.png

1037 ms

yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js

yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js

306 ms

ad_status.js

ad_status.js

308 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

338 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

346 ms

sdk.js

sdk.js

387 ms

analytics.js

analytics.js

252 ms

context.js

context.js

448 ms

watch.js

watch.js

679 ms

gtm.js

gtm.js

289 ms

home_slider_prev_next.png

home_slider_prev_next.png

653 ms

5dda9f2.png

5dda9f2.png

651 ms

payment_demo_5.png

payment_demo_5.png

652 ms

collect

collect

26 ms

35 ms

xd_arbiter.php

xd_arbiter.php

131 ms

xd_arbiter.php

xd_arbiter.php

258 ms

context_static_r1065.js

context_static_r1065.js

335 ms

advert.gif

advert.gif

90 ms

70502

70502

181 ms

watch.js

watch.js

167 ms

1

1

92 ms

watch.js

watch.js

179 ms

Accessibility Review

rdw.by accessibility score

81

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

Image elements do not have [alt] attributes

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

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

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

rdw.by SEO score

80

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

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

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

rdw.by

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