12.7 sec in total
596 ms
11.8 sec
345 ms
Click here to check amazing Media JTBC content for South Korea. Otherwise, check out these important facts you probably never knew about media.jtbc.co.kr
Visit media.jtbc.co.krWe analyzed Media.jtbc.co.kr page load time and found that the first response time was 596 ms and then it took 12.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
media.jtbc.co.kr performance score
596 ms
612 ms
1221 ms
1015 ms
838 ms
Our browser made a total of 160 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Media.jtbc.co.kr, 55% (88 requests) were made to Fs.jtbc.joins.com and 29% (46 requests) were made to Images.jtbc.joins.com. The less responsive or slowest element that took the longest time to load (8.2 sec) relates to the external source Afs.opap.co.kr.
Page size can be reduced by 1.2 MB (31%)
3.9 MB
2.7 MB
In fact, the total size of Media.jtbc.co.kr main page is 3.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. 70% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 89.8 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 89.8 kB or 80% of the original size.
Potential reduce by 165.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. Media JTBC images are well optimized though.
Potential reduce by 728.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 728.8 kB or 81% of the original size.
Potential reduce by 214.2 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. Media.jtbc.co.kr needs all CSS files to be minified and compressed as it can save up to 214.2 kB or 86% of the original size.
Number of requests can be reduced by 42 (27%)
156
114
The browser has sent 156 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Media JTBC. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and as a result speed up the page load time.
media.jtbc.co.kr
596 ms
media.jtbc.joins.com
612 ms
jtbc.joins.com
1221 ms
common_v5.css
1015 ms
index_v4.css
838 ms
jquery-1.6.2.min.js
984 ms
common.js
786 ms
toplogomenu.js
990 ms
right.js
991 ms
Schedule.js
595 ms
makecrmpcookie.js
602 ms
jtbc_tv_showcase_banner.js
212 ms
prog_Y.js
198 ms
prog_E.js
206 ms
prog_today_section.js
207 ms
analytics.js
7 ms
u_skip_access.gif
616 ms
k_top_left.png
617 ms
k_top_right.png
620 ms
k_top.jpg
1243 ms
b_bbanner01.png
634 ms
b_bbanner02.png
636 ms
b_bbanner03.png
812 ms
b_bbanner04.png
812 ms
b_bbanner05.png
814 ms
b_bbanner06.png
836 ms
b_bbanner07.png
839 ms
b_bbanner08.png
1009 ms
201601111803318341.jpg
600 ms
201510261358023497.jpg
790 ms
201602171656101400.jpg
797 ms
collect
22 ms
k_gnb.png
992 ms
u_jtbc.png
987 ms
t_jtbc_index.gif
1012 ms
k_gnb_service.png
1016 ms
k_gnb_service_onair.png
1194 ms
u_gnb_service.png
1193 ms
u_gnb_service_v6.png
1194 ms
u_gnb_service_v5.png
1214 ms
k_search_bg.png
1219 ms
k_body_left.png
1379 ms
k_body_right.png
1381 ms
k_doc_v2.png
2769 ms
b_prev_v3.png
1415 ms
b_next_v3.png
1416 ms
collect
66 ms
k_onair.png
1409 ms
k_index.png
1564 ms
k_recom.png
1566 ms
k_vod_v2.png
1606 ms
k_right_v3.png
1605 ms
hc.aspx
600 ms
follow_button.html
118 ms
jtbc.tweet.js
340 ms
TvFacebook_JTBClove.js
349 ms
BannerRight.js
343 ms
jtbc_common_right_notice_list.js
537 ms
u_sns.png
1600 ms
u_sns_icon.gif
1750 ms
t_notice.png
1752 ms
tv_main_showcase.js
538 ms
k_bottom_banner.png
1794 ms
jtbc_index_btm_program_drama.js
540 ms
jtbc_index_btm_program_enter.js
733 ms
jtbc_index_btm_program_culture.js
734 ms
jtbc_index_btm_program_sisa.js
740 ms
jtbc_index_btm_program_etc.js
742 ms
jtbc_prog_dr_list.js
923 ms
jtbc_prog_en_list.js
922 ms
jtbc_prog_cu_list.js
929 ms
jtbc_prog_nw2_list.js
934 ms
jtbc_prog_si_list.js
934 ms
t_program.png
1782 ms
683 ms
schedule_day3.js
927 ms
jtbc_tv_photo_news.js
1107 ms
jtbc_tv_home_news.js
1107 ms
prog_CM_VOD9.js
1117 ms
prog_CM_PREVIEW9.js
1316 ms
prog_week_recomm.js
1128 ms
MainPopup.js
1128 ms
like.php
126 ms
jot
96 ms
vpc6VNjRPXV.js
137 ms
LVx-xkvaJ0b.png
152 ms
vpc6VNjRPXV.js
53 ms
JTBCLoveTimeline10.js
802 ms
20160226_104652_2824.jpg
983 ms
20160212_191858_7264.jpg
982 ms
2e-9P5Ad_normal.jpeg
68 ms
12672774_831091520335255_2106420959_n.jpg
86 ms
12496803_831106717000402_55462886_n.jpg
102 ms
12801131_831633486947725_8634989239957282419_n.png
118 ms
12594517_831192950325112_412927855_n.jpg
135 ms
12672219_831086900335717_674032712_n.jpg
137 ms
201601201322565834.jpg
786 ms
t_program_v3.png
1241 ms
k_program_liberal_tab.png
1387 ms
k_footer.png
1387 ms
k_footer_logo.png
1417 ms
v_qrcode.png
1417 ms
hana_280x230_160119.jpg
8236 ms
201510191336431252.jpg
600 ms
201512111715430207.jpg
602 ms
201409221555594019.jpg
767 ms
r_arrow.png
1246 ms
u_common.png
1387 ms
20160219_125408_5322.jpg.tn91.jpg
572 ms
20160219_132500_4513.jpg.tn91.jpg
583 ms
20160219_142735_7832.jpg.tn91.jpg
588 ms
20160225_163905_2342.jpg.tn91.jpg
590 ms
20160225_163821_3673.jpg.tn91.jpg
593 ms
20141217_105632_2654(1).jpg.tn91.jpg
765 ms
20160225_164532_5067.jpg.tn91.jpg
771 ms
20160225_164426_2219.jpg.tn91.jpg
784 ms
20160219_132414_0566.jpg.tn91.jpg
789 ms
i_live.png
1198 ms
201603011821366832.jpg
1205 ms
201603011553212783.jpg
1215 ms
201603011554047870.jpg
1375 ms
201602292155261453.jpg
1378 ms
6Amn89yr_normal.jpg
28 ms
20150519_213344_2571.jpg.tn202.jpg
796 ms
20160229_210113_4944.jpg.tn202.jpg
802 ms
20160229_233708_8070.jpg.tn202.jpg
998 ms
20160225_224059_3956.jpg.tn202.jpg
1006 ms
20140405_011342_8240.jpg.tn202.jpg
1201 ms
20150428_231346_9789.jpg.tn202.jpg
1208 ms
20160229_205828_6949.jpg.tn202.jpg
1390 ms
20160223_223318_7020.jpg.tn202.jpg
1401 ms
20160229_234057_1768.jpg.tn202.jpg
1402 ms
k_movie_v3.png
1053 ms
l_dot3.gif
1054 ms
20150918_094154_2143.jpg
1393 ms
20160205_133253_4056(1).jpg
1539 ms
20150918_091713_9176.jpg
1545 ms
20160108_164142_9225(1).jpg
1576 ms
20151019_133312_5564.jpg
1585 ms
20160216_091440_7265.jpg
1586 ms
20160216_092103_0226.jpg
1594 ms
20151217_170925_6346.jpg
1580 ms
20151211_132639_3938.jpg
1586 ms
20160113_165445_4798.jpg
1610 ms
20160120_102622_1728.jpg
1611 ms
20160205_105803_8325.jpg
1610 ms
20151217_171353_7570.jpg
1616 ms
20160120_112545_5605(1).jpg
1586 ms
20160229_165728_1878(1).jpg
1587 ms
20160216_091452_8322.jpg
1612 ms
20151019_134538_9228.jpg
1614 ms
20160222_171832_7151.jpg.tn202.jpg
1614 ms
20160222_182248_8146.jpg.tn202.jpg
1620 ms
20160229_131131_4095.jpg.tn202.jpg
1585 ms
20160229_131214_1382.jpg.tn202.jpg
1585 ms
20160217_133111_1494.jpg.tn202.jpg
1612 ms
20160217_132742_4513.jpg.tn202.jpg
1617 ms
20160301_164513_4794.jpg.tn202.jpg
1516 ms
20160225_095307_4359.jpg.tn202.jpg
1418 ms
20160226_195802_6090.jpg.tn202.jpg
1359 ms
media.jtbc.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 Media.jtbc.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 Media.jtbc.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.
media.jtbc.co.kr
Open Graph description is not detected on the main page of Media JTBC. 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: