16.4 sec in total
3 sec
13 sec
360 ms
Click here to check amazing Epik Go content for United States. Otherwise, check out these important facts you probably never knew about epik.go.kr
Visit epik.go.krWe analyzed Epik.go.kr page load time and found that the first response time was 3 sec and then it took 13.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
epik.go.kr performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value11.5 s
0/100
25%
Value12.4 s
3/100
10%
Value430 ms
65/100
30%
Value0.014
100/100
15%
Value11.7 s
18/100
10%
2984 ms
422 ms
435 ms
472 ms
469 ms
Our browser made a total of 166 requests to load all elements on the main page. We found that 68% of them (113 requests) were addressed to the original Epik.go.kr, 11% (19 requests) were made to Static.xx.fbcdn.net and 8% (13 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (6.4 sec) belongs to the original domain Epik.go.kr.
Page size can be reduced by 194.4 kB (20%)
971.4 kB
777.0 kB
In fact, the total size of Epik.go.kr main page is 971.4 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. 70% of websites need less resources to load. Images take 726.9 kB which makes up the majority of the site volume.
Potential reduce by 44.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 8.3 kB, which is 15% 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.7 kB or 81% of the original size.
Potential reduce by 25.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. Epik Go images are well optimized though.
Potential reduce by 110.5 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 110.5 kB or 64% of the original size.
Potential reduce by 13.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. Epik.go.kr needs all CSS files to be minified and compressed as it can save up to 13.7 kB or 78% of the original size.
Number of requests can be reduced by 48 (29%)
165
117
The browser has sent 165 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Epik Go. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
index.do
2984 ms
basic.css
422 ms
layout.css
435 ms
header.css
472 ms
index.css
469 ms
nivo-slider.css
475 ms
jquery-1.7.2.min.js
2235 ms
util.js
638 ms
common.js
689 ms
menu.js
695 ms
snssend.js
698 ms
menu_model2.js
844 ms
jquery.nivo.slider.pack.js
911 ms
main.css
922 ms
popupzone.js
925 ms
js_rolling.js
1050 ms
all.js
21 ms
wrapbg.gif
576 ms
mainlogo.png
230 ms
search_btn.gif
212 ms
topmenu_01.png
234 ms
submenu1_01.gif
227 ms
submenu1_02.gif
207 ms
submenu1_03.gif
418 ms
topmenu_02.png
422 ms
submenu2_01.gif
573 ms
submenu2_02.gif
573 ms
submenu2_03.gif
573 ms
topmenu_03.png
630 ms
submenu3_01.gif
649 ms
submenu3_02.gif
673 ms
submenu3_03.gif
683 ms
submenu3_04.gif
687 ms
topmenu_04.png
712 ms
submenu4_01.gif
832 ms
submenu4_02.gif
840 ms
submenu4_03.gif
895 ms
submenu4_04.gif
908 ms
submenu4_05.gif
913 ms
topmenu_05.png
951 ms
submenu5_01.gif
1033 ms
submenu5_02.gif
1045 ms
submenu5_03.gif
1117 ms
submenu5_04.gif
1135 ms
submenu5_05.gif
1139 ms
topmenu_06.png
1189 ms
submenu6_01.gif
1237 ms
submenu6_02.gif
1255 ms
submenu6_03.gif
1339 ms
submenu6_04.gif
1362 ms
submenu6_05.gif
1366 ms
submenu6_06.gif
1428 ms
analytics.js
31 ms
150 ms
collect
32 ms
xd_arbiter.php
39 ms
xd_arbiter.php
57 ms
widgets.js
38 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
27 ms
syndication
111 ms
415273987438964737
408 ms
like_box.php
215 ms
submenu6_07.gif
1263 ms
topmenu_07.png
1360 ms
submenu7_01.gif
1369 ms
submenu7_02.gif
1371 ms
submenu7_03.gif
1441 ms
jTuqQ-OPDr6.css
47 ms
n370yiaI2G6.css
53 ms
dbNRhrdsQao.css
51 ms
1-xIpmMldel.css
59 ms
_rx8naC75Dy.js
67 ms
x5F9OMjKyLw.js
80 ms
ICDbTSzjQEg.js
80 ms
TTCre3391I0.js
91 ms
njO1TPvGzoR.js
91 ms
b_6HNn_J2BZ.js
93 ms
7cm7D75Y0Sf.js
96 ms
rFmE1g6Dkoz.js
101 ms
336JejShbZp.js
94 ms
submenu7_04.gif
1260 ms
submenu7_05.gif
1251 ms
68657_514058365285249_1978202253_n.png
84 ms
222110_514059881951764_1031638740_n.png
23 ms
12647029_1123628560994890_8974907524955209001_n.jpg
25 ms
12670073_1121319974559082_5607532266388176733_n.jpg
26 ms
12647243_1117159274975152_2041941259562911785_n.jpg
27 ms
10003332_1097766786914401_4078310134210896023_n.jpg
25 ms
12239652_1080945391929874_2945170922904771837_n.jpg
27 ms
wL6VQj7Ab77.png
18 ms
s7jcwEQH7Sx.png
18 ms
QDwYpIaRyfG.png
18 ms
a-ZN6WoEOje.png
17 ms
submenu7_06.gif
1220 ms
submenu7_07.gif
1250 ms
1389072156159_193
2162 ms
1389072166582_113
2311 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
8 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
11 ms
I6-MnjEovm5.js
8 ms
vlXaquuXMrr.js
206 ms
te30kzeoan7gk9wlc523_normal.jpeg
55 ms
CScDlRI1_normal.jpeg
51 ms
CaawTwgUMAAE3lP.jpg:small
53 ms
CaHjzKuUAAAN9mj.jpg:small
54 ms
CZjakI3UUAERzCE.jpg:small
56 ms
CUJ0zlLUEAAx2Fe.jpg:small
56 ms
CRUz2LuVEAAiB1C.jpg:small
53 ms
CRGmK3PUYAAj9qp.jpg:small
60 ms
CPF51peUcAA2GeW.jpg:small
58 ms
COg8ARIU8AA0m8q.jpg:small
58 ms
CNy8DABUkAAXFpE.jpg:small
59 ms
CMCO6ipUsAERGYZ.jpg:small
60 ms
CI35sq-UkAA1sfA.jpg:small
59 ms
1389073936854_725
2217 ms
linediv_img_01.gif
3068 ms
linediv_img_02.gif
1346 ms
linediv_img_03.gif
1371 ms
linediv_img_04.gif
1784 ms
linediv2_tit_01.gif
1573 ms
linediv2_tit_02.gif
1682 ms
1450744889744_268_THUMB
1862 ms
jot
25 ms
linediv2_tit_03.gif
1846 ms
btn_popup_play.png
2023 ms
btn_popup_stop.png
2052 ms
num_on.png
2018 ms
linediv3_img_01.gif
2069 ms
more_btn01.gif
2041 ms
linediv3_img_02.gif
2271 ms
linediv3_img_03.gif
2297 ms
more_btn02.gif
2061 ms
linediv3_img_04.gif
2313 ms
more_btn03.gif
2108 ms
linediv4_tit_01.gif
2174 ms
contactus.gif
2248 ms
socialfb_btn.gif
2248 ms
socialtwt_btn.gif
2292 ms
socialyou_btn.gif
2234 ms
email_btn.gif
2246 ms
linediv4_tit_02.gif
2361 ms
1443682861316_859
4098 ms
facebook_tit.png
2297 ms
twt_tit.png
2296 ms
banner_left_btn.gif
2248 ms
banner_stop_btn.gif
2255 ms
banner_right_btn.gif
2397 ms
1395967161417_884
2326 ms
1386399545055_549
2300 ms
1386399537075_622
2106 ms
1386399529258_436
2081 ms
1386399504231_435
2029 ms
1386399511285_316
1874 ms
1386399518886_988
1843 ms
epik_flogo.png
1624 ms
niied_logo.png
1608 ms
header_bg.gif
1811 ms
mainvisualbg.png
3119 ms
li_bullet.gif
1668 ms
2.jpg
6364 ms
linediv3_03bg.gif
1615 ms
linediv3_04bg.gif
1788 ms
facebook_tit_ov.png
1704 ms
footerwrap_bg.gif
1705 ms
footerbg.gif
3008 ms
bullets.png
1684 ms
epik.go.kr accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Links do not have a discernible name
epik.go.kr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
epik.go.kr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
N/A
US
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Epik.go.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), while the claimed language is . Our system also found out that Epik.go.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.
epik.go.kr
Open Graph description is not detected on the main page of Epik Go. 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: