8.2 sec in total
762 ms
7 sec
491 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 762 ms and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
wh.ru performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value5.2 s
22/100
25%
Value12.7 s
3/100
10%
Value360 ms
71/100
30%
Value0.196
63/100
15%
Value11.5 s
18/100
10%
762 ms
905 ms
1203 ms
283 ms
565 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 83% of them (55 requests) were addressed to the original Wh.ru, 3% (2 requests) were made to Code-ya.jivosite.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Wh.ru.
Page size can be reduced by 81.7 kB (5%)
1.6 MB
1.5 MB
In fact, the total size of Wh.ru main page is 1.6 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. 35% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 43.9 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 43.9 kB or 78% of the original size.
Potential reduce by 35.7 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 2.1 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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 38 (60%)
63
25
The browser has sent 63 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 19 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
wh.ru
762 ms
www.wh.ru
905 ms
www.wh.ru
1203 ms
5e08bc58c9.css
283 ms
jquery.fancybox.css
565 ms
style.less-fb9b3ebc-a253e820-e6dd4c89.css
846 ms
responsive.less-2793e118-a253e820-78efb0d6.css
845 ms
Basic.css
847 ms
yTQ1MQabBh
568 ms
jquery.min.js
22 ms
jquery.datetimepicker.min.js
929 ms
parsley.min.js
930 ms
Tabs.min.js
930 ms
Form.min.js
1125 ms
imageMapResizer.min.js
1124 ms
jquery.matchHeight.js
1127 ms
jquery.sudoSlider.min.js
1144 ms
jquery.fancybox.pack.js
1150 ms
jquery-ui.min.js
1744 ms
jquery.jpanelmenu.js
1405 ms
jquery.clever-infinite-scroll.js
1405 ms
script.js
1410 ms
js
70 ms
js
118 ms
tag.js
1011 ms
map-marker-black.png
574 ms
clock-24.png
584 ms
icon13.png
832 ms
icon6.png
833 ms
icon7.png
839 ms
icon8.png
857 ms
icon9.png
869 ms
icon10.png
1112 ms
icon11.png
1112 ms
slideshow_wh20.jpg
2246 ms
slideshow_wh10.jpg
1705 ms
slideshow_wh40.jpg
1723 ms
1maket2.jpg
1181 ms
232Mb_croper_ru.jpeg
1393 ms
2.jpg
1953 ms
3.jpg
1473 ms
WH-norma_small.jpg
1669 ms
WH-integra_small.jpg
1760 ms
WH-combo_small.jpg
1948 ms
WH-ArtLine_small.jpg
1988 ms
wh-thermo_small.jpg
2009 ms
WH-ultra_small.jpg
2051 ms
_DSC4933-1.jpg
2512 ms
yTQ1MQabBh
540 ms
csm_Z0403250_demidovskiy_8c22d38664.jpg
2442 ms
csm_PICT0002_9442ee24bd.jpg
2205 ms
img2.jpg
2508 ms
icon12.png
2246 ms
icon2.png
2257 ms
icon3.png
2292 ms
icon4.png
2355 ms
phone-46-24.png
2498 ms
email-24.png
2498 ms
yTQ1MQabBh
580 ms
map-marker-2-24.png
2260 ms
hit
537 ms
icon24.png
1885 ms
icon25.png
1906 ms
advert.gif
694 ms
1
140 ms
bundle_ru_RU.js
319 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
Page has valid source maps
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: