5.4 sec in total
530 ms
4.3 sec
582 ms
Visit wh.ru now to see the best up-to-date Wh content for Russia and also check out these interesting facts you probably never knew about wh.ru
Компания «Woodhouse» - изготовление, продажа, доставка и монтаж деревянных окон в Москве. Гибкие цены на окна из дерева со стеклопакетом от производителя для дома и дачи.
Visit wh.ruWe analyzed Wh.ru page load time and found that the first response time was 530 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
wh.ru performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value5.8 s
15/100
25%
Value12.3 s
3/100
10%
Value2,420 ms
5/100
30%
Value0.22
57/100
15%
Value15.0 s
7/100
10%
530 ms
2313 ms
299 ms
293 ms
293 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 53% of them (42 requests) were addressed to the original Wh.ru, 10% (8 requests) were made to Ssl.gstatic.com and 9% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Wh.ru.
Page size can be reduced by 567.4 kB (51%)
1.1 MB
535.5 kB
In fact, the total size of Wh.ru main page is 1.1 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. 55% of websites need less resources to load. Javascripts take 548.6 kB which makes up the majority of the site volume.
Potential reduce by 66.3 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 66.3 kB or 75% of the original size.
Potential reduce by 13.2 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. Wh images are well optimized though.
Potential reduce by 385.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 385.5 kB or 70% of the original size.
Potential reduce by 102.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. Wh.ru needs all CSS files to be minified and compressed as it can save up to 102.4 kB or 83% of the original size.
Number of requests can be reduced by 44 (57%)
77
33
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wh. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
wh.ru
530 ms
www.wh.ru
2313 ms
stylesheet_3a717cabce.css
299 ms
jquery.ui.theme.css
293 ms
jquery.ui.datepicker.css
293 ms
javascript_9a38f34785.js
291 ms
jquery.min.js
12 ms
jquery.fancybox-1.3.4.css
292 ms
jquery.easing-1.3.pack.js
369 ms
jquery.mousewheel-3.0.4.pack.js
416 ms
jquery.fancybox-1.3.4.js
547 ms
jquery.main.js
423 ms
jquery-ui.min.js
24 ms
jquery.ui.datepicker-ru.min.js
29 ms
jquery.ui.all.min.css
19 ms
all.css
414 ms
platform.js
88 ms
jquery-ui.min.js
131 ms
jquery.ui.datepicker.min.js
386 ms
jquery.validationEngine-en.js
251 ms
jquery.validationEngine.js
444 ms
tabs.js
301 ms
form.js
385 ms
gplus-32.png
19 ms
logo
317 ms
bg-img-new1.jpg
515 ms
icon01.png
193 ms
icon02.png
195 ms
icon03.png
190 ms
icon05.png
195 ms
icon04.png
204 ms
woodeuro3.jpg
509 ms
woodeuro2.jpg
400 ms
okna_dlja_zagorodnogo_doma.jpg
553 ms
listvennica.jpg
562 ms
materialy.jpg
582 ms
wh-integra.jpg
536 ms
RTEmagicC_Img_6026_02.jpg
638 ms
img13.jpg
769 ms
bg-top-panel.png
654 ms
logo.png
677 ms
none.gif
690 ms
bg-white.png
701 ms
bg-white-block.png
749 ms
bg-title.png
781 ms
hit
301 ms
sdk.js
112 ms
selector01.png
741 ms
bg-title-box.png
758 ms
bg-title-box-r.png
758 ms
bg-footer.gif
932 ms
analytics.js
92 ms
cb=gapi.loaded_0
43 ms
cb=gapi.loaded_1
42 ms
subscribe_embed
136 ms
control.png
713 ms
collect
61 ms
postmessageRelay
82 ms
www-subscribe-embed-vflTum1sJ.css
112 ms
photo.jpg
159 ms
www-subscribe-embed.js
121 ms
hit
151 ms
135 ms
xd_arbiter.php
67 ms
xd_arbiter.php
82 ms
3193398744-postmessagerelay.js
50 ms
rpc:shindig_random.js
217 ms
www-hitchhiker-vflvB63an.png
41 ms
cb=gapi.loaded_0
27 ms
cb=gapi.loaded_2
7 ms
border_3.gif
11 ms
subscribe_embed
70 ms
spacer.gif
9 ms
border_3.gif
4 ms
bubbleSprite_3.png
5 ms
bubbleDropR_3.png
9 ms
bubbleDropB_3.png
8 ms
cb=gapi.loaded_0
12 ms
www-subscribe-embed-card-vflqARhQ4.css
12 ms
www-subscribe-embed-card.js
15 ms
wh.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
wh.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
Missing source maps for large first-party JavaScript
wh.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
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wh.ru 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 Wh.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.
wh.ru
Open Graph description is not detected on the main page of Wh. 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: