1.2 sec in total
166 ms
825 ms
174 ms
Visit whr.com now to see the best up-to-date Whr content and also check out these interesting facts you probably never knew about whr.com
Visit whr.comWe analyzed Whr.com page load time and found that the first response time was 166 ms and then it took 999 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
whr.com performance score
166 ms
93 ms
71 ms
73 ms
156 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Whr.com, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (194 ms) relates to the external source Secure5.whirlpool.com.
Page size can be reduced by 467.2 kB (62%)
748.0 kB
280.8 kB
In fact, the total size of Whr.com main page is 748.0 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. 35% of websites need less resources to load. Javascripts take 406.6 kB which makes up the majority of the site volume.
Potential reduce by 76.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. This page needs HTML code to be minified as it can gain 11.9 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 76.0 kB or 81% of the original size.
Potential reduce by 221 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. Whr images are well optimized though.
Potential reduce by 268.9 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 268.9 kB or 66% of the original size.
Potential reduce by 122.1 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. Whr.com needs all CSS files to be minified and compressed as it can save up to 122.1 kB or 80% of the original size.
Number of requests can be reduced by 24 (44%)
54
30
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
secure5.whirlpool.com
166 ms
home.jsp
93 ms
mycarousel.css
71 ms
skin.css
73 ms
global_new.css
156 ms
jquery-1.10.1.min.js
153 ms
prototype-1.4.0.js
122 ms
jquery_all.js
132 ms
jquery.autocomplete.js
95 ms
lib.js
95 ms
header.jsp
123 ms
utility_javascript.jsp
148 ms
persistent_cart.jsp
147 ms
yahoo_all.js
194 ms
jquery.jcarousel.min.js
193 ms
jquery-ui-1.8.10.custom.min.js
157 ms
jquery-migrate-1.2.1.min.js
158 ms
analytics.js
135 ms
gtm.js
149 ms
logo_whirlpool.png
122 ms
btn-search.png
118 ms
blue_arrow_small.png
120 ms
btn-go-bg.png
120 ms
progress-running.gif
119 ms
btn_login_e5eaef.png
121 ms
arsSlide-epp-inactivebg.png
137 ms
ama_logolaunch_2016.jpg
162 ms
pause.png
144 ms
list_blue_bg.png
144 ms
btn_home_login.png
143 ms
thought%20bubble.jpg
144 ms
continue_button_home.png
164 ms
Loop-Logo_108x65.png
168 ms
hub_logo_ql.png
165 ms
whirlpool_ia_ql.png
166 ms
logo_footer.png
169 ms
close.gif
185 ms
loading.gif
187 ms
snav_price_res-off.png
111 ms
snav_price_res-on.png
114 ms
snav_reports-off.png
113 ms
snav_reports-on.png
115 ms
nav_product_catalog-off.png
132 ms
nav_product_catalog-on.png
132 ms
nav_check_price-off.png
135 ms
nav_check_price-on.png
137 ms
nav_new_order-off.png
137 ms
nav_new_order-on.png
140 ms
nav_manage_orders-off.png
157 ms
nav_manage_orders-on.png
158 ms
carousel_prev.png
159 ms
carousel_next.png
160 ms
next.png
159 ms
prev.png
163 ms
arsSlide-epp-activebg.png
179 ms
collect
16 ms
collect
53 ms
whr.com SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whr.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Whr.com 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.
whr.com
Open Graph description is not detected on the main page of Whr. 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: