5.4 sec in total
780 ms
4.5 sec
115 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 780 ms and then it took 4.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.2 s
44/100
10%
Value8.4 s
2/100
25%
Value10.7 s
7/100
10%
Value880 ms
32/100
30%
Value0.146
77/100
15%
Value14.6 s
8/100
10%
780 ms
245 ms
498 ms
499 ms
500 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 36% of them (20 requests) were addressed to the original Build.ru, 11% (6 requests) were made to Ad.adriver.ru and 11% (6 requests) were made to Content.adriver.ru. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Build.ru.
Page size can be reduced by 169.8 kB (24%)
716.4 kB
546.6 kB
In fact, the total size of Build.ru main page is 716.4 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. 30% of websites need less resources to load. Javascripts take 413.7 kB which makes up the majority of the site volume.
Potential reduce by 33.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. 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 33.0 kB or 80% of the original size.
Potential reduce by 49 B
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 102.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 102.7 kB or 25% of the original size.
Potential reduce by 34.0 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 34.0 kB or 85% of the original size.
Number of requests can be reduced by 15 (34%)
44
29
The browser has sent 44 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 16 to 1 for JavaScripts and as a result speed up the page load time.
build.ru
780 ms
reset.css
245 ms
main.css
498 ms
jquery-ui.css
499 ms
cufon-yui.js
500 ms
hlv_400.font.js
510 ms
jquery.min.js
11 ms
share.js
257 ms
func.js
503 ms
main.js
620 ms
jquery-ui.min.js
1100 ms
jquery.maxlength.js
859 ms
api.js
35 ms
context.js
962 ms
top100.jcn
371 ms
watch.js
1 ms
top100.jcn
885 ms
share.d5b30abe919b24183022bcd01d19328c.js
135 ms
recaptcha__en.js
50 ms
3_0_E0E0E0FF_C0C0C0FF_0_pageviews
421 ms
logo-1.png
129 ms
5_priznakov_professionalnoy_stroyorganizacii_01.jpg
363 ms
kak_pravilno_podgotovit_osnovanie_pod_teplyi_pol_01.jpg
363 ms
oblicovochnoe_pokrytie_bassejna_kakoe_vybrat_01.jpg
373 ms
icon-twitter.png
250 ms
icon-vkontakte.png
256 ms
erle.cgi
391 ms
main-menu-bucket.png
367 ms
search-drill.png
472 ms
erle.cgi
361 ms
login-form-keys.png
472 ms
erle.cgi
364 ms
saw.png
562 ms
prepareCode
619 ms
erle.cgi
135 ms
erle.cgi
135 ms
erle.cgi
141 ms
counter2
282 ms
AV.js
787 ms
ad-marking.js
682 ms
dc.js
7 ms
aci.js
526 ms
prepareCode
351 ms
__utm.gif
12 ms
0.jpg
1071 ms
0.jpg
913 ms
index.html
654 ms
s.html
135 ms
event.cgi
672 ms
s.html
129 ms
event.cgi
683 ms
s.html
253 ms
event.cgi
697 ms
s.js
143 ms
zagl.gif
500 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: