6.2 sec in total
588 ms
5.4 sec
186 ms
Visit build.ru now to see the best up-to-date BUILD content for Russia and also check out these interesting facts you probably never knew about build.ru
Калькулятор ремонта. Заказ пиломатериалов. Каталоги товаров, услуг, компаний. Новости компаний. Скидки и акции. Архив статей. Тендеры и исследования. Строительные выставки.
Visit build.ruWe analyzed Build.ru page load time and found that the first response time was 588 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
build.ru performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value15.5 s
0/100
25%
Value11.7 s
4/100
10%
Value600 ms
49/100
30%
Value0.172
69/100
15%
Value17.7 s
4/100
10%
588 ms
1360 ms
257 ms
518 ms
519 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 39% of them (22 requests) were addressed to the original Build.ru, 9% (5 requests) were made to Mc.yandex.ru and 7% (4 requests) were made to Ssp.adriver.ru. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Build.ru.
Page size can be reduced by 200.9 kB (58%)
347.3 kB
146.3 kB
In fact, the total size of Build.ru main page is 347.3 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. 20% of websites need less resources to load. Javascripts take 205.3 kB which makes up the majority of the site volume.
Potential reduce by 39.8 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 39.8 kB or 80% of the original size.
Potential reduce by 1.9 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. BUILD images are well optimized though.
Potential reduce by 125.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 125.7 kB or 61% of the original size.
Potential reduce by 33.6 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. Build.ru needs all CSS files to be minified and compressed as it can save up to 33.6 kB or 84% of the original size.
Number of requests can be reduced by 21 (42%)
50
29
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of BUILD. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.
build.ru
588 ms
www.build.ru
1360 ms
reset.css
257 ms
main.css
518 ms
jquery-ui.css
519 ms
cufon-yui.js
530 ms
hlv_400.font.js
536 ms
jquery.min.js
31 ms
share.js
261 ms
func.js
520 ms
main.js
673 ms
jquery-ui.min.js
1142 ms
jquery.maxlength.js
895 ms
top100.jcn
384 ms
watch.js
181 ms
watch.js
445 ms
favicon.ico
759 ms
favicon.ico
515 ms
site_1.ico
506 ms
site_1.ico
558 ms
aluguard-logo.png
581 ms
3_0_E0E0E0FF_C0C0C0FF_0_pageviews
230 ms
logo-1.png
132 ms
montazh_laminata_kratkaya_instrukciya_01.jpg
561 ms
metallicheskie_vorota_na_zakaz_01.jpg
461 ms
dekorativnye_mramornye_stoliki_01.jpg
563 ms
icon-twitter.png
263 ms
icon-facebook.png
270 ms
icon-vkontakte.png
392 ms
main-menu-bucket.png
515 ms
search-drill.png
499 ms
login-form-keys.png
620 ms
saw.png
671 ms
top100.scn
132 ms
dc.js
31 ms
getblock
391 ms
advert.gif
84 ms
__utm.gif
13 ms
erle.cgi
280 ms
erle.cgi
282 ms
1
85 ms
index.html
468 ms
3.html
391 ms
0.gif
895 ms
3.html
389 ms
30593972
85 ms
counter
311 ms
1.js
258 ms
zagl.gif
1018 ms
pixel
20 ms
adriver-sync
264 ms
Aj0Kl_YMcfdnFohNB0R8TBA
389 ms
pixel
19 ms
sync.cgi
389 ms
sync.cgi
343 ms
sync.cgi
275 ms
sync.cgi
539 ms
build.ru accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Links do not have a discernible name
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
build.ru 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
build.ru SEO score
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Build.ru 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 Build.ru 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.
build.ru
Open Graph description is not detected on the main page of BUILD. 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: