10.6 sec in total
2.3 sec
7.4 sec
914 ms
Click here to check amazing Wangjahanger content for South Korea. Otherwise, check out these important facts you probably never knew about wangjahanger.com
Since 1978 국민브랜드 왕자행거입니다.
Visit wangjahanger.comWe analyzed Wangjahanger.com page load time and found that the first response time was 2.3 sec and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
wangjahanger.com performance score
name
value
score
weighting
Value8.6 s
0/100
10%
Value33.7 s
0/100
25%
Value25.6 s
0/100
10%
Value2,730 ms
3/100
30%
Value0.265
46/100
15%
Value40.7 s
0/100
10%
2279 ms
461 ms
688 ms
463 ms
473 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 95% of them (94 requests) were addressed to the original Wangjahanger.com, 1% (1 request) were made to Wcs.naver.net and 1% (1 request) were made to Pgweb.dacom.net. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Wangjahanger.com.
Page size can be reduced by 488.7 kB (14%)
3.5 MB
3.1 MB
In fact, the total size of Wangjahanger.com main page is 3.5 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. 60% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 49.2 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 49.2 kB or 80% of the original size.
Potential reduce by 267.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. Wangjahanger images are well optimized though.
Potential reduce by 135.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 135.4 kB or 70% of the original size.
Potential reduce by 36.8 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. Wangjahanger.com needs all CSS files to be minified and compressed as it can save up to 36.8 kB or 86% of the original size.
Number of requests can be reduced by 15 (16%)
96
81
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wangjahanger. 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 from 5 to 1 for CSS and as a result speed up the page load time.
wangjahanger.com
2279 ms
common.css
461 ms
common.js
688 ms
embed.js
463 ms
ajax.js
473 ms
json.js
500 ms
rollover.js
690 ms
user_func.js
690 ms
menu.css
722 ms
jquery.js
1496 ms
menu.js
919 ms
jquery.bxslider.css
685 ms
c_jquery.bxslider.css
690 ms
jquery.bxslider.min.js
949 ms
popup_main.js.asp
725 ms
wcslog.js
7 ms
escrowValid.js
760 ms
dummy.asp
453 ms
pr_t.gif
1517 ms
lo.jpg
453 ms
topmenu_search_button2.gif
456 ms
160226_b.jpg
1200 ms
20160225_ss_18.jpg
1625 ms
11.jpg
1381 ms
1.jpg
2056 ms
5.jpg
1660 ms
NEW_1(1).jpg
1544 ms
NEW_2(1).jpg
1665 ms
NEW_3(1).jpg
1817 ms
left_i.gif
1795 ms
right_i.gif
1848 ms
dressroom_%EC%83%8C%EB%B2%A0.jpg
2367 ms
dressroom03.gif
2640 ms
dressroom01.gif
2791 ms
left_i(0).gif
2045 ms
right_i(0).gif
2075 ms
BEST_160104-4_05.jpg
2273 ms
best02(0).gif
2731 ms
best03(0).gif
2756 ms
left_i(1).gif
2502 ms
right_i(1).gif
2601 ms
b1.jpg
2731 ms
1(0).jpg
2839 ms
2(0).jpg
2871 ms
1.gif
2958 ms
2.gif
2959 ms
pr_t_1.gif
1500 ms
pr1.gif
1354 ms
pr2.gif
1357 ms
pr3.gif
1358 ms
pr4.gif
1358 ms
pr5.gif
1508 ms
exec_getTopmenuBox.asp
2983 ms
3.gif
3025 ms
4.gif
2872 ms
sothong.gif
2898 ms
hwoo.gif
2976 ms
guide_ico(0).gif
2942 ms
ranking_ico(0).gif
2787 ms
notice_event.gif
2853 ms
btm_board_icon.gif
2876 ms
find.gif
2875 ms
escrowValid.js
745 ms
new.gif
2586 ms
m
504 ms
ngc16.nsm-corp.com
506 ms
main_rolling_goods.asp
2255 ms
main_rolling_goods.asp
2104 ms
main_rolling_goods.asp
2024 ms
n_e_bottom.gif
1940 ms
find_bottom.gif
1930 ms
home_top.gif
1990 ms
logo_company.gif
1881 ms
facebook.gif
1890 ms
su.gif
1949 ms
cs_back.gif
1772 ms
bx_loader.gif
1776 ms
bg_pager.png
1805 ms
bg_pager1.png
1621 ms
topicon_02.gif
935 ms
topicon_03.gif
1031 ms
topicon_04.gif
1068 ms
topicon_06.gif
1058 ms
topicon_07.gif
1109 ms
common.css
687 ms
rolling.js
718 ms
dummy.asp
238 ms
NHC-793-2_500.jpg
254 ms
NHC-790_500.jpg
241 ms
NHC-791_791-1_500(1).jpg
242 ms
NHC-792-1_500.jpg
240 ms
NHC772_500.jpg
473 ms
NHC-781_500.jpg
664 ms
NHC-758-1_550.jpg
472 ms
NHC-753(PG)_500.jpg
470 ms
NHC-785_500.jpg
474 ms
NHC-774_500.jpg
504 ms
NHC-767-1_500.jpg
700 ms
NHC-752(PE)_500.jpg
703 ms
wangjahanger.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
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
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.
wangjahanger.com 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
Page has valid source maps
wangjahanger.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
KO
N/A
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wangjahanger.com can be misinterpreted by Google and other search engines. Our service has detected that Korean 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 Wangjahanger.com main page’s claimed encoding is euc-kr. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
wangjahanger.com
Open Graph description is not detected on the main page of Wangjahanger. 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: