9.2 sec in total
1.1 sec
7.8 sec
244 ms
Visit traveltimes.co.kr now to see the best up-to-date Traveltimes content for South Korea and also check out these interesting facts you probably never knew about traveltimes.co.kr
인터넷 신문,여행신문,국내여행정보,해외여행정보,여행전문지,주간지,여행통계,여행뉴스,관광정보,여행최신뉴스,관광청소식,항공사소식
Visit traveltimes.co.krWe analyzed Traveltimes.co.kr page load time and found that the first response time was 1.1 sec and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
traveltimes.co.kr performance score
name
value
score
weighting
Value9.9 s
0/100
10%
Value13.3 s
0/100
25%
Value24.3 s
0/100
10%
Value12,400 ms
0/100
30%
Value0.115
86/100
15%
Value37.1 s
0/100
10%
1143 ms
2490 ms
467 ms
934 ms
1165 ms
Our browser made a total of 139 requests to load all elements on the main page. We found that 72% of them (100 requests) were addressed to the original Traveltimes.co.kr, 4% (6 requests) were made to Pagead2.googlesyndication.com and 4% (6 requests) were made to Travie.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Travie.com.
Page size can be reduced by 341.4 kB (42%)
810.9 kB
469.4 kB
In fact, the total size of Traveltimes.co.kr main page is 810.9 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. 50% of websites need less resources to load. Javascripts take 420.3 kB which makes up the majority of the site volume.
Potential reduce by 41.1 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.5 kB, which is 16% 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 41.1 kB or 78% of the original size.
Potential reduce by 21.8 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. Traveltimes images are well optimized though.
Potential reduce by 243.0 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 243.0 kB or 58% of the original size.
Potential reduce by 35.6 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. Traveltimes.co.kr needs all CSS files to be minified and compressed as it can save up to 35.6 kB or 77% of the original size.
Number of requests can be reduced by 76 (56%)
135
59
The browser has sent 135 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Traveltimes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
traveltimes.co.kr
1143 ms
www.traveltimes.co.kr
2490 ms
style.css
467 ms
common.js
934 ms
common2.js
1165 ms
jquery-1.7.1.min.js
1667 ms
default.css
957 ms
jquery-1.8.3.min.js
1846 ms
jquery.menu.js
1152 ms
wrest.js
1166 ms
select.css
972 ms
jquery-latest.js
8 ms
select.js
1160 ms
topmenu.js
1171 ms
adsbygoogle.js
12 ms
default2.css
936 ms
layout.css
970 ms
common.css
1153 ms
contents.css
1163 ms
main.css
1168 ms
popupzone.js
997 ms
cert_img.mrk
810 ms
wcslog.js
8 ms
PopupCheck.js
961 ms
PopupMove.js
960 ms
thumb-982933293_1454646219.47_130x90.jpg
2601 ms
224 ms
thumb-982933293_1454638573.12_130x90.jpg
2841 ms
thumb-982933293_1454637389.53_130x90.jpg
2631 ms
thumb-982933293_1454568198.92_130x90.jpg
2636 ms
thumb-982933293_1454563234.6_130x90.jpg
2882 ms
thumb-982933293_1454474587.91_130x90.jpg
2677 ms
gnb_travie.gif
244 ms
logo.gif
245 ms
btn_search.gif
243 ms
travie_ad175.jpg
245 ms
menu1.gif
244 ms
menu2.gif
246 ms
menu3.gif
464 ms
menu4.gif
466 ms
menu5.gif
468 ms
14567224951.jpg
468 ms
14567229551.jpg
477 ms
headpt_tit.gif
481 ms
14567236476.jpg
723 ms
tktt_ranky1.jpg
723 ms
w292_2.gif
722 ms
banner3.gif
733 ms
thumb-982933293_1456108313.27_113x73.jpg
733 ms
thumb-982933293_1456117643.12_113x73.jpg
734 ms
thumb-982933293_1456118782.94_113x73.jpg
934 ms
thumb-982933293_1456118106.36_113x73.jpg
931 ms
tit_tour.gif
935 ms
tit_people.gif
938 ms
thumb-982933293_1456719279.52_90x75.jpg
953 ms
thumb-982933293_1456719333.17_90x75.jpg
958 ms
thumb-982933293_1456107834.04_90x75.jpg
1161 ms
tit_local.gif
1163 ms
tit_photo.gif
1165 ms
145672338912.jpg
1166 ms
145672338913.jpg
1190 ms
banner_land2016.jpg
1196 ms
tit_survey.gif
1390 ms
btn_sur.gif
1394 ms
14567235361.jpg
1395 ms
14567235871.jpg
1395 ms
banner_wednesdayjourna.jpg
1425 ms
tit_ad.jpg
1420 ms
ca-pub-0945582647615999.js
62 ms
zrt_lookup.html
66 ms
show_ads_impl.js
96 ms
logo1_certification.png
407 ms
analytics.js
76 ms
m
511 ms
ads
299 ms
osd.js
12 ms
collect
22 ms
249 ms
ads
284 ms
collect
61 ms
b_logo.gif
1384 ms
tktt_kodb2.gif
1388 ms
b_copyright.gif
1390 ms
b_customercenter.gif
1394 ms
familysite.gif
1427 ms
ads
289 ms
01_01.jpg
1423 ms
ads
266 ms
01_02.jpg
1395 ms
01_03.jpg
1398 ms
01_04.jpg
1400 ms
01_05.jpg
1403 ms
02_01.jpg
1433 ms
land2016_pop.jpg
1675 ms
m_js_controller.js
50 ms
abg.js
67 ms
googlelogo_color_112x36dp.png
112 ms
13302436116232819459
35 ms
16702424525879917821
24 ms
favicon
98 ms
favicon
158 ms
nessie_icon_tiamat_white.png
43 ms
s
51 ms
x_button_blue2.png
34 ms
redir.html
130 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
32 ms
02_02.jpg
1366 ms
popup_close.jpg
1373 ms
03_01.jpg
1367 ms
03_02.jpg
1370 ms
03_03.jpg
1414 ms
03_04.jpg
1583 ms
iframe.html
33 ms
bg_gnb.gif
1397 ms
gnb_bar.gif
1396 ms
gnb_btnbg1.gif
1400 ms
ico_letter.gif
1446 ms
gnb_btnbg2.gif
1442 ms
btn_arrow_down.gif
1592 ms
lnb_bar.gif
1397 ms
bg_circulation1.gif
1399 ms
bg_circulation2.gif
1404 ms
ico_arrow_red2.gif
1457 ms
dot1.gif
1443 ms
dotline1.gif
1582 ms
ico_headarrow.gif
1398 ms
2colorline.gif
1399 ms
dotline2.gif
1404 ms
bg_tour.gif
1463 ms
bg_people.gif
1442 ms
ico_circle_gray.gif
1572 ms
ico_circle_gray2.gif
1400 ms
bg_weeklyevent.gif
1401 ms
ico_arrow_red.gif
1405 ms
ico_arrow_more.gif
1468 ms
btn_suron.gif
1445 ms
btn_adver_off.gif
1564 ms
activeview
14 ms
b_bar.gif
1401 ms
traveltimes.co.kr accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
traveltimes.co.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
traveltimes.co.kr SEO score
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
KO
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Traveltimes.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 Traveltimes.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.
traveltimes.co.kr
Open Graph description is not detected on the main page of Traveltimes. 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: