Report Summary

  • 37

    Performance

    Renders faster than
    57% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

dom.by

Дом.by — строительный портал Беларуси: товары и услуги для дома, ремонта и строительства

Page Load Speed

6.7 sec in total

First Response

811 ms

Resources Loaded

4.8 sec

Page Rendered

1 sec

dom.by screenshot

About Website

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

Крупнейший каталог строительных компаний в Беларуси. Служба заказов товаров и услуг для дома и дачи.

Visit dom.by

Key Findings

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

Performance Metrics

dom.by performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

45/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value1,290 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.3 s

12/100

10%

Network Requests Diagram

www.dom.by

811 ms

all.css

647 ms

global.js

384 ms

all.js

778 ms

analytics.js

24 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Dom.by, 53% (47 requests) were made to Static.dom.by and 10% (9 requests) were made to Mh8.adriver.ru. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Static.dom.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 774.4 kB (20%)

Content Size

3.9 MB

After Optimization

3.1 MB

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

HTML Optimization

-91%

Potential reduce by 514.0 kB

  • Original 563.1 kB
  • After minification 246.3 kB
  • After compression 49.0 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 316.8 kB, which is 56% 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 514.0 kB or 91% of the original size.

Image Optimization

-2%

Potential reduce by 55.6 kB

  • Original 3.0 MB
  • After minification 3.0 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. Dom images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 73.5 kB

  • Original 113.1 kB
  • After minification 103.3 kB
  • After compression 39.7 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 73.5 kB or 65% of the original size.

CSS Optimization

-72%

Potential reduce by 131.4 kB

  • Original 182.1 kB
  • After minification 182.0 kB
  • After compression 50.7 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. Dom.by needs all CSS files to be minified and compressed as it can save up to 131.4 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (38%)

Requests Now

80

After Optimization

50

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

Accessibility Review

dom.by accessibility score

54

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-hidden="true"] elements contain focusable descendents

High

[role] values are not valid

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

Form elements do not have associated labels

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.

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

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

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

dom.by SEO score

90

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

    RU

  • Encoding

    UTF-8

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