6.3 sec in total
744 ms
4.8 sec
756 ms
Welcome to aumtaekwang.com homepage info - get ready to check Aumtaekwang best content right away, or after learning these important things about aumtaekwang.com
Visit aumtaekwang.comWe analyzed Aumtaekwang.com page load time and found that the first response time was 744 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
aumtaekwang.com performance score
744 ms
217 ms
11 ms
278 ms
210 ms
Our browser made a total of 159 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Aumtaekwang.com, 30% (48 requests) were made to Blogimgs.naver.net and 18% (29 requests) were made to Blogimgs.naver.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Postfiles9.naver.net.
Page size can be reduced by 1.4 MB (50%)
2.7 MB
1.4 MB
In fact, the total size of Aumtaekwang.com main page is 2.7 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 394 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 394 B or 45% of the original size.
Potential reduce by 55.1 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. Aumtaekwang images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 74% of the original size.
Potential reduce by 273.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. Aumtaekwang.com needs all CSS files to be minified and compressed as it can save up to 273.8 kB or 84% of the original size.
Number of requests can be reduced by 99 (63%)
158
59
The browser has sent 158 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aumtaekwang. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
aumtaekwang.com
744 ms
holiland
217 ms
Frameset-981964519.js
11 ms
PostList.nhn
278 ms
NBlogHidden.nhn
210 ms
Hidden-597428542.js
5 ms
MusicPlayer-449972894.js
21 ms
LayoutTopCommon-484882993.css
13 ms
player-846d457.css
24 ms
RemoveSubDomain-dea9950.js
32 ms
Jindo152-363950062.js
31 ms
LayoutTopCommon-730083628.js
29 ms
JindoComponent-318925938.js
30 ms
PostList-1027637939.css
27 ms
gnb_quirks_euckr.nhn
96 ms
likeit_blog.css
248 ms
likeit.css
318 ms
SeViewerBlog-165931490.css
27 ms
PostTopCommon-327917359.js
93 ms
splugin.js
261 ms
PostBottomCommon-1023812380.js
89 ms
PostBottomCommon_utf8-169531666.js
107 ms
likeIt.list.js
245 ms
allowSwfForChrome-7dd9772.js
87 ms
LayoutBottomCommon-902441421.js
105 ms
spc.gif
53 ms
PostList.nhn
411 ms
%BE%F6%C1%F6.jpg
1151 ms
%BE%F6%C1%F62.jpg
1648 ms
%BE%F6%C1%F63.jpg
1508 ms
%BE%F6%C1%F6%C0%E5%B1%BA5.jpg
1794 ms
%BE%F6%C1%F6%C0%E5%B1%BA6.jpg
1095 ms
%BE%F6%C1%F64.jpg
1198 ms
%BE%F6%C1%F65.jpg
772 ms
%BE%F6%C1%F6%C0%E5%B1%BA3.jpg
1080 ms
btn_confirm2.gif
57 ms
%ED%94%84%EB%A1%9C%ED%95%84.jpg
494 ms
0004_login.png
49 ms
btn_qk_set.gif
47 ms
btn_what2.gif
47 ms
btn_clse_ly2.gif
49 ms
spc.gif
47 ms
btn_urlcopy.gif
48 ms
blank.gif
48 ms
btn_confirm.gif
60 ms
btn_cancel.gif
48 ms
btn_close.gif
46 ms
btn_thin_close.gif
46 ms
btn_close8.gif
46 ms
ico_file.gif
47 ms
btn_download2.gif
48 ms
btn_cancel3.gif
48 ms
btn_close3.gif
49 ms
btn_close5.gif
49 ms
btn_confirm.gif
49 ms
btn_cancel.gif
50 ms
btn_close_1.gif
50 ms
btn_viewexif.gif
52 ms
btn_originaldn.gif
50 ms
tit_viewexif.gif
51 ms
ico_notice2.gif
52 ms
btn_close.gif
52 ms
btn_close3.gif
53 ms
btn_close.gif
53 ms
btn_ok.gif
52 ms
btn_close2.gif
53 ms
btn_confirm_pop2.gif
53 ms
btn_cancel_pop2.gif
54 ms
%BE%F6%C1%F6%C0%E5%B1%BA.jpg
892 ms
%BE%F6%C1%F6%C0%E5%B1%BA4.jpg
1114 ms
%BE%F6%C1%F6%C0%E5%B1%BA7.jpg
1126 ms
%BE%F6%C1%F6%C0%E5%B1%BA2.jpg
1131 ms
ico_help.gif
49 ms
promo_npay.png
42 ms
%C5%B8%C0%CC%C6%B2.jpg
1269 ms
0144_966.gif
36 ms
bg_qk_ly2.gif
16 ms
0126_back1.gif
14 ms
ico_tag.gif
10 ms
sp_post_btn.png
5 ms
ico_post_sccl-by-nc-nd.png
5 ms
sp_arr1.gif
59 ms
bg_likeit2.gif
62 ms
sp_likeit_pc3.png
61 ms
0126_back2.gif
56 ms
0126_back3.gif
56 ms
0126_back4.gif
58 ms
0126_ico1_down.gif
59 ms
0126_back6.gif
59 ms
0126_back7.gif
57 ms
0126_back8_1.gif
57 ms
0126_back9.gif
59 ms
AdPostInjectAsync.nhn
333 ms
WidgetView.nhn
262 ms
btn_blogsearch.gif
17 ms
shadow.png
9 ms
shadow02.png
10 ms
bg_not_available_word.gif
17 ms
lg_photoviewer.gif
19 ms
btn_left.gif
18 ms
btn_right.gif
18 ms
btn_original2.png
17 ms
btn_close.gif
17 ms
0113_head.gif
36 ms
0113_body.gif
50 ms
0113_back.gif
18 ms
0112_image.gif
18 ms
0113_footer.gif
34 ms
WidgetListAsync.nhn
250 ms
section_connect_widget2-413879d.css
9 ms
jindo.min-78c07e0.js
5 ms
agent.ie11-6694cec.js
7 ms
BuddyConnectWidget-242001126.js
18 ms
BuddyConnectBriefWidget-898830988.js
24 ms
line_skin20_v.gif
10 ms
%C7%C1%B7%CE%C7%CA%BC%F6%C1%A4.jpg
51 ms
ico_arr2.gif
43 ms
b.gif
50 ms
ico_skin21_arr.gif
41 ms
ico_up.gif
42 ms
btn_skin20_pgn.gif
42 ms
btn_skin21_add_2.png
42 ms
btn_skin20_adm_2.png
42 ms
btn_skin20_dnld_2.png
42 ms
4459.gif
281 ms
%C7%C1%B7%CE%C7%CA.jpg
475 ms
btn_rst_clse.gif
12 ms
ico_n_photo.gif
12 ms
sp_widget_map_v4.png
13 ms
bg_country_v3.gif
25 ms
0000_icon.gif
13 ms
0002_arw.gif
13 ms
ico_npay.png
20 ms
adpost_logo.png
18 ms
ExternalWidgetRender.nhn
602 ms
ExternalWidgetRender.nhn
646 ms
ExternalWidgetRender.nhn
650 ms
ExternalWidgetRender.nhn
702 ms
100000172198060.3494.1579017311.png
330 ms
542830609108784.2568.323281702.png
206 ms
getLoginStatus.nhn
408 ms
92 ms
d93e757e1104.png
9 ms
542830609108784.2568.323281702.png
125 ms
100000172198060.3494.1579017311.png
1204 ms
promo_npay_1603.png
7 ms
clickcrD.js
8 ms
0004_menu.png
4 ms
sp_gnb_v10.png
5 ms
spi_standard_20160222.css
1029 ms
BlogTagListInfo.nhn
1239 ms
index.html
1029 ms
icon_set.gif
1025 ms
m
398 ms
likeIt.list.main.js
14 ms
sp_spi_pc.png
13 ms
likeit.css
4 ms
likeit_blog.css
5 ms
likeItServiceContentList.jsonp
430 ms
aumtaekwang.com SEO score
KO
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aumtaekwang.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 Aumtaekwang.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.
aumtaekwang.com
Open Graph description is not detected on the main page of Aumtaekwang. 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: