8.5 sec in total
1.4 sec
6.3 sec
773 ms
Visit magmakorea.co.kr now to see the best up-to-date Magmakorea content and also check out these interesting facts you probably never knew about magmakorea.co.kr
도메인, 도메인등록, 퀵돔등록, 도메인연장, 도메인이전, 무료 파킹, 무료포워딩 제공, 국내 최저가 도메인 서비스 제공, 웹호스팅, 서버호스팅, 홈페이지제작, 쇼핑몰, 서버, IDC
Visit magmakorea.co.krWe analyzed Magmakorea.co.kr page load time and found that the first response time was 1.4 sec and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
magmakorea.co.kr performance score
1396 ms
384 ms
386 ms
11 ms
602 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 81% of them (71 requests) were addressed to the original Magmakorea.co.kr, 7% (6 requests) were made to Img.echosting.cafe24.com and 6% (5 requests) were made to Img0001.echosting.cafe24.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Magmakorea.co.kr.
Page size can be reduced by 76.5 kB (20%)
388.9 kB
312.5 kB
In fact, the total size of Magmakorea.co.kr main page is 388.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 302.8 kB which makes up the majority of the site volume.
Potential reduce by 60.7 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 11.9 kB, which is 17% 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.7 kB or 88% of the original size.
Potential reduce by 10.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. Magmakorea images are well optimized though.
Potential reduce by 5.3 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 5.3 kB or 30% of the original size.
Number of requests can be reduced by 25 (29%)
87
62
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Magmakorea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
magmakorea.co.kr
1396 ms
common.js
384 ms
cid.generate.js
386 ms
wcslog.js
11 ms
optimizer.php
602 ms
optimizer.php
1020 ms
go.png
384 ms
against_posi_02.jpg
773 ms
against_login_01.jpg
389 ms
against_login_02.jpg
387 ms
against_posi_06.jpg
397 ms
against_posi_07.jpg
574 ms
against_posi_08.jpg
577 ms
category_01.jpg
771 ms
category_03.jpg
587 ms
category_04.jpg
764 ms
category_05.jpg
767 ms
category_06.jpg
777 ms
category_07.jpg
954 ms
category_08.jpg
956 ms
category_09.jpg
961 ms
category_10.jpg
963 ms
category_11.jpg
967 ms
category_12.jpg
1010 ms
category_13.jpg
1143 ms
category_14.jpg
1145 ms
category_15.jpg
1151 ms
category_16.jpg
1152 ms
category_17.jpg
1156 ms
category_18.jpg
1204 ms
category_19.jpg
1332 ms
category_20.jpg
1334 ms
category_21.jpg
1342 ms
category_22.jpg
1345 ms
category_23.jpg
1347 ms
against_board_01.jpg
1398 ms
against_board_02.jpg
1522 ms
against_board_03.jpg
1525 ms
against_board_04.jpg
1532 ms
against_board_05.jpg
1536 ms
bg_prdTitle.gif
399 ms
icon_22_01.gif
656 ms
mt_black_middle.gif
1170 ms
txt_prog_001.gif
640 ms
icon_12_01.gif
642 ms
icon_03_02.gif
642 ms
icon_14_02.gif
641 ms
icon_19_01.gif
642 ms
btn_prd_zoom.gif
398 ms
icon_new_p.gif
399 ms
btn_bag.gif
398 ms
btn_option.gif
401 ms
icon_rec.gif
400 ms
img_loading_bar.gif
1048 ms
m
607 ms
against_left_01.jpg
1265 ms
against_left_02.jpg
1224 ms
against_left_05.jpg
1343 ms
against_posi_01.jpg
1343 ms
against_posi_09.jpg
1339 ms
against_main_02.jpg
2121 ms
against_main_08.jpg
1359 ms
magmakorea_92.jpg
2978 ms
magmakorea_14.jpg
1340 ms
magmakorea_93.jpg
1570 ms
magmakorea_24.jpg
1166 ms
magmakorea_77.jpg
1552 ms
magmakorea_74.jpg
1544 ms
weblog.js
636 ms
async
1594 ms
magmakorea_68.jpg
1747 ms
magmakorea_4.jpg
1757 ms
against_main_09.jpg
1774 ms
magmakorea_89.jpg
3669 ms
magmakorea_66.jpg
1738 ms
magmakorea_16.jpg
1753 ms
magmakorea_15.png
2142 ms
magmakorea_101.jpg
1973 ms
magmakorea_76.jpg
1920 ms
btn_c_view.gif
1885 ms
against_16.jpg
1935 ms
9a0529278aabe0fc1cd08d9d2c7b1867.jpg
1945 ms
agiainst_quickR_02.jpg
1974 ms
agiainst_quickR_03.jpg
2111 ms
agiainst_quickR_04.jpg
2121 ms
agiainst_quickR_05.jpg
2088 ms
btn_todayprev.gif
1986 ms
btn_todaynext.gif
2123 ms
magmakorea.co.kr SEO score
![]()
KO
![]()
KO
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Magmakorea.co.kr 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 Magmakorea.co.kr 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.
magmakorea.co.kr
Open Graph description is not detected on the main page of Magmakorea. 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: