Tools & Wizards About Us
realt.by screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

realt.by

Realt: Недвижимость, коммерческая недвижимость в Минске и Беларуси

Page Load Speed

4.4 sec in total

First Response

798 ms

Resources Loaded

2.1 sec

Page Rendered

1.5 sec

realt.by screenshot

About Website

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

Недвижимость в Минске и в Беларуси. Площадка Realt предлагает большой выбор актуальных предложений аренды и продажи недвижимости в Минске и по всей Беларуси

Visit realt.by

Key Findings

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

Performance Metrics

realt.by performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

45/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value7,240 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.2 s

4/100

10%

Network Requests Diagram

realt.by

798 ms

443d9ec057c82092.css

226 ms

b49197388a6fb4e4.css

225 ms

polyfills-78c92fac7aa8fdd8.js

223 ms

webpack-38743c916e20a195.js

253 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 91% of them (52 requests) were addressed to the original Realt.by, 9% (5 requests) were made to Static.realt.by. The less responsive or slowest element that took the longest time to load (963 ms) belongs to the original domain Realt.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 490.3 kB (62%)

Content Size

788.7 kB

After Optimization

298.4 kB

  • HTML
  • Images

In fact, the total size of Realt.by main page is 788.7 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. 45% of websites need less resources to load. HTML takes 580.3 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 487.1 kB

  • Original 580.3 kB
  • After minification 579.9 kB
  • After compression 93.1 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 487.1 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 3.2 kB

  • Original 208.4 kB
  • After minification 205.3 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. Realt images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 21 (72%)

Requests Now

29

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

realt.by

realt.by

798 ms

443d9ec057c82092.css

443d9ec057c82092.css

226 ms

b49197388a6fb4e4.css

b49197388a6fb4e4.css

225 ms

polyfills-78c92fac7aa8fdd8.js

polyfills-78c92fac7aa8fdd8.js

223 ms

webpack-38743c916e20a195.js

webpack-38743c916e20a195.js

253 ms

framework-f0918f007280e2a4.js

framework-f0918f007280e2a4.js

252 ms

main-5897bb19675e7d54.js

main-5897bb19675e7d54.js

332 ms

_app-810664e27007e447.js

_app-810664e27007e447.js

334 ms

b3a13d7d-ab54a5c2b98b8382.js

b3a13d7d-ab54a5c2b98b8382.js

333 ms

89797-7c1b74adb4775be8.js

89797-7c1b74adb4775be8.js

386 ms

33412-ecccd71cb2610070.js

33412-ecccd71cb2610070.js

387 ms

84812-034fb832281f059f.js

84812-034fb832281f059f.js

442 ms

28348-9e1e77216ec0667c.js

28348-9e1e77216ec0667c.js

443 ms

16534-a115a54a5e9936b5.js

16534-a115a54a5e9936b5.js

444 ms

45891-c77c66fb574257a5.js

45891-c77c66fb574257a5.js

467 ms

26455-882a11f4a0226554.js

26455-882a11f4a0226554.js

514 ms

47475-798e15ef12397454.js

47475-798e15ef12397454.js

511 ms

17508-c4593cd11e2fe11b.js

17508-c4593cd11e2fe11b.js

552 ms

41783-c50cf6cd579cdb1b.js

41783-c50cf6cd579cdb1b.js

553 ms

68760-2f505e1ca0695517.js

68760-2f505e1ca0695517.js

554 ms

69026-f502100b5d83a456.js

69026-f502100b5d83a456.js

581 ms

33589-173f95291069c524.js

33589-173f95291069c524.js

637 ms

index-d030a42305425321.js

index-d030a42305425321.js

638 ms

_buildManifest.js

_buildManifest.js

665 ms

_ssgManifest.js

_ssgManifest.js

665 ms

polyfills-78c92fac7aa8fdd8.js

polyfills-78c92fac7aa8fdd8.js

571 ms

443d9ec057c82092.css

443d9ec057c82092.css

589 ms

b49197388a6fb4e4.css

b49197388a6fb4e4.css

499 ms

framework-f0918f007280e2a4.js

framework-f0918f007280e2a4.js

776 ms

webpack-38743c916e20a195.js

webpack-38743c916e20a195.js

523 ms

main-5897bb19675e7d54.js

main-5897bb19675e7d54.js

646 ms

b3a13d7d-ab54a5c2b98b8382.js

b3a13d7d-ab54a5c2b98b8382.js

646 ms

_app-810664e27007e447.js

_app-810664e27007e447.js

963 ms

89797-7c1b74adb4775be8.js

89797-7c1b74adb4775be8.js

590 ms

33412-ecccd71cb2610070.js

33412-ecccd71cb2610070.js

592 ms

84812-034fb832281f059f.js

84812-034fb832281f059f.js

570 ms

28348-9e1e77216ec0667c.js

28348-9e1e77216ec0667c.js

605 ms

16534-a115a54a5e9936b5.js

16534-a115a54a5e9936b5.js

717 ms

45891-c77c66fb574257a5.js

45891-c77c66fb574257a5.js

621 ms

47475-798e15ef12397454.js

47475-798e15ef12397454.js

614 ms

26455-882a11f4a0226554.js

26455-882a11f4a0226554.js

639 ms

17508-c4593cd11e2fe11b.js

17508-c4593cd11e2fe11b.js

618 ms

41783-c50cf6cd579cdb1b.js

41783-c50cf6cd579cdb1b.js

656 ms

68760-2f505e1ca0695517.js

68760-2f505e1ca0695517.js

680 ms

69026-f502100b5d83a456.js

69026-f502100b5d83a456.js

747 ms

33589-173f95291069c524.js

33589-173f95291069c524.js

685 ms

index-d030a42305425321.js

index-d030a42305425321.js

645 ms

_buildManifest.js

_buildManifest.js

673 ms

_ssgManifest.js

_ssgManifest.js

677 ms

c9c2283295.jpeg

c9c2283295.jpeg

807 ms

27daced6f2.jpg

27daced6f2.jpg

551 ms

6ad5193a7b.jpg

6ad5193a7b.jpg

560 ms

ab7ac2a9e4.jpg

ab7ac2a9e4.jpg

694 ms

19cf287d75.jpeg

19cf287d75.jpeg

577 ms

27daced6f2.jpg

27daced6f2.jpg

123 ms

6ad5193a7b.jpg

6ad5193a7b.jpg

220 ms

19cf287d75.jpeg

19cf287d75.jpeg

123 ms

Accessibility Review

realt.by accessibility score

81

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

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

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

[id] attributes on active, focusable elements are not unique

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

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

realt.by best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

realt.by SEO score

85

Search Engine Optimization Advices

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

realt.by

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