13.5 sec in total
482 ms
12.7 sec
367 ms
Visit jung17.com now to see the best up-to-date JUNG 17 content and also check out these interesting facts you probably never knew about jung17.com
Visit jung17.comWe analyzed Jung17.com page load time and found that the first response time was 482 ms and then it took 13 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
jung17.com performance score
482 ms
6254 ms
607 ms
421 ms
1075 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 97% of them (75 requests) were addressed to the original Jung17.com, 1% (1 request) were made to Api.mobilis.co.kr and 1% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (6.3 sec) belongs to the original domain Jung17.com.
Page size can be reduced by 407.5 kB (14%)
2.8 MB
2.4 MB
In fact, the total size of Jung17.com main page is 2.8 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. 40% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 60.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 9.9 kB, which is 15% 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 60.0 kB or 88% of the original size.
Potential reduce by 234.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. JUNG 17 images are well optimized though.
Potential reduce by 7.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 7.5 kB or 77% of the original size.
Potential reduce by 105.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. Jung17.com needs all CSS files to be minified and compressed as it can save up to 105.6 kB or 90% of the original size.
Number of requests can be reduced by 6 (8%)
75
69
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of JUNG 17. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
jung17.com
482 ms
board_list.asp
6254 ms
607 ms
active.js
421 ms
style_0862.css
1075 ms
main_func.js
446 ms
jquery-1.4.2.js
11 ms
board.css
456 ms
top_topbg_new2.gif
289 ms
jung20_net_20160308_194813.jpg
277 ms
jung20_net_20160308_194824.jpg
260 ms
%EC%84%A0%EB%B6%88%ED%8F%B0_[3].gif
408 ms
jung20_net_20160308_194758.jpg
425 ms
twi_icon.png
493 ms
star_icon.png
506 ms
je_icon.png
551 ms
icon_chat.png
547 ms
jung16_net_20150901_175010_[1].jpg
614 ms
jung16_net_20150901_175010_[2].jpg
625 ms
jung20_net_20160202_223326.jpg
1457 ms
jung16_net_20150720_164856.jpg
970 ms
jung17_net_20150910_190136.jpg
1159 ms
jung20_com_20151103_200316.jpg
1309 ms
jung20_net_20160202_223835.jpg
1342 ms
abam1_kr_20151220_191303.jpg
1120 ms
jung16_net_20150907_192623.jpg
1564 ms
jung20_com_20151103_200507.jpg
1668 ms
jung20_com_20151113_171607.jpg
1484 ms
%EB%86%80%EC%9D%B4%ED%84%B0.jpg
1503 ms
jung20_net_20160211_182806_[2].jpg
1735 ms
jung20_com_20151103_195955.jpg
1813 ms
%ED%81%AC%EA%B8%B0%EB%B3%80%ED%99%98_%ED%99%8D%EB%8C%80%EB%AF%B8%EC%8A%A4%ED%8B%B1_[1].jpg
1811 ms
jung20_com_20151020_194836.jpg
1686 ms
jung20_com_20151103_195059.jpg
1922 ms
jung20_net_20160308_195032.jpg
1834 ms
jung20_net_20160202_223420.jpg
1857 ms
jung16_net_20150720_163714.jpg
1909 ms
%EB%86%80%EB%9F%AC%EC%99%80.jpg
1993 ms
jung20_net_20160111_230527.jpg
2149 ms
02.gif
1997 ms
ico-new.gif
2049 ms
04.gif
2073 ms
01.gif
2395 ms
03.gif
2440 ms
05.gif
2144 ms
btn_write.gif
1989 ms
btn_search.gif
1975 ms
jung20_net_20160211_182806_[1].jpg
2073 ms
bb_hu.gif
2042 ms
jung20_com_20151020_201604.jpg
2322 ms
jung20_net_20160201_190239.jpg
2726 ms
jung20_net_20151212_221306_[1].jpg
2483 ms
jung20_com_20151019_192557.jpg
2731 ms
jung20_net_20160201_184905.jpg
2072 ms
jung16_net_20150922_113600.jpg
2053 ms
jung20_net_20160201_185017.jpg
2571 ms
dasom20_net_20160301_235158_[1].jpg
2270 ms
jung20_net_20160201_185635.jpg
1945 ms
jung17_net_20150910_190136_[1].jpg
2029 ms
%EC%BB%A8_[1].gif
3032 ms
jung20_net_20160120_194832.jpg
2363 ms
jung16_net_20151005_165227.jpg
2050 ms
jung16_net_20150802_211900.jpg
2185 ms
jung20_net_20151231_154913.jpg
2030 ms
%EC%9B%B0%EC%BB%B401_[1].jpg
2348 ms
2RLObp52em.gif
2476 ms
jung20_net_20160207_143029.jpg
2035 ms
jung16_com_20150608_214321.jpg
2198 ms
NFM1BP7CNHVA0UOPPBUL_[1].gif
2718 ms
%EA%B0%9C%EA%BF%80_[1].gif
2596 ms
%EC%84%A0%EB%B6%88%ED%8F%B0_[1].gif
2318 ms
jung20_net_20160201_190120.jpg
2299 ms
ttop_jungbg8.jpg
2422 ms
mm_bars05rl_1.png
2356 ms
board_01_bar.gif
2375 ms
sub_bgbg.gif
2466 ms
sub_board_titles.gif
2434 ms
jung17.com SEO score
KO
KO
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jung17.com can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it matches the claimed language. Our system also found out that Jung17.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.
jung17.com
Open Graph description is not detected on the main page of JUNG 17. 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: