10.7 sec in total
678 ms
9.5 sec
513 ms
Visit d-h.by now to see the best up-to-date D H content for Belarus and also check out these interesting facts you probably never knew about d-h.by
Купить межкомнатные и входные двери в Минске по доступной цене: большой выбор межкомнатных и входных дверей в рассрочку недорого в каталоге интернет магазина с фото, описанием, доставкой, замером и це...
Visit d-h.byWe analyzed D-h.by page load time and found that the first response time was 678 ms and then it took 10 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
d-h.by performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value5.4 s
21/100
25%
Value9.0 s
14/100
10%
Value2,400 ms
5/100
30%
Value0
100/100
15%
Value14.3 s
9/100
10%
678 ms
51 ms
79 ms
519 ms
811 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 84% of them (61 requests) were addressed to the original D-h.by, 3% (2 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to Bitrix.info. The less responsive or slowest element that took the longest time to load (5.2 sec) belongs to the original domain D-h.by.
Page size can be reduced by 977.5 kB (51%)
1.9 MB
955.6 kB
In fact, the total size of D-h.by main page is 1.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. 50% of websites need less resources to load. Images take 773.1 kB which makes up the majority of the site volume.
Potential reduce by 99.6 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 26.7 kB, which is 23% 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 99.6 kB or 85% of the original size.
Potential reduce by 77.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. D H images are well optimized though.
Potential reduce by 520.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 520.5 kB or 73% of the original size.
Potential reduce by 279.8 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. D-h.by needs all CSS files to be minified and compressed as it can save up to 279.8 kB or 85% of the original size.
Number of requests can be reduced by 15 (22%)
69
54
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of D H. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
d-h.by
678 ms
css
51 ms
css
79 ms
kernel_main.css
519 ms
template_14791300995bd27258790d22275a58e1.css
811 ms
kernel_main.js
673 ms
core_db.js
504 ms
core_frame_cache.min.js
523 ms
jquery-1.8.3.min.js
682 ms
ajax.min.js
878 ms
template_05ac41517c5b1f573bf70f603b3f0f77.js
2112 ms
d-h.by
1597 ms
ba.js
725 ms
%D0%9D%D0%BE%D0%B2%D1%8B%D0%B9%20%D0%BB%D0%BE%D0%B3%D0%BE%D1%82%D0%B8%D0%BF-%D1%81%D1%82%D0%BE%D0%BB%D0%B1%D0%B8%D0%BA80.png
727 ms
logo_small.gif
731 ms
logo_gorod.png
728 ms
logo_vel.png
730 ms
slider1_obj.png
731 ms
m78-blizhe-mini-oval.png
1445 ms
20-mini.png
1500 ms
90_350.jpg
1192 ms
layt-mini.png
1896 ms
%D0%B0%D0%BA%D1%86%D0%B8%D1%8F.png
976 ms
%D1%85%D0%B8%D1%82-%D0%BF%D1%80%D0%BE%D0%B4%D0%B0%D0%B6.png
1190 ms
new.png
1504 ms
sasales.png
1756 ms
sofia_original_dveri_franco_poli_3%20%D0%BC%D0%B8%D0%BD%D0%B8%202.jpg
2022 ms
vkhodnyedveri.jpg
2325 ms
7_569%D0%BC%D0%B8%D0%BD%D0%B8%202.jpg
2351 ms
%D0%BC%D0%B8%D1%81%D1%82%D0%B5%D1%80%D0%B8%20%D0%BC%D0%B8%D0%BD%D0%B8.jpg
2519 ms
5e1bf7b64a7cf56ccc86e8a849cad9a1%D0%BC%D0%B8%D0%BD%D0%B8.jpg
2670 ms
%D0%91%D0%B5%D0%B7%20%D0%B8%D0%BC%D0%B5%D0%BD%D0%B8-1.jpg
2501 ms
%D0%91%D0%B5%D0%B7%20%D0%B8%D0%BC%D0%B5%D0%BD%D0%B8-1.jpg
2830 ms
%D0%91%D0%B5%D0%B7%20%D0%B8%D0%BC%D0%B5%D0%BD%D0%B8-1.jpg
2839 ms
%D0%91%D0%B5%D0%B7%20%D0%B8%D0%BC%D0%B5%D0%BD%D0%B8-1.jpg
2998 ms
%D0%91%D0%B5%D0%B7%20%D0%B8%D0%BC%D0%B5%D0%BD%D0%B8-1.jpg
2858 ms
%D0%91%D0%B5%D0%B7%20%D0%B8%D0%BC%D0%B5%D0%BD%D0%B8-1.jpg
3051 ms
%D0%91%D0%B5%D0%B7%20%D0%B8%D0%BC%D0%B5%D0%BD%D0%B8-1.jpg
3192 ms
%D0%91%D0%B5%D0%B7%20%D0%B8%D0%BC%D0%B5%D0%BD%D0%B8-1.jpg
3472 ms
%D0%91%D0%B5%D0%B7%20%D0%B8%D0%BC%D0%B5%D0%BD%D0%B8-1.jpg
3504 ms
%D0%91%D0%B5%D0%B7%20%D0%B8%D0%BC%D0%B5%D0%BD%D0%B8-1.jpg
3468 ms
%D0%91%D0%B5%D0%B7%20%D0%B8%D0%BC%D0%B5%D0%BD%D0%B8-1.jpg
3518 ms
3.jpg
3499 ms
4.jpg
3981 ms
14.jpg
4000 ms
bez-imeni_1.jpg
4042 ms
mini.jpg
3885 ms
10506_Halva.png
4368 ms
gtm.js
704 ms
1.png
4197 ms
ZL0rsgklm4
627 ms
fontawesome-webfont.woff
3910 ms
190%20+190.png
3763 ms
7.png
3650 ms
2.png
3782 ms
3.png
3952 ms
analytics.js
37 ms
watch.js
5 ms
watch.js
5 ms
bx_stat
273 ms
widget_ru_RU.js
272 ms
collect
210 ms
collect
230 ms
200-200.jpg
3865 ms
5.png
3766 ms
slider1_bg-_2.jpg
4679 ms
fon-svetlyy.jpg
5184 ms
vesna-fon-prozrach.png
4856 ms
3slider_bg.png
4676 ms
27189-mini.jpg
4506 ms
background.png
4537 ms
csf-logo.png
4139 ms
sprite-1x.png
4349 ms
d-h.by accessibility score
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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
<html> element does not have a [lang] attribute
d-h.by best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
d-h.by SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise D-h.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 D-h.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.
d-h.by
Open Graph description is not detected on the main page of D H. 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: