9.5 sec in total
806 ms
8.5 sec
139 ms
Welcome to etribe.co.kr homepage info - get ready to check ETRIBE best content for South Korea right away, or after learning these important things about etribe.co.kr
새로운 경험을 창조하는 디지털 통합미디어 에이전시 이트라이브에 오신걸 환영합니다.
Visit etribe.co.krWe analyzed Etribe.co.kr page load time and found that the first response time was 806 ms and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
etribe.co.kr performance score
806 ms
396 ms
801 ms
1238 ms
407 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 86% of them (70 requests) were addressed to the original Etribe.co.kr, 2% (2 requests) were made to Google-analytics.com and 2% (2 requests) were made to Api-read.facebook.com. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Etribe.co.kr.
Page size can be reduced by 1.0 MB (82%)
1.3 MB
228.7 kB
In fact, the total size of Etribe.co.kr main page is 1.3 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. 25% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 25.4 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 25.4 kB or 75% of the original size.
Potential reduce by 867.2 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, ETRIBE needs image optimization as it can save up to 867.2 kB or 85% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 89.3 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 89.3 kB or 62% of the original size.
Potential reduce by 49.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. Etribe.co.kr needs all CSS files to be minified and compressed as it can save up to 49.6 kB or 83% of the original size.
Number of requests can be reduced by 32 (40%)
80
48
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ETRIBE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
main.jsp
806 ms
etribe_2011.css
396 ms
etribe_2011_web.css
801 ms
jquery-1.5.1.min.js
1238 ms
rr2jquery.js
407 ms
common.js
804 ms
sns.js
992 ms
all.js
160 ms
jquery.easing.1.3.js
1002 ms
jquery.mousewheel.min.js
801 ms
facebook.js
1004 ms
ajax_makingObject.js
1011 ms
ajax_main_list.js
1011 ms
bg_pjtbox_web02.gif
201 ms
h1_logo.gif
199 ms
menu_01.jpg
396 ms
menu_01_01.jpg
403 ms
menu_01_02.jpg
403 ms
menu_01_03.jpg
405 ms
menu_01_05.jpg
586 ms
menu_01_04.jpg
589 ms
menu_02.jpg
796 ms
menu_02_01.jpg
793 ms
menu_02_02.jpg
800 ms
menu_02_03.jpg
802 ms
menu_03.jpg
981 ms
menu_03_01.jpg
983 ms
menu_03_02.jpg
1193 ms
menu_03_03.jpg
1209 ms
menu_03_04.jpg
1208 ms
menu_04.jpg
1212 ms
menu_05.jpg
1379 ms
A1408437682438.jpg
1793 ms
A1402996585352.jpg
1582 ms
A1402464333538.jpg
1609 ms
A1383283994715.jpg
1619 ms
A1383284586052.jpg
1818 ms
spinner.gif
1770 ms
animatedHand.png
1984 ms
C1408437682440.jpg
4262 ms
btn_view_detail.gif
2013 ms
btn_visit_website.gif
2163 ms
h3_friends_activity.gif
2190 ms
blog_banner.gif
2407 ms
h3_news_notice.gif
2383 ms
btn_view_all.gif
2423 ms
h3_etribe_labs.gif
2566 ms
img_movie_test.gif
2778 ms
ga.js
28 ms
h3_onproject.gif
2781 ms
restserver.php
177 ms
restserver.php
239 ms
__utm.gif
46 ms
face.jsp
2645 ms
ajax_main_list.jsp
2824 ms
h4_web.gif
2598 ms
A1407746541110.gif
2795 ms
A1407746524305.gif
2790 ms
A1402465798130.gif
2809 ms
A1402465785154.gif
2797 ms
A1402465718820.gif
2830 ms
A1402465680143.gif
2801 ms
h4_mobile.gif
2796 ms
A1407746511289.gif
2825 ms
A1407746496390.gif
2973 ms
A1402465771881.gif
2831 ms
A1402465753571.gif
3009 ms
A1402465732784.gif
2798 ms
bg_pjtbox_web03.gif
2812 ms
img_go_recruit2.gif
2959 ms
text_bg.png
2995 ms
txt_copyright.gif
3004 ms
B1408437682439.jpg
3205 ms
137 ms
xd_arbiter.php
147 ms
xd_arbiter.php
267 ms
like.php
130 ms
rU2ubZ6l1Q5.js
331 ms
LVx-xkvaJ0b.png
361 ms
etribe_2011_smartphone.css
597 ms
etribe_2011_tablet.css
797 ms
etribe.co.kr SEO score
KO
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Etribe.co.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Etribe.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.
etribe.co.kr
Open Graph description is not detected on the main page of ETRIBE. 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: