10.5 sec in total
1.6 sec
8.4 sec
463 ms
Visit pokpok2.com now to see the best up-to-date Pokpok 2 content for South Korea and also check out these interesting facts you probably never knew about pokpok2.com
Visit pokpok2.comWe analyzed Pokpok2.com page load time and found that the first response time was 1.6 sec and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster. This domain responded with an error, which can significantly jeopardize Pokpok2.com rating and web reputation
pokpok2.com performance score
1571 ms
409 ms
419 ms
9 ms
853 ms
Our browser made a total of 122 requests to load all elements on the main page. We found that 79% of them (96 requests) were addressed to the original Pokpok2.com, 7% (9 requests) were made to Img0001.echosting.cafe24.com and 7% (8 requests) were made to Img.echosting.cafe24.com. The less responsive or slowest element that took the longest time to load (6.1 sec) belongs to the original domain Pokpok2.com.
Page size can be reduced by 101.4 kB (83%)
121.5 kB
20.1 kB
In fact, the total size of Pokpok2.com main page is 121.5 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. 65% of websites need less resources to load. HTML takes 95.3 kB which makes up the majority of the site volume.
Potential reduce by 85.6 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 26.5 kB, which is 28% 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 85.6 kB or 90% of the original size.
Potential reduce by 61 B
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. Pokpok 2 images are well optimized though.
Potential reduce by 15.8 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 15.8 kB or 67% of the original size.
Number of requests can be reduced by 22 (19%)
117
95
The browser has sent 117 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pokpok 2. 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 as a result speed up the page load time.
pokpok2.com
1571 ms
common.js
409 ms
cid.generate.js
419 ms
wcslog.js
9 ms
optimizer.php
853 ms
photoslide2.app-runtime.cafe24.com
408 ms
optimizer.php
1408 ms
584afaaf47b8522110f28d00ab4343de.jpg
408 ms
icon_sellout.gif
399 ms
icon_12_01.gif
397 ms
txt_prog_001.gif
491 ms
comm_titleQuick_3on.gif
214 ms
comm_btnPrevQuick.gif
205 ms
comm_btnNextQuick.gif
408 ms
comm_bnrRightQuick.gif
813 ms
comm_btnTopOnQuick.png
491 ms
comm_favoriteTop.png
490 ms
comm_logoTop.png
1017 ms
comm_searchTop_L.png
622 ms
comm_searchTop_R.png
630 ms
49a0312e2e7a03c41ea90002ed217bde.png
848 ms
skin1_category24_menu.gif
834 ms
skin1_category25_menu.gif
839 ms
skin1_category26_menu.gif
1015 ms
skin1_category27_menu.gif
1043 ms
skin1_category28_menu.gif
1049 ms
skin1_category29_menu.gif
1061 ms
comm_iconCsTop.gif
1224 ms
main_bnr01.jpg
2275 ms
main_bnr02.jpg
1921 ms
main_bnr03.jpg
2095 ms
main_prdTitle_new.gif
1272 ms
prd_imgRecomm.jpg
1382 ms
pokpok2com_19.jpg
2028 ms
pokpok2com_103.jpg
1694 ms
pokpok2com_23.jpg
1801 ms
pokpok2com_32.jpg
2117 ms
pokpok2com_33.jpg
2011 ms
pokpok2com_53.jpg
2341 ms
pokpok2com_89.jpg
2430 ms
main_cateImg_01.gif
2433 ms
pokpok2com_18.jpg
2512 ms
pokpok2com_22.jpg
2541 ms
pokpok2com_27.jpg
2679 ms
icon_14_02.gif
395 ms
icon_20_02.gif
396 ms
icon_06_01.gif
395 ms
icon_01_08.gif
397 ms
icon_02_01.gif
404 ms
icon_05_01.gif
579 ms
icon_22_01.gif
590 ms
icon_lock.gif
592 ms
icon_cash.gif
397 ms
btn_list_cart.gif
397 ms
btn_list_option.gif
398 ms
img_loading_bar.gif
805 ms
main_cateImg_02.gif
2758 ms
pokpok2com_35.jpg
2440 ms
pokpok2com_36.jpg
2632 ms
584afaaf47b8522110f28d00ab4343de.jpg
390 ms
pokpok2com_50.jpg
2529 ms
img-loading.gif
201 ms
m
617 ms
bg_footer_util.gif
199 ms
NanumGothic.woff
6090 ms
pokpok2com_51.jpg
2365 ms
main_cateImg_03.gif
2399 ms
pokpok2com_63.jpg
2564 ms
pokpok2com_64.jpg
2620 ms
584afaaf47b8522110f28d00ab4343de.jpg
1560 ms
pokpok2com_75.jpg
2462 ms
main_cateImg_04.gif
2259 ms
pokpok2com_76.jpg
2516 ms
pokpok2com_77.jpg
2651 ms
pokpok2com_78.jpg
2591 ms
pokpok2com_79.jpg
2639 ms
main_cateImg_05.gif
2440 ms
pokpok2com_80.jpg
2726 ms
pokpok2com_81.jpg
2633 ms
weblog.js
614 ms
bg-title.png
200 ms
sfix-ico.png
199 ms
async
2611 ms
SubCategory
2542 ms
pokpok2com_82.jpg
2234 ms
pokpok2com_83.jpg
2391 ms
main_cateImg_06.gif
2138 ms
pokpok2com_84.jpg
2274 ms
pokpok2com_85.jpg
2107 ms
pokpok2com_86.jpg
2038 ms
pokpok2com_87.jpg
2150 ms
main_boardTitle_1.gif
2063 ms
main_boardTitle_2.gif
2004 ms
pokpok2com_18.jpg
1972 ms
pokpok2com_102.jpg
2045 ms
pokpok2com_103.jpg
1976 ms
main_boardTitle_3.gif
1997 ms
b686a440b3a1aef7bb91b5d75120027c.jpg
1915 ms
main_boardTitle_4.gif
1932 ms
main_bnr_04.jpg
1928 ms
main_bnr_05.jpg
2055 ms
eeff8e2597778505a241f72ca6395ba7.png
1892 ms
comm_bankinfoFooter.png
1880 ms
comm_iconFooter_1_1.png
1890 ms
comm_iconFooter_1_2.png
1812 ms
comm_iconFooter_1_3.png
1763 ms
comm_iconFooter_1_4.png
1729 ms
comm_iconPG.png
1763 ms
comm_btnPgOKFooter.gif
1746 ms
comm_logoFooter.png
1632 ms
comm_iconGroupFooter_2_1.png
1660 ms
comm_iconGroupFooter_2_2.png
1581 ms
comm_iconGroupFooter_2_3.png
1590 ms
comm_iconGroupFooter_2_4.png
1612 ms
comm_titleQuick_1on.gif
1600 ms
bg_util.gif
1586 ms
bg_util2.gif
1548 ms
mainBoardBg.gif
1570 ms
icon_dot04.gif
1580 ms
bottomBg.gif
1607 ms
footer_bannerGroup_03.png
1505 ms
comm_pgFooter.png
1473 ms
pokpok2.com SEO score
JA
KO
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pokpok2.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed Korean language. Our system also found out that Pokpok2.com 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.
pokpok2.com
Open Graph description is not detected on the main page of Pokpok 2. 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: