28 sec in total
2.4 sec
25.4 sec
199 ms
Visit winhan.com now to see the best up-to-date Winhan content and also check out these interesting facts you probably never knew about winhan.com
Visit winhan.comWe analyzed Winhan.com page load time and found that the first response time was 2.4 sec and then it took 25.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
winhan.com performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value3.0 s
79/100
25%
Value3.0 s
94/100
10%
Value90 ms
98/100
30%
Value0.016
100/100
15%
Value3.3 s
94/100
10%
2364 ms
398 ms
1023 ms
399 ms
596 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 98% of them (78 requests) were addressed to the original Winhan.com, 1% (1 request) were made to Ajax.googleapis.com and 1% (1 request) were made to Fontface.kr. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Fontface.kr.
Page size can be reduced by 500.4 kB (26%)
1.9 MB
1.4 MB
In fact, the total size of Winhan.com main page is 1.9 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. 20% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 17.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. This page needs HTML code to be minified as it can gain 2.6 kB, which is 12% 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 17.9 kB or 82% of the original size.
Potential reduce by 172.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. Obviously, Winhan needs image optimization as it can save up to 172.4 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 264.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 264.4 kB or 71% of the original size.
Potential reduce by 45.6 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. Winhan.com needs all CSS files to be minified and compressed as it can save up to 45.6 kB or 80% of the original size.
Number of requests can be reduced by 15 (19%)
78
63
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Winhan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
winhan.com
2364 ms
xe.min.css
398 ms
jquery-ui.css
1023 ms
flexslider.css
399 ms
layout.css
596 ms
style.css
452 ms
widget.css
578 ms
layout.css
779 ms
jquery.min.js
1755 ms
x.min.js
1041 ms
xe.min.js
1552 ms
webfont.js
7 ms
jquery.flexslider-min.js
1368 ms
custom.js
1164 ms
autolink.js
1229 ms
jquery-ui.min.js
2652 ms
jquery.ui.datepicker-ko.js
1380 ms
resize_image.min.js
1628 ms
bg_head.gif
213 ms
635848da36fa1f4bcbfc8bc948a8b02c.gif
403 ms
186.20130901150111.menu_normal_btn.gif
444 ms
188.20130901181433.menu_normal_btn.gif
445 ms
190.20130901181425.menu_normal_btn.gif
448 ms
192.20130901181418.menu_normal_btn.gif
600 ms
194.20130901181410.menu_normal_btn.gif
807 ms
201.20130901181402.menu_normal_btn.gif
832 ms
127.20130901150138.menu_normal_btn.gif
835 ms
145.20130901181352.menu_normal_btn.gif
852 ms
336.20130901181303.menu_normal_btn.gif
991 ms
346.20130901181957.menu_normal_btn.gif
1222 ms
151.20130901181333.menu_normal_btn.gif
1225 ms
206.20130901151457.menu_normal_btn.gif
1224 ms
128.20130901150153.menu_normal_btn.gif
1239 ms
153.20130901181453.menu_normal_btn.gif
1381 ms
155.20130901181458.menu_normal_btn.gif
1433 ms
157.20130901181501.menu_normal_btn.gif
1604 ms
341.20130901181611.menu_normal_btn.gif
1606 ms
161.20130901181634.menu_normal_btn.gif
1611 ms
129.20130901150204.menu_normal_btn.gif
1646 ms
163.20130901181639.menu_normal_btn.gif
1770 ms
165.20130901151620.menu_normal_btn.gif
1849 ms
167.20130901151636.menu_normal_btn.gif
1991 ms
169.20130901151647.menu_normal_btn.gif
1994 ms
130.20131023144004.menu_normal_btn.gif
1995 ms
171.20130901181652.menu_normal_btn.gif
2066 ms
173.20130901152127.menu_normal_btn.gif
2161 ms
175.20140306153903.menu_normal_btn.gif
2276 ms
109681.20140306153240.menu_normal_btn.gif
2378 ms
1563.20131023143836.menu_normal_btn.gif
2378 ms
btn_China.gif
2382 ms
btn_login.gif
2464 ms
btn_sns.gif
2537 ms
btn_facebook.gif
2636 ms
203.20130901152328.menu_normal_btn.jpg
4360 ms
1324.20130926220241.menu_normal_btn.jpg
3780 ms
109197.20140218142232.menu_normal_btn.jpg
3942 ms
109212.20140123114711.menu_normal_btn.jpg
4025 ms
109423.20140220160633.menu_normal_btn.jpg
4276 ms
title_new.gif
2477 ms
bullet.gif
2695 ms
196.20130901152220.menu_normal_btn.gif
3091 ms
197.20130901152239.menu_normal_btn.gif
3479 ms
198.20130901152248.menu_normal_btn.gif
3720 ms
199.20130901152258.menu_normal_btn.gif
3710 ms
css
20394 ms
banner01_title.gif
3707 ms
165x115.crop.jpg
4040 ms
208.20130906001757.menu_normal_btn.jpg
4371 ms
209.20130906001808.menu_normal_btn.jpg
4165 ms
banner02_title.gif
3853 ms
165x115.crop.jpg
4152 ms
211.20140128103314.menu_normal_btn.jpg
4747 ms
212.20130901200401.menu_normal_btn.gif
3906 ms
213.20130901200625.menu_normal_btn.gif
4050 ms
214.20130901200635.menu_normal_btn.gif
4166 ms
215.20130901200646.menu_normal_btn.gif
4257 ms
216.20130901153810.menu_normal_btn.gif
4185 ms
110709.20140408180015.menu_normal_btn.jpg
4135 ms
msg.loading.gif
4077 ms
bg_direction_nav.png
4187 ms
winhan.com 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
winhan.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
winhan.com SEO score
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
N/A
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Winhan.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Korean. Our system also found out that Winhan.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.
winhan.com
Open Graph description is not detected on the main page of Winhan. 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: