15.4 sec in total
2.1 sec
13.1 sec
188 ms
Visit krispykreme.co.kr now to see the best up-to-date Krispykreme content for South Korea and also check out these interesting facts you probably never knew about krispykreme.co.kr
롯데리아, 엔제리너스, 크리스피크림, 플레이팅, 빌라드샬롯 브랜드 공식 홈페이지입니다.
Visit krispykreme.co.krWe analyzed Krispykreme.co.kr page load time and found that the first response time was 2.1 sec and then it took 13.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
krispykreme.co.kr performance score
2071 ms
1230 ms
467 ms
1581 ms
710 ms
Our browser made a total of 133 requests to load all elements on the main page. We found that 91% of them (121 requests) were addressed to the original Krispykreme.co.kr, 2% (3 requests) were made to Platform.twitter.com and 2% (2 requests) were made to Graph.facebook.com. The less responsive or slowest element that took the longest time to load (5.8 sec) belongs to the original domain Krispykreme.co.kr.
Page size can be reduced by 337.0 kB (12%)
2.9 MB
2.6 MB
In fact, the total size of Krispykreme.co.kr main page is 2.9 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. 45% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 44.2 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 7.0 kB, which is 13% 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 44.2 kB or 80% of the original size.
Potential reduce by 112.3 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. Krispykreme images are well optimized though.
Potential reduce by 102.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 102.6 kB or 71% of the original size.
Potential reduce by 77.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. Krispykreme.co.kr needs all CSS files to be minified and compressed as it can save up to 77.8 kB or 84% of the original size.
Number of requests can be reduced by 19 (15%)
131
112
The browser has sent 131 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Krispykreme. 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.
krispykreme.co.kr
2071 ms
main.css
1230 ms
nanumgothic.css
467 ms
jquery-1.10.1.min.js
1581 ms
default.js
710 ms
all.js
8 ms
common.js
1038 ms
jquery.easing.min.js
691 ms
bgpos.js
916 ms
main_20160229.js
1170 ms
main_facebook.js
1142 ms
default.css
468 ms
bg_header.gif
239 ms
logo.png
259 ms
bl_util_bar.gif
238 ms
bg_gnb_sub_menu.gif
228 ms
gnb_sub_menu_visual_02.png
449 ms
gnb_menu01.png
204 ms
gnb_menu02.png
408 ms
gnb_menu03.png
453 ms
gnb_menu04.png
472 ms
gnb_menu05.png
469 ms
gnb_menu06.png
516 ms
img_mainvis_stop.png
611 ms
img_mainvis_play_on.png
674 ms
img_mainvis_on.png
679 ms
bg_coolcream.jpg
1655 ms
coolcream_img01.png
937 ms
btn_detail_160226.png
772 ms
btn_main_sns01.png
814 ms
btn_main_sns02.png
897 ms
img_mainvis_off.png
904 ms
bg_berryEvent.jpg
2600 ms
berry_img01.png
1018 ms
btn_detail_160216.png
1128 ms
bg_devils.jpg
2966 ms
devils_img01.png
1172 ms
btn_detail_160129.png
1244 ms
bg_fruitstea.jpg
2055 ms
fruitstea_img01.png
1427 ms
fruitstea_img02.png
1451 ms
btn_vis_00_140227.png
1665 ms
bg_pairing.jpg
2295 ms
pairing_img01.png
1887 ms
pairing_img02.png
1900 ms
btn_detail.png
2121 ms
img_main_visual01.jpg
2852 ms
img_intro01_01.png
2259 ms
like.php
84 ms
NanumGothic-Bold.woff
149 ms
widgets.js
111 ms
kkdkorea1937
116 ms
vpc6VNjRPXV.js
24 ms
LVx-xkvaJ0b.png
22 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
135 ms
posts
618 ms
main_twitter.asp
2785 ms
img_intro02_01.png
2286 ms
img_intro02_txt_01.png
2267 ms
img_intro02_txt_02.png
2473 ms
vis_02_obj.png
3383 ms
follow_button.6a78875565a912489e9aef879c881358.en.html
48 ms
vis_02_ani_line01.png
2454 ms
vis_02_ani_line02.png
2467 ms
btn_vis01.png
2639 ms
jot
92 ms
btn_vis02.png
2650 ms
btn_go_story.png
2647 ms
vis_br_01_txt1.png
2680 ms
vis_br_01_txt2.png
2715 ms
vs_br_01_ani0.jpg
2958 ms
vs_br_01_ani1.jpg
2861 ms
btn_hotlight.png
2651 ms
btn_store.png
2800 ms
vis_br_02_txt1.png
2664 ms
vis_br_02_txt2.png
2743 ms
btn_donut_shortcut.png
2808 ms
vis_br_03_txt1.png
2779 ms
restserver.php
105 ms
vis_br_03_txt2.png
2896 ms
btn_dozen_shortcut.png
2719 ms
btn_close_story.png
2620 ms
img_main_notice.png
2446 ms
notic_partition_tit.gif
2496 ms
h3_main_notice.png
2379 ms
img_mainm_bg.jpg
2425 ms
img_tit_dotted.gif
2213 ms
h3_mainm_01.png
2250 ms
ban_control_on.png
2101 ms
2016226153239_40740.jpg
2112 ms
btn_detailview.gif
1986 ms
ban_control_off.png
2026 ms
201512115219_12198.jpg
1830 ms
h3_mainm_02.png
1901 ms
2016226152534_21856.jpg
1768 ms
2016225142618_5404.jpg
1731 ms
h3_mainm_03.png
1652 ms
201512116954_12955.jpg
1692 ms
201512116652_4104.jpg
1647 ms
2015111215412_39147.jpg
1605 ms
2015102810523_1259.jpg
1680 ms
img_mainm_bg2.jpg
1559 ms
h3_title_facebook.png
1622 ms
ico_facebook.gif
1655 ms
h3_title_twitter.png
1590 ms
btn_follow.gif
1450 ms
h3_title_instgram.png
1429 ms
qr_instgram.png
1394 ms
txt_instgram.png
1416 ms
footer_menu09.gif
1384 ms
footer_menu05.gif
1347 ms
footer_menu04.gif
1374 ms
footer_menu01.gif
1411 ms
footer_menu02.gif
1445 ms
footer_menu10.gif
1415 ms
footer_menu03.gif
1318 ms
footer_menu08.gif
1352 ms
footer_address.gif
1344 ms
footer_copyright.gif
1314 ms
btn_foot_worldwide.gif
1362 ms
h3_worldwide.gif
1413 ms
btn_pannel_close.png
1352 ms
footer_ico01.gif
1348 ms
footer_ico02.gif
1309 ms
footer_ico03.gif
1308 ms
footer_ico04.gif
1353 ms
footer_facebook.gif
1409 ms
footer_twitter.gif
1379 ms
bg_footer_line.gif
1340 ms
bl_footer_bar.gif
1317 ms
img_br_visual01.jpg
5763 ms
temp_sns02.gif
1353 ms
img_social_dotted.gif
1394 ms
krispykreme.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 Krispykreme.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 Krispykreme.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.
krispykreme.co.kr
Open Graph description is not detected on the main page of Krispykreme. 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: