4.3 sec in total
469 ms
3.5 sec
271 ms
Click here to check amazing Treelz content. Otherwise, check out these important facts you probably never knew about treelz.com
Treelz - Leave your mark here! Place your photo's and messages on the world map(Google Maps). You can share these treelz with your friends, colleagues, family or anyone. This way you can log your stor...
Visit treelz.comWe analyzed Treelz.com page load time and found that the first response time was 469 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
treelz.com performance score
name
value
score
weighting
Value1.7 s
92/100
10%
Value6.7 s
7/100
25%
Value4.1 s
79/100
10%
Value510 ms
57/100
30%
Value0.005
100/100
15%
Value5.4 s
72/100
10%
469 ms
102 ms
34 ms
617 ms
272 ms
Our browser made a total of 132 requests to load all elements on the main page. We found that 65% of them (86 requests) were addressed to the original Treelz.com, 8% (11 requests) were made to Maps.google.com and 8% (10 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (836 ms) belongs to the original domain Treelz.com.
Page size can be reduced by 543.6 kB (40%)
1.3 MB
800.9 kB
In fact, the total size of Treelz.com 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. 55% of websites need less resources to load. Images take 609.1 kB which makes up the majority of the site volume.
Potential reduce by 82.2 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 82.2 kB or 87% of the original size.
Potential reduce by 19.0 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. Treelz images are well optimized though.
Potential reduce by 348.4 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 348.4 kB or 65% of the original size.
Potential reduce by 94.0 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. Treelz.com needs all CSS files to be minified and compressed as it can save up to 94.0 kB or 88% of the original size.
Number of requests can be reduced by 57 (54%)
105
48
The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Treelz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.
www.treelz.com
469 ms
EN.js
102 ms
maps
34 ms
combine_2010_10_26.js
617 ms
style_2010_10_26.css
272 ms
yui_menu_2009_01_09.css
196 ms
ga.js
28 ms
icon_footer_help.png
103 ms
icon_footer_info.png
107 ms
icon_footer_search_field.png
100 ms
bg_zoom_footer.png
90 ms
icon_footer_zoom_out.png
180 ms
icon_footer_zoom_between.png
177 ms
icon_footer_zoom_in.png
190 ms
icon_footer_send_link.png
191 ms
icon_footer_add_message.png
202 ms
icon_footer_profile_friend.png
203 ms
icon_footer_profile_group.png
268 ms
icon_footer_overview.png
269 ms
icon_footer_close_all.png
287 ms
icon_close_active.png
284 ms
icon_close_active_tooltip.png
298 ms
icon_zoom_in_tooltip.png
300 ms
icon_add_message_tooltip.png
353 ms
empty_1x1.gif
354 ms
intro_register.png
363 ms
intro_skip.png
371 ms
intro_travel.png
383 ms
intro_groups.png
385 ms
intro_maplog.png
435 ms
intro_pages_groups_1.png
436 ms
intro_pages_travel_1.png
451 ms
intro_pages_maplog_1.png
473 ms
logo_treelz.png
478 ms
black_corner_t_l.png
480 ms
black_corner_t_r.png
522 ms
ajax-loader_1.gif
524 ms
__utm.gif
11 ms
icon_close_inactive.png
512 ms
counter_div_l_c.png
533 ms
counter_div_r_c.png
540 ms
loading_indicator_3.gif
543 ms
shadow.png
573 ms
landmarks.png
582 ms
worldmap.png
570 ms
login.png
587 ms
black_corner_t_l.png
586 ms
black_corner_t_r.png
587 ms
EN_intro_skip.png
544 ms
EN_intro_register.png
550 ms
EN_intro_groups.png
741 ms
EN_intro_travel.png
799 ms
EN_intro_pages_groups_1.png
681 ms
EN_intro_pages_travel_1.png
779 ms
EN_intro_pages_maplog_1.png
556 ms
EN_intro_maplog.png
721 ms
common.js
28 ms
map.js
29 ms
overlay.js
26 ms
util.js
26 ms
geocoder.js
25 ms
intro_register.png
136 ms
intro_skip.png
135 ms
intro_travel.png
131 ms
intro_groups.png
836 ms
intro_maplog.png
132 ms
intro_pages_groups_1.png
142 ms
intro_pages_travel_1.png
224 ms
intro_pages_maplog_1.png
224 ms
black_corner_t_l.png
232 ms
black_corner_t_r.png
234 ms
empty_bu_search.gif
294 ms
selection_cap_top.png
300 ms
selection_cap_bottom.png
322 ms
selection_expand_category.png
322 ms
icon_selection_Global.png
323 ms
icon_selection_Groups.png
324 ms
icon_selection_Friends.png
371 ms
icon_selection_Search.png
397 ms
footer_bg_zoom.png
395 ms
onion.js
29 ms
openhand_8_8.cur
21 ms
flag_gb.gif
317 ms
flag_us.gif
312 ms
menu_arrow.png
377 ms
html;charset=utf-8,%3Chtml%3E%3Chead%3E%3Cscript%20type%3D%22text%2Fjavascript%22%3Ewindow.onresize%3Dfunction()%7Bwindow.parent.YAHOO.widget.Module.textResizeEvent.fire()%3B%7D%3B%3C%2Fscript%3E%3C%2Fhead%3E%3Cbody%3E%3C%2Fbody%3E%3C%2Fhtml%3E
40 ms
jsonapi.php
521 ms
ViewportInfoService.GetViewportInfo
47 ms
stats.js
38 ms
transparent.png
39 ms
kh
38 ms
kh
42 ms
controls.js
28 ms
infowindow.js
27 ms
kh
21 ms
kh
83 ms
kh
85 ms
kh
95 ms
kh
83 ms
kh
85 ms
kh
89 ms
kh
90 ms
kh
90 ms
kh
89 ms
kh
93 ms
kh
89 ms
kh
90 ms
kh
93 ms
jsonapi.php
553 ms
css
49 ms
jsonapi.php
391 ms
google4.png
63 ms
marker.js
39 ms
mapcnt6.png
32 ms
sv5.png
31 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
22 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
22 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
24 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
24 ms
tmapctrl.png
23 ms
cb_scout5.png
26 ms
tmapctrl4.png
25 ms
imgs8.png
25 ms
google_white5.png
24 ms
icon_cat_1100.png
109 ms
icon_cat_1200.png
106 ms
icon_cat_1300.png
105 ms
icon_cat_1400.png
100 ms
icon_cat_1500.png
193 ms
icon_cat_1600.png
191 ms
icon_cat_1700.png
204 ms
icon_cat_1800.png
200 ms
treelz.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
treelz.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
treelz.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 Treelz.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 Treelz.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.
treelz.com
Open Graph description is not detected on the main page of Treelz. 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: