5 sec in total
726 ms
4.1 sec
207 ms
Welcome to junjeong.com homepage info - get ready to check Jun Jeong best content right away, or after learning these important things about junjeong.com
Visit junjeong.comWe analyzed Junjeong.com page load time and found that the first response time was 726 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
junjeong.com performance score
726 ms
211 ms
9 ms
572 ms
204 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Junjeong.com, 31% (32 requests) were made to Blogimgs.naver.net and 25% (26 requests) were made to Blogthumb2.naver.net. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Blogthumb2.naver.net.
Page size can be reduced by 941.2 kB (67%)
1.4 MB
467.7 kB
In fact, the total size of Junjeong.com main page is 1.4 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. 65% of websites need less resources to load. Javascripts take 980.3 kB which makes up the majority of the site volume.
Potential reduce by 401 B
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 401 B or 46% of the original size.
Potential reduce by 18.5 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. Jun Jeong images are well optimized though.
Potential reduce by 722.6 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 722.6 kB or 74% of the original size.
Potential reduce by 199.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. Junjeong.com needs all CSS files to be minified and compressed as it can save up to 199.6 kB or 85% of the original size.
Number of requests can be reduced by 57 (55%)
103
46
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jun Jeong. 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.
junjeong.com
726 ms
junjeong83
211 ms
Frameset-981964519.js
9 ms
PrologueList.nhn
572 ms
NBlogHidden.nhn
204 ms
Hidden-597428542.js
9 ms
MusicPlayer-449972894.js
18 ms
LayoutTopCommon-484882993.css
7 ms
player-846d457.css
14 ms
RemoveSubDomain-dea9950.js
15 ms
Jindo152-363950062.js
17 ms
LayoutTopCommon-730083628.js
25 ms
JindoComponent-318925938.js
31 ms
PrologueWebzine-71207160.css
30 ms
gnb_quirks_euckr.nhn
80 ms
allowSwfForChrome-7dd9772.js
29 ms
LayoutBottomCommon-902441421.js
28 ms
spc.gif
267 ms
PrologueList.nhn
311 ms
IMG_1426.JPG
536 ms
btn_confirm2.gif
263 ms
IMG_0233.JPG
566 ms
IMG_1439.JPG
474 ms
IMG_1424.JPG
486 ms
IMG_1381.JPG
487 ms
IMG_1386.JPG
458 ms
22.PNG
526 ms
IMG_1252.JPG
920 ms
IMG_1327.JPG
942 ms
IMG_1352.JPG
1005 ms
IMG_1344.JPG
967 ms
IMG_1342.JPG
1085 ms
IMG_1426.JPG
1010 ms
IMG_1439.JPG
1399 ms
IMG_1274.JPG
1407 ms
IMG_0430.JPG
1445 ms
IMG_1269.JPG
1463 ms
IMG_1233.JPG
1433 ms
IMG_1278.JPG
1857 ms
image.jpg
2082 ms
IMG_1185.JPG
2084 ms
IMG_1177.JPG
1949 ms
IMG_1205.JPG
2484 ms
IMG_1039.JPG
1881 ms
IMG_1171.JPG
2373 ms
11111111.PNG
2435 ms
IMG_1139.JPG
2447 ms
ico_help.gif
255 ms
0004_login.png
256 ms
btn_confirm.gif
257 ms
btn_cancel.gif
260 ms
btn_close.gif
259 ms
btn_thin_close.gif
259 ms
btn_close8.gif
259 ms
ico_file.gif
259 ms
btn_download2.gif
265 ms
btn_cancel3.gif
267 ms
btn_close3.gif
269 ms
btn_close5.gif
268 ms
btn_confirm.gif
266 ms
btn_cancel.gif
268 ms
btn_close_1.gif
268 ms
btn_viewexif.gif
270 ms
btn_originaldn.gif
270 ms
spc.gif
271 ms
tit_viewexif.gif
270 ms
ico_notice2.gif
271 ms
btn_close.gif
270 ms
btn_close3.gif
272 ms
btn_close.gif
270 ms
btn_ok.gif
271 ms
btn_close2.gif
270 ms
btn_confirm_pop2.gif
272 ms
btn_cancel_pop2.gif
271 ms
promo_npay.png
257 ms
Untitled-1.jpg
519 ms
0120_966.gif
242 ms
WidgetListAsync.nhn
389 ms
m
602 ms
btn_blogsearch.gif
36 ms
shadow.png
36 ms
shadow02.png
37 ms
bg_not_available_word.gif
37 ms
0130_back1.gif
65 ms
0130_back2.gif
60 ms
0130_back3.gif
51 ms
0130_back4.gif
57 ms
0130_back6.gif
84 ms
0130_back7.gif
78 ms
0130_back8.gif
98 ms
0130_back9.gif
110 ms
0155_head.gif
101 ms
0130_image.gif
68 ms
2417244.gif
45 ms
0158_head.gif
16 ms
IMG_0233.JPG
517 ms
0158_body.gif
14 ms
0158_icon.gif
13 ms
0158_footer.gif
11 ms
getLoginStatus.nhn
660 ms
promo_npay_1603.png
4 ms
clickcrD.js
10 ms
0004_menu.png
4 ms
sp_gnb_v10.png
5 ms
junjeong.com SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Junjeong.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Junjeong.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.
junjeong.com
Open Graph description is not detected on the main page of Jun Jeong. 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: