8.1 sec in total
1.2 sec
6.8 sec
119 ms
Click here to check amazing O Tree content. Otherwise, check out these important facts you probably never knew about o-tree.com
Visit o-tree.comWe analyzed O-tree.com page load time and found that the first response time was 1.2 sec and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
o-tree.com performance score
1165 ms
388 ms
685 ms
973 ms
510 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 77% of them (48 requests) were addressed to the original O-tree.com, 11% (7 requests) were made to Ad.ilikesponsorad.co.kr and 3% (2 requests) were made to Adtg.widerplanet.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain O-tree.com.
Page size can be reduced by 143.3 kB (73%)
196.4 kB
53.0 kB
In fact, the total size of O-tree.com main page is 196.4 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. 15% of websites need less resources to load. Javascripts take 127.0 kB which makes up the majority of the site volume.
Potential reduce by 48.3 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 48.3 kB or 84% of the original size.
Potential reduce by 88.9 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 88.9 kB or 70% of the original size.
Potential reduce by 6.1 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. O-tree.com needs all CSS files to be minified and compressed as it can save up to 6.1 kB or 53% of the original size.
Number of requests can be reduced by 39 (65%)
60
21
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of O Tree. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
o-tree.com
1165 ms
style.css
388 ms
common.js
685 ms
jquery-1.4.2.min.js
973 ms
ajax.js
510 ms
ad.js
688 ms
sideview.js
228 ms
wrest.js
384 ms
2039565887_d9a536c2_topbuilder.gif
229 ms
bg_gnb_middle.gif
237 ms
bg_gnb_left.gif
256 ms
bg_gnb_right.gif
231 ms
btn_prev.gif
196 ms
btn_next.gif
389 ms
btn_more.gif
484 ms
btn_prev.gif
455 ms
btn_next.gif
459 ms
btn_more.gif
469 ms
btn_prev.gif
512 ms
btn_next.gif
580 ms
btn_more.gif
681 ms
no_image.gif
688 ms
btn_more.gif
704 ms
icon_hot.gif
684 ms
btn_more.gif
768 ms
no_image.gif
772 ms
search_title.gif
911 ms
search_btn.gif
883 ms
btn_more.gif
917 ms
no_image.gif
938 ms
2039565887_85fdeabc_topbanner200_20100228.gif
1022 ms
copyright.gif
966 ms
ad_live.html
714 ms
bu_listtext.gif
1070 ms
bu_listtext.gif
1122 ms
bu_listtext.gif
1129 ms
bg_tab_on.gif
1151 ms
bg_tab_off.gif
1134 ms
bu_listtext.gif
1246 ms
1.gif
1248 ms
arrow.gif
1328 ms
2.gif
1339 ms
3.gif
1313 ms
4.gif
1373 ms
5.gif
1498 ms
6.gif
1289 ms
7.gif
1316 ms
bu_listtext.gif
1361 ms
bu_listtext.gif
1371 ms
hbg0.gif
1389 ms
ad.css
197 ms
afr.php
95 ms
ad_asyn_ct_passback.html
199 ms
lg.php
21 ms
ad_live.html
204 ms
wfr.php
758 ms
ad_live.html
205 ms
wfr.php
507 ms
ad_live.html
205 ms
_n2s_nblg_adinfo.php
691 ms
ad_live.html
210 ms
a09b68ada5e8b2060f380a53c02cf3d8
1111 ms
o-tree.com SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise O-tree.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that O-tree.com 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.
o-tree.com
Open Graph description is not detected on the main page of O Tree. 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: