Tools & Wizards About Us
tikle.co.kr screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

tikle.co.kr

Page Load Speed

11.4 sec in total

First Response

944 ms

Resources Loaded

10.2 sec

Page Rendered

240 ms

tikle.co.kr screenshot

About Website

Click here to check amazing Tikle content. Otherwise, check out these important facts you probably never knew about tikle.co.kr

도메인, 도메인등록, 퀵돔등록, 도메인연장, 도메인이전, 무료 파킹, 무료포워딩 제공, 국내 최저가 도메인 서비스 제공, 웹호스팅, 서버호스팅, 홈페이지제작, 쇼핑몰, 서버, IDC

Visit tikle.co.kr

Key Findings

We analyzed Tikle.co.kr page load time and found that the first response time was 944 ms and then it took 10.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

tikle.co.kr performance score

0

Network Requests Diagram

tikle.co.kr

944 ms

www.tikle.co.kr

2248 ms

dd-3.5.2.css

417 ms

aero.css

417 ms

dd_skin2.css

445 ms

Our browser made a total of 153 requests to load all elements on the main page. We found that 89% of them (136 requests) were addressed to the original Tikle.co.kr, 3% (5 requests) were made to Maps.googleapis.com and 2% (3 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Tikle.co.kr.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (44%)

Content Size

2.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tikle.co.kr main page is 2.5 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. 50% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 373.6 kB

  • Original 405.6 kB
  • After minification 316.2 kB
  • After compression 32.0 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 89.4 kB, which is 22% 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 373.6 kB or 92% of the original size.

Image Optimization

-7%

Potential reduce by 88.1 kB

  • Original 1.2 MB
  • After minification 1.1 MB

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. Tikle images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 501.6 kB

  • Original 740.6 kB
  • After minification 683.7 kB
  • After compression 239.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 501.6 kB or 68% of the original size.

CSS Optimization

-82%

Potential reduce by 149.0 kB

  • Original 180.8 kB
  • After minification 147.0 kB
  • After compression 31.8 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. Tikle.co.kr needs all CSS files to be minified and compressed as it can save up to 149.0 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (26%)

Requests Now

151

After Optimization

111

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 151 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tikle. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

tikle.co.kr

tikle.co.kr

944 ms

www.tikle.co.kr

www.tikle.co.kr

2248 ms

dd-3.5.2.css

dd-3.5.2.css

417 ms

aero.css

aero.css

417 ms

dd_skin2.css

dd_skin2.css

445 ms

dd_custume.css

dd_custume.css

446 ms

datepicker.css

datepicker.css

679 ms

datepicker_custom.css

datepicker_custom.css

611 ms

font-awesome.css

font-awesome.css

811 ms

font-awesome.min.css

font-awesome.min.css

886 ms

common.css

common.css

1110 ms

header.css

header.css

1000 ms

popup.css

popup.css

1128 ms

main.css

main.css

1021 ms

sidebar.css

sidebar.css

1107 ms

jquery-2.1.0.min.js

jquery-2.1.0.min.js

78 ms

jquery-ui.min.js

jquery-ui.min.js

155 ms

json2.min.js

json2.min.js

1193 ms

jquery.cookie-1.4.0.min.js

jquery.cookie-1.4.0.min.js

1219 ms

jquery.blockUI-2.66.min.js

jquery.blockUI-2.66.min.js

1328 ms

jquery.dd-3.5.2.min.js

jquery.dd-3.5.2.min.js

1344 ms

jquery.icheck-0.9.1.min.js

jquery.icheck-0.9.1.min.js

1353 ms

googlelog.js

googlelog.js

1387 ms

js

js

36 ms

common_pattern.js

common_pattern.js

1415 ms

common_msg.js

common_msg.js

1549 ms

common_func.js

common_func.js

1788 ms

head_common.js

head_common.js

1544 ms

header_content.js

header_content.js

233 ms

banner_header.js

banner_header.js

234 ms

main_common.js

main_common.js

269 ms

main.js

main.js

390 ms

sidebar.js

sidebar.js

422 ms

footer_content.js

footer_content.js

640 ms

popup.js

popup.js

428 ms

footer_common.js

footer_common.js

640 ms

api_fb.js

api_fb.js

641 ms

analytics.js

analytics.js

15 ms

collect

collect

13 ms

logo_c_s.png

logo_c_s.png

372 ms

arrow_gnb.gif

arrow_gnb.gif

375 ms

ico_start.gif

ico_start.gif

372 ms

ico_arrival.gif

ico_arrival.gif

371 ms

btn_search.gif

btn_search.gif

373 ms

photo

photo

375 ms

bg_arrow.png

bg_arrow.png

405 ms

photo

photo

478 ms

photo

photo

529 ms

photo

photo

588 ms

photo

photo

555 ms

photo

photo

588 ms

photo

photo

653 ms

photo

photo

732 ms

photo

photo

807 ms

photo

photo

848 ms

photo

photo

866 ms

photo

photo

892 ms

photo

photo

896 ms

photo

photo

973 ms

photo

photo

1103 ms

photo

photo

1127 ms

photo

photo

1128 ms

photo

photo

1194 ms

photo

photo

1158 ms

photo

photo

1228 ms

photo

photo

1430 ms

photo

photo

1466 ms

photo

photo

1417 ms

photo

photo

1434 ms

photo

photo

1485 ms

photo

photo

1480 ms

photo

photo

1604 ms

photo

photo

1671 ms

photo

photo

1569 ms

procuserpointInfo

procuserpointInfo

1814 ms

sdk.js

sdk.js

268 ms

getmynotifyviewcnt

getmynotifyviewcnt

1930 ms

photo

photo

1438 ms

photo

photo

1411 ms

photo

photo

1599 ms

photo

photo

1612 ms

NanumGothic.woff

NanumGothic.woff

4478 ms

NanumGothicBold.woff

NanumGothicBold.woff

4244 ms

photo

photo

1750 ms

142 ms

xd_arbiter.php

xd_arbiter.php

225 ms

xd_arbiter.php

xd_arbiter.php

428 ms

photo

photo

1700 ms

photo

photo

1751 ms

photo

photo

2146 ms

photo

photo

2875 ms

photo

photo

2087 ms

photo

photo

2053 ms

photo

photo

2203 ms

photo

photo

2192 ms

photo

photo

2200 ms

photo

photo

2378 ms

photo

photo

2429 ms

photo

photo

2377 ms

photo

photo

2416 ms

photo

photo

2483 ms

photo

photo

2517 ms

photo

photo

2564 ms

photo

photo

2583 ms

photo

photo

2653 ms

photo

photo

2507 ms

photo

photo

2556 ms

photo

photo

2597 ms

photo

photo

2713 ms

photo

photo

2763 ms

photo

photo

2761 ms

photo

photo

2583 ms

photo

photo

2723 ms

photo

photo

2744 ms

photo

photo

2707 ms

photo

photo

2715 ms

photo

photo

2883 ms

photo

photo

2867 ms

photo

photo

2840 ms

photo

photo

2629 ms

photo

photo

2701 ms

photo

photo

2703 ms

photo

photo

2742 ms

photo

photo

2319 ms

photo

photo

2316 ms

photo

photo

2319 ms

photo

photo

2164 ms

photo

photo

2184 ms

bg_cntf_alert.png

bg_cntf_alert.png

2177 ms

bg_cntl_alert.png

bg_cntl_alert.png

2005 ms

logo.png

logo.png

1928 ms

mark_share_white.png

mark_share_white.png

1980 ms

icon.png

icon.png

1912 ms

btn_confirm.gif

btn_confirm.gif

1927 ms

ico_map_tikle.gif

ico_map_tikle.gif

1827 ms

btn_small_done.gif

btn_small_done.gif

1802 ms

btn_msg_send.gif

btn_msg_send.gif

1775 ms

btn_num_receive.gif

btn_num_receive.gif

1781 ms

btn_num_confirm.gif

btn_num_confirm.gif

1694 ms

btn_save.gif

btn_save.gif

1708 ms

ico_guess.png

ico_guess.png

1677 ms

img_txt_levelup.gif

img_txt_levelup.gif

1612 ms

dd_arrow.gif

dd_arrow.gif

1541 ms

bg_dot.png

bg_dot.png

1542 ms

aero.png

aero.png

1531 ms

common.js

common.js

6 ms

util.js

util.js

28 ms

stats.js

stats.js

27 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

340 ms

xd_arbiter.php

xd_arbiter.php

139 ms

like.php

like.php

95 ms

wy1X4hBW7e7.js

wy1X4hBW7e7.js

484 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

539 ms

SEO Factors

tikle.co.kr SEO score

0

Language and Encoding

  • Language Detected

    KO

  • Language Claimed

    KO

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tikle.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 Tikle.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.

Social Sharing Optimization

tikle.co.kr

Open Graph data is detected on the main page of Tikle. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: