53.8 sec in total
1.7 sec
51.3 sec
784 ms
Click here to check amazing Miniblock content. Otherwise, check out these important facts you probably never knew about miniblock.co.kr
나노블럭 있는곳, 감성키덜트 미니블럭에 오신것을 환영합니다.
Visit miniblock.co.krWe analyzed Miniblock.co.kr page load time and found that the first response time was 1.7 sec and then it took 52.1 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 10 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
miniblock.co.kr performance score
1705 ms
424 ms
429 ms
55 ms
665 ms
Our browser made a total of 133 requests to load all elements on the main page. We found that 53% of them (70 requests) were addressed to the original Miniblock.co.kr, 18% (24 requests) were made to Img.echosting.cafe24.com and 8% (10 requests) were made to App-storage-004.cafe24.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Miniblock.co.kr.
Page size can be reduced by 782.1 kB (12%)
6.3 MB
5.5 MB
In fact, the total size of Miniblock.co.kr main page is 6.3 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. 55% of websites need less resources to load. Images take 6.2 MB which makes up the majority of the site volume.
Potential reduce by 97.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 12.4 kB, which is 11% 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 97.0 kB or 90% of the original size.
Potential reduce by 664.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. Obviously, Miniblock needs image optimization as it can save up to 664.1 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 21.0 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 21.0 kB or 69% of the original size.
Number of requests can be reduced by 16 (16%)
101
85
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Miniblock. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
miniblock.co.kr
1705 ms
common.js
424 ms
cid.generate.js
429 ms
wcslog.js
55 ms
optimizer.php
665 ms
photoslide2.app-runtime.cafe24.com
674 ms
optimizer.php
1981 ms
btn_search.gif
426 ms
4db9bb03331b1345bc21396fdb3b86b7.jpg
685 ms
blank
61 ms
dome.jpg
16079 ms
escro.gif
931 ms
ae7e006e1550c76a0c944e871d7455a9.jpg
665 ms
b699d377663f774a0638e12628286555.jpg
667 ms
27e857ce051e21865797a0b6d8476cf1.jpg
672 ms
6aa6d4083ca783990ca3269b465a1569.jpg
668 ms
79da6dde77ed01498ab269b557496054.jpg
668 ms
b22f709db64ded1695202a81ef381291.jpg
894 ms
9e5db75411aa83cba92c622d17d001c6.jpg
912 ms
9a07fc706ffe0ec09ac899d1bc5e8bb6.jpg
1585 ms
ca48427094979d8e528df30eb752bcbf.jpg
918 ms
bn_attend.gif
421 ms
btn_board_more.gif
419 ms
ico_hit.gif
422 ms
ico_new.gif
421 ms
ico_attach2.gif
431 ms
btn_desktop.gif
593 ms
btn_zoom.gif
638 ms
btn_list_cart.gif
643 ms
btn_list_option.gif
642 ms
btn_recent_prev.gif
647 ms
btn_recent_next.gif
649 ms
btn_top1.gif
827 ms
btn_top2.gif
888 ms
txt_progress.gif
887 ms
img_loading.gif
1690 ms
0ae9b5d52da6601ee767afd9f57ade37_3_top.jpg
5447 ms
sc1035.jpg
5826 ms
ge8311.jpg
19506 ms
li68166.jpg
5832 ms
li68165.jpg
1660 ms
dr618.jpg
2791 ms
dr617.jpg
2989 ms
dr616.jpg
3639 ms
dr615.jpg
4715 ms
lo9715.jpg
4372 ms
lo9714.jpg
5008 ms
lo9713.jpg
6612 ms
lo9712.jpg
5517 ms
lo9711.jpg
8587 ms
lo9543.jpg
6001 ms
lo9542.jpg
9093 ms
lo9541.jpg
7753 ms
lo9540.jpg
6398 ms
lo9539.jpg
6860 ms
lo9538.jpg
7591 ms
lo9537.jpg
8125 ms
lo9536.jpg
11189 ms
li68173.jpg
8853 ms
li68172.jpg
12522 ms
li68171.jpg
10698 ms
li68170.jpg
10334 ms
li68169.jpg
15094 ms
li68168.jpg
11540 ms
li68167.jpg
11585 ms
ge8132.jpg
20491 ms
we2421.jpg
17376 ms
we2420.jpg
16181 ms
we2415.jpg
16663 ms
we2414.jpg
20489 ms
m
854 ms
ico_util1.gif
611 ms
bg_new_count.png
613 ms
ico_util2.gif
860 ms
ico_bookmark.gif
1771 ms
ico_category1.gif
887 ms
ico_util_footer.gif
891 ms
we2413.jpg
18654 ms
4db9bb03331b1345bc21396fdb3b86b7.jpg
1737 ms
ae7e006e1550c76a0c944e871d7455a9.jpg
1718 ms
b699d377663f774a0638e12628286555.jpg
2398 ms
6aa6d4083ca783990ca3269b465a1569.jpg
2398 ms
79da6dde77ed01498ab269b557496054.jpg
2408 ms
27e857ce051e21865797a0b6d8476cf1.jpg
1794 ms
b22f709db64ded1695202a81ef381291.jpg
1698 ms
9e5db75411aa83cba92c622d17d001c6.jpg
1681 ms
ca48427094979d8e528df30eb752bcbf.jpg
1767 ms
9a07fc706ffe0ec09ac899d1bc5e8bb6.jpg
1274 ms
we2412.jpg
19842 ms
weblog.js
738 ms
bg-title.png
288 ms
sfix-ico.png
520 ms
popup_6.html
16316 ms
4db9bb03331b1345bc21396fdb3b86b7.jpg
1950 ms
ae7e006e1550c76a0c944e871d7455a9.jpg
1238 ms
27e857ce051e21865797a0b6d8476cf1.jpg
1437 ms
b22f709db64ded1695202a81ef381291.jpg
1087 ms
9e5db75411aa83cba92c622d17d001c6.jpg
1833 ms
ca48427094979d8e528df30eb752bcbf.jpg
905 ms
9a07fc706ffe0ec09ac899d1bc5e8bb6.jpg
1822 ms
b699d377663f774a0638e12628286555.jpg
1352 ms
6aa6d4083ca783990ca3269b465a1569.jpg
1603 ms
79da6dde77ed01498ab269b557496054.jpg
1838 ms
LikeCommon
15635 ms
async
14775 ms
SubCategory
14651 ms
we2411.jpg
15660 ms
we2410.jpg
15386 ms
we2373.jpg
16100 ms
we2372.jpg
19677 ms
we2371.jpg
16195 ms
we2370.jpg
16285 ms
we2369.jpg
15795 ms
sc1034.jpg
15939 ms
sc1033.jpg
16343 ms
sc1032.jpg
15304 ms
sc1031.jpg
15331 ms
lo9717.jpg
15035 ms
lo9716.jpg
14571 ms
sd8076.jpg
19639 ms
sd8075.jpg
20404 ms
0ae9b5d52da6601ee767afd9f57ade37_3_bottom.jpg
13178 ms
optimizer.php
5246 ms
copy(1459241668)-pop2.jpg
2757 ms
optimizer.php
5325 ms
m
472 ms
ge8311.jpg
19995 ms
ge8132.jpg
12136 ms
we2414.jpg
1699 ms
we2412.jpg
1714 ms
we2372.jpg
1901 ms
sd8076.jpg
19985 ms
sd8075.jpg
19984 ms
miniblock.co.kr SEO score
KO
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Miniblock.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 Miniblock.co.kr 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.
miniblock.co.kr
Open Graph description is not detected on the main page of Miniblock. 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: