6.1 sec in total
520 ms
4.9 sec
611 ms
Click here to check amazing S H content for Russia. Otherwise, check out these important facts you probably never knew about s-h.ru
Построить дом из клееного бруса в Москве и Подмосковье: цены на проект загородного дома из дерева с отделкой под ключ от компании «Строй Хауз». ➡ Заказать на сайте и по телефону ☎ 7 (495) 645-44-30.
Visit s-h.ruWe analyzed S-h.ru page load time and found that the first response time was 520 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
s-h.ru performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value9.8 s
0/100
25%
Value10.8 s
7/100
10%
Value3,810 ms
1/100
30%
Value0.14
79/100
15%
Value26.0 s
0/100
10%
520 ms
1394 ms
34 ms
1136 ms
271 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 60% of them (27 requests) were addressed to the original S-h.ru, 22% (10 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain S-h.ru.
Page size can be reduced by 864.2 kB (19%)
4.7 MB
3.8 MB
In fact, the total size of S-h.ru main page is 4.7 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. 65% of websites need less resources to load. Images take 3.7 MB which makes up the majority of the site volume.
Potential reduce by 64.7 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 64.7 kB or 90% of the original size.
Potential reduce by 175.4 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. S H images are well optimized though.
Potential reduce by 410.4 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 410.4 kB or 67% of the original size.
Potential reduce by 213.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. S-h.ru needs all CSS files to be minified and compressed as it can save up to 213.7 kB or 80% of the original size.
Number of requests can be reduced by 4 (15%)
27
23
The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of S 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 5 to 1 for JavaScripts and as a result speed up the page load time.
s-h.ru
520 ms
www.s-h.ru
1394 ms
css
34 ms
main.css
1136 ms
modernizr.js
271 ms
conversion.js
29 ms
js
99 ms
compiled.js
1361 ms
sh_anosino_1_0_00_00_000_ps_.jpg
929 ms
1_anosino.jpg
763 ms
2_lukyaonovo.jpg
1415 ms
3_blagovecshenka.jpg
1448 ms
4_klokovo.jpg
1376 ms
5_pushkino.jpg
923 ms
6_yaxroma.jpg
1283 ms
7_aleksandrovka_fin.jpg
1386 ms
house.svg
1079 ms
empty.png
1226 ms
phone-teaser-bg.jpg
1388 ms
pushkin.jpg
1416 ms
149 ms
gothaprobla-webfont.woff
1366 ms
K88pR3goAWT7BTt32Z01m6CWcynf_cDxXwCLxiixG1c.ttf
62 ms
DXI1ORHCpsQm3Vp6mXoaTWeP1y_Bkidl4ESyB_O2G_c.ttf
142 ms
MTP_ySUJH_bn48VBG8sNSmeP1y_Bkidl4ESyB_O2G_c.ttf
473 ms
k3k702ZOKiLJc3WVjuplzGeP1y_Bkidl4ESyB_O2G_c.ttf
475 ms
EInbV5DfGHOiMmvb1Xr-hmeP1y_Bkidl4ESyB_O2G_c.ttf
472 ms
gothapromed-webfont.woff
1405 ms
gothaprobol-webfont.woff
1406 ms
gothaproreg-webfont.woff
1406 ms
xjAJXh38I15wypJXxuGMBlwIJl2YiaXHM0xUx_ugXFg.ttf
473 ms
PRmiXeptR36kaC0GEAetxmpz0z5zL8i4lJVsvdmh4hw.ttf
469 ms
PRmiXeptR36kaC0GEAetxs48OaV_SNIXktLWq3KXug4.ttf
140 ms
PRmiXeptR36kaC0GEAetxgbEkm-f2UOALJ0ub4PpKrw.ttf
468 ms
PRmiXeptR36kaC0GEAetxpUejhVR4X9s8dmwuSBKoOY.ttf
471 ms
383 ms
watch.js
83 ms
analytics.js
133 ms
img_6073_ps800_.jpg
1004 ms
img_9663_ps800_.jpg
1004 ms
img_7843_ps800_.jpg
1185 ms
img_8581_ps800_.jpg
1105 ms
img_5536_ps800_.jpg
1346 ms
img_7492_ps800_.jpg
1232 ms
collect
13 ms
s-h.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
Image elements do not have [alt] attributes
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
s-h.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
s-h.ru 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 S-h.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 S-h.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.
s-h.ru
Open Graph description is not detected on the main page of S 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: