36.2 sec in total
2.5 sec
33.3 sec
351 ms
Welcome to totem.kr homepage info - get ready to check Totem best content right away, or after learning these important things about totem.kr
Visit totem.krWe analyzed Totem.kr page load time and found that the first response time was 2.5 sec and then it took 33.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
totem.kr performance score
2516 ms
33 ms
888 ms
670 ms
2982 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 99% of them (94 requests) were addressed to the original Totem.kr, 1% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (19.9 sec) belongs to the original domain Totem.kr.
Page size can be reduced by 400.1 kB (27%)
1.5 MB
1.1 MB
In fact, the total size of Totem.kr main page is 1.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. 25% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 51.1 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 18.9 kB, which is 32% 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 51.1 kB or 88% of the original size.
Potential reduce by 177.2 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, Totem needs image optimization as it can save up to 177.2 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 159.1 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 159.1 kB or 65% of the original size.
Potential reduce by 12.7 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. Totem.kr needs all CSS files to be minified and compressed as it can save up to 12.7 kB or 82% of the original size.
Number of requests can be reduced by 8 (9%)
87
79
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Totem. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
totem.kr
2516 ms
jquery-latest.min.js
33 ms
style.css
888 ms
menu.css
670 ms
jquery-1.7.2.min.js
2982 ms
flash.js
475 ms
navi.js
479 ms
font.css
223 ms
main_bg.jpg
554 ms
fa.png
409 ms
home.png
363 ms
btn_login.png
711 ms
btn_line.png
430 ms
btn_join.png
410 ms
btn_trans.png
700 ms
btn_cart.png
819 ms
btn_cus.png
806 ms
btn_comm.png
822 ms
logo.png
1209 ms
btn_search.png
1166 ms
r_011.jpg
3798 ms
m_m_011.jpg
3984 ms
m_m_012.jpg
4037 ms
m_m_013.jpg
3991 ms
m_m_014.jpg
3498 ms
m_m_015.jpg
3936 ms
m_m_ttl_01.jpg
4253 ms
PR14856705_size_m.jpg
5539 ms
PR14674082_size_m.jpg
5685 ms
PR18239448_size_m.jpg
5546 ms
PR9535195_size_m.jpg
5410 ms
PR18048942_size_m.jpg
5796 ms
PR15302559_size_m.jpg
5797 ms
PR13945752_size_m.jpg
5960 ms
PR8322627_size_m.jpg
6309 ms
PR12954285_size_m.jpg
6131 ms
m_r_ttl_01.jpg
5933 ms
m_r_b_01.jpg
6502 ms
m_r_ttl_02.jpg
6053 ms
m_r_b_02.jpg
7732 ms
m_pro_013-1.jpg
6855 ms
m_pro_013.jpg
6953 ms
m_m_ttl_02.jpg
6361 ms
PR11797068_size_m.jpg
6807 ms
index.asp
6235 ms
index.html
6359 ms
NanumGothic-Regular.woff2
6408 ms
NanumGothic-Bold.woff2
6615 ms
PR13882746_size_m.jpg
6764 ms
PR17376081_size_m.jpg
6655 ms
PR15559598_size_m.jpg
6735 ms
m_m_ttl_03.jpg
6877 ms
PR16118615_size_m.jpg
6737 ms
PR15824381_size_m.jpg
6976 ms
m_cus_01.jpg
6643 ms
m_cus_02.jpg
6926 ms
m_cus_03.jpg
4736 ms
m_cus_04.jpg
4591 ms
m_ttl_03.jpg
4069 ms
more.gif
4046 ms
po.gif
4050 ms
m_cus_05.jpg
4959 ms
m_cus_06.jpg
4741 ms
m_cus_07.jpg
3354 ms
foot.jpg
3765 ms
jbmenu.png
3004 ms
nav_bg.png
2946 ms
menu_01.png
2998 ms
menu_02.png
3070 ms
menu_03.png
3065 ms
menu_04.png
3122 ms
menu_05.png
3087 ms
menu_06.png
3109 ms
menu_07.png
2945 ms
foot_bg.jpg
2880 ms
jquery.min.js
4832 ms
style.css
2629 ms
jquery.min.js
3878 ms
NanumGothic-Regular.woff
2641 ms
NanumGothic-Bold.woff
2436 ms
NanumGothic-Regular.ttf
19854 ms
NanumGothic-Bold.ttf
19831 ms
iphone_1.jpg
493 ms
iphone_2.jpg
500 ms
iphone_3.jpg
527 ms
iphone_4.jpg
957 ms
iphone_1b.jpg
1404 ms
iphone_2b.jpg
1452 ms
iphone_3b.jpg
1913 ms
iphone_4b.jpg
2076 ms
01.jpg
5856 ms
02.jpg
7992 ms
03.jpg
7079 ms
04.jpg
7972 ms
05.jpg
10067 ms
totem.kr SEO score
N/A
N/A
KS_C_5601-1987
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Totem.kr 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 Totem.kr main page’s claimed encoding is ks_c_5601-1987. 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.
totem.kr
Open Graph description is not detected on the main page of Totem. 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: