44.2 sec in total
15.5 sec
28.4 sec
235 ms
Visit inside.olleh.com now to see the best up-to-date Inside Olleh content for South Korea and also check out these interesting facts you probably never knew about inside.olleh.com
글로벌 No.1 KT입니다. KT 상품서비스를 이용하시는 고객을 위한 혜택과 서비스를 제공, 다양한 이벤트도 참여해보세요.
Visit inside.olleh.comWe analyzed Inside.olleh.com page load time and found that the first response time was 15.5 sec and then it took 28.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
inside.olleh.com performance score
name
value
score
weighting
Value17.2 s
0/100
10%
Value20.0 s
0/100
25%
Value21.1 s
0/100
10%
Value120 ms
97/100
30%
Value0
100/100
15%
Value20.7 s
2/100
10%
15531 ms
283 ms
562 ms
483 ms
5410 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 14% of them (10 requests) were addressed to the original Inside.olleh.com, 80% (56 requests) were made to Cfm.olleh.com and 3% (2 requests) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (15.5 sec) belongs to the original domain Inside.olleh.com.
Page size can be reduced by 289.4 kB (77%)
375.6 kB
86.2 kB
In fact, the total size of Inside.olleh.com main page is 375.6 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. Javascripts take 163.8 kB which makes up the majority of the site volume.
Potential reduce by 80.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 80.6 kB or 86% of the original size.
Potential reduce by 43.7 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, Inside Olleh needs image optimization as it can save up to 43.7 kB or 77% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 112.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 112.5 kB or 69% of the original size.
Potential reduce by 52.5 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. Inside.olleh.com needs all CSS files to be minified and compressed as it can save up to 52.5 kB or 86% of the original size.
Number of requests can be reduced by 18 (27%)
67
49
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Inside Olleh. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
inside.olleh.com
15531 ms
index.asp
283 ms
noticeList.asp
562 ms
olleh_notice.css
483 ms
ollehGlobal.asp
5410 ms
jquery-1.6.4.min.js
9471 ms
olleh_common.css
1892 ms
autocomNsummary.css
1436 ms
jquery-1.11.3.min.js
2487 ms
autocomNsummary.js
2283 ms
olleh_function.js
1246 ms
olleh_common.asp
2696 ms
s_code.js
2281 ms
check.js
1669 ms
satelliteLib-ec634da1892b150971a6a62838a5b388a597cb51.js
142 ms
olleh_popup.css
294 ms
olleh_old.css
288 ms
mbox-contents-f22f8ff04582fd949eb125f4f0442703f6c58028.js
33 ms
target.js
95 ms
cfm_y15_olleh_gnb_bg.png
251 ms
skip_ico.png
304 ms
new15logo.png
312 ms
cfm_olleh_y15_util_line.png
312 ms
cfm_olleh_util_list1.png
314 ms
cfm_olleh_util_list2.png
308 ms
cfm_olleh_util_list3.png
456 ms
cfm_olleh_y15_util_ar_bar.png
481 ms
H0000.png
488 ms
cfm_bars.png
489 ms
N0000_s.png
2708 ms
B0000_s.png
489 ms
WF000_s.png
673 ms
F0000_s.png
687 ms
E0000_s.png
688 ms
cfm_olleh_search_bg.png
691 ms
cfm_btn_olleh_search.png
687 ms
cfm_button_total_menu.png
896 ms
cfm_total_top_bg.png
903 ms
24_01.png
903 ms
23_01.png
903 ms
12_01.png
935 ms
tit_notice_1.gif
261 ms
cfm_olleh_icon_home.png
1026 ms
btn_success.png
627 ms
btn_search.png
325 ms
line_top.gif
429 ms
page_next.gif
528 ms
s_code.js
679 ms
footer_logo_d.png
803 ms
113_01.png
804 ms
112_01.png
803 ms
99_01.png
843 ms
98_01.png
1006 ms
97_01.png
1004 ms
96_01.png
1007 ms
95_01.png
1019 ms
115_01.png
1055 ms
164_01.png
1215 ms
172_01.png
1215 ms
171_01.png
1217 ms
170_01.png
1251 ms
cfm_olleh_best_title.png
1281 ms
165_01.png
1442 ms
166_01.png
1439 ms
167_01.png
1442 ms
cfm_olleh_quick_button_top1.png
1478 ms
cfm_olleh_quick_small_buttonOff.png
1370 ms
cfm_olleh_quick_bg2.png
1471 ms
titleDotBg.png
1459 ms
s85085614633280
46 ms
inside.olleh.com accessibility score
inside.olleh.com 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
General
Impact
Issue
Detected JavaScript libraries
inside.olleh.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
KO
KO
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inside.olleh.com 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 Inside.olleh.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.
inside.olleh.com
Open Graph description is not detected on the main page of Inside Olleh. 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: