6.7 sec in total
811 ms
4.8 sec
1 sec
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.byWe 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.
dom.by performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value4.2 s
45/100
25%
Value8.6 s
17/100
10%
Value1,290 ms
18/100
30%
Value0
100/100
15%
Value13.3 s
12/100
10%
811 ms
647 ms
384 ms
778 ms
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 size can be reduced by 774.4 kB (20%)
3.9 MB
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.
Potential reduce by 514.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.
Potential reduce by 55.6 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. Dom images are well optimized though.
Potential reduce by 73.5 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.
Potential reduce by 131.4 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.
Number of requests can be reduced by 30 (38%)
80
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.
www.dom.by
811 ms
all.css
647 ms
global.js
384 ms
all.js
778 ms
analytics.js
24 ms
watch.js
22 ms
acode.js
238 ms
consultant_1.jpg
165 ms
924c6c895f84ec4f189d2b322a6be817.png
271 ms
53c0cb052d1581807ecc09a33de53ca6.png
631 ms
dd7a313340b02780611220b5dc9ce190.jpg
625 ms
5e19ea1b8500375988f14eeb1803c680.png
625 ms
ab236a7057662c9e24fc2db977c48af2.png
626 ms
22815604f759e4e0c3a50bcf623afcef.png
655 ms
941bd877d7ea1f7b6af957c1ab0f460f.png
825 ms
29c562390fb622ecde331852c9a7665a.jpg
630 ms
3412e38f2e9085d498bd82bc9886fab1.jpg
629 ms
6b6173d502706b1d47bb4dad29494f24.jpg
876 ms
691bdd1522a23aa3653eb5ca2545f5c0.jpg
823 ms
8ecf6242d107b291de5e8fc2a8bcd193.jpg
993 ms
3660d9f848b44092301b35d268a259a8.jpg
879 ms
1122700541b0bcb2730b3da512786047.jpg
806 ms
0029764128b0ac5f84777cea0ce2379a.jpg
929 ms
30d7cabffecfa154a4de36770360350e.png
1198 ms
2b91e480dfc62ad5f599e8a5bc111ab6.png
1086 ms
5621421d9f321818d65c821d675dea04.png
1257 ms
75c510e58621d2cf2a5503b3f9b94ccb.png
1388 ms
9791513a848393c29ff9503f9961f8fa.jpg
1058 ms
0b1f9ca5916b320c9ebe01f66bd89987.jpg
1124 ms
2ea3bd3d9b96ae16ba5d953dc0ce721e.jpg
1180 ms
2d8a2fd5a2e87f74e5bc93d12fae5a08.jpg
1209 ms
0b828a129cccdba0d494cac5788c6bdb.jpg
1372 ms
0942cb152e37c859adc1b395c2253321.jpg
1308 ms
097f5b5bfc5ecd800f0ad670727589f9.jpg
1322 ms
0a0fb3e3c38dae71673ba3cc08153370.jpeg
1333 ms
2dd65f287a86670c426635df32ee7cac.png
1375 ms
85c66368f8e4875eaa22a1bb4ec326e4.png
1429 ms
c94aace77dae9b35f8515e73c5ac1b5c.png
1446 ms
9a9de9bebc20ede475c565290380696f.png
1729 ms
b173b9abdb18999cbf311700bae3102d.png
1619 ms
ef5cb6e40ef93ebc6fa8c99431d133d7.png
1625 ms
autoUpdate.adriver.js
618 ms
gtm.js
62 ms
collect
33 ms
ico.png
1415 ms
collect
130 ms
2559-37edc71f9dd3f2c8b59-6d337edc71f9dd3f2c8-30892d-5d4.js
464 ms
main.js
778 ms
watch.js
43 ms
bd879f96959c46ebc409a835aac87ff2
454 ms
RobotoLight.woff
1385 ms
qDUaAaId5ga4rR6q5gBIYLzTkYrTRjcL7UTMC40UzBpNbMwLTSzMGs1CzAfD1RUiG+eRFRAAAAAAABVJLr9QAA
42 ms
xgemius.js
587 ms
ga-audiences
52 ms
wm
386 ms
RobotoMedium.ttf
1556 ms
collect
52 ms
RobotoBold.woff
1023 ms
main-page-form.jpg
1427 ms
bb8a0b1e464a9c6ab629bfc4bb0c49a6.jpg
1794 ms
a3d683ff1fbfb501337290347caef73f.jpg
1925 ms
741f59fa921fd0949994057e57c5b708.jpg
1926 ms
ed0db427b64ec549195f624c9b8edc80.jpg
1480 ms
0e8ae7be1469f95fe68b6c72c379739f.jpg
1835 ms
old.adriver.js
293 ms
getTime.js
301 ms
frame_cookie.php
297 ms
fpdata.js
132 ms
lsget.html
259 ms
adlik
192 ms
checkFlash.adriver.js
244 ms
functions.adriver.js
362 ms
firstInput.js
145 ms
rexdot.js
130 ms
d96eb691d84061568e2a05a1bf390e3f945fe92e668758fcda55e284af815d86.js
137 ms
merle.cgi
292 ms
merle.cgi
291 ms
merle.cgi
296 ms
script.js
299 ms
script.js
295 ms
script.js
434 ms
pixel.adriver.js
286 ms
makeFlash.adriver.js
285 ms
checkFB.adriver.js
287 ms
makeImage.adriver.js
286 ms
clickCoord.adriver.js
285 ms
checkOver.adriver.js
434 ms
html.adriver.js
574 ms
event.adriver.js
310 ms
dom.by accessibility score
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
[aria-hidden="true"] elements contain focusable descendents
[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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
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
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
dom.by best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
dom.by SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
RU
RU
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.
dom.by
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: