5.2 sec in total
798 ms
4.2 sec
151 ms
Welcome to hypetree.com homepage info - get ready to check Hypetree best content right away, or after learning these important things about hypetree.com
Join the musical democracy - discover and rate thousands of songs exclusively by independent musicians
Visit hypetree.comWe analyzed Hypetree.com page load time and found that the first response time was 798 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
hypetree.com performance score
798 ms
95 ms
93 ms
92 ms
24 ms
Our browser made a total of 158 requests to load all elements on the main page. We found that 61% of them (96 requests) were addressed to the original Hypetree.com, 6% (9 requests) were made to D.adroll.com and 5% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Hypetree.com.
Page size can be reduced by 808.1 kB (31%)
2.6 MB
1.8 MB
In fact, the total size of Hypetree.com main page is 2.6 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. 65% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 155.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. This page needs HTML code to be minified as it can gain 25.7 kB, which is 14% 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 155.4 kB or 87% of the original size.
Potential reduce by 63.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. Hypetree images are well optimized though.
Potential reduce by 503.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 503.9 kB or 73% of the original size.
Potential reduce by 85.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. Hypetree.com needs all CSS files to be minified and compressed as it can save up to 85.8 kB or 81% of the original size.
Number of requests can be reduced by 61 (44%)
139
78
The browser has sent 139 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hypetree. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
hypetree.com
798 ms
screen.css
95 ms
main.css
93 ms
form.css
92 ms
css
24 ms
tree.css
96 ms
inlinewidget.css
95 ms
jquery-ui.css
222 ms
circle.player.css
182 ms
widget_PlayerLaunch.css
181 ms
jquery.ui.selectmenu.css
181 ms
styles.css
185 ms
panel.css
232 ms
jquery.js
474 ms
jquery-ui.min.js
444 ms
jquery.ba-bbq.js
337 ms
main.js
267 ms
player.js
302 ms
jquery.jplayer.min.js
390 ms
jquery.transform.js
350 ms
jquery.grab.js
381 ms
mod.csstransforms.min.js
421 ms
circle.player.js
430 ms
widget_PlayerLaunch.js
519 ms
font-awesome.css
4 ms
hostedbadge.php
311 ms
plusone.js
71 ms
conversion.js
80 ms
jquery.ui.selectmenu.js
552 ms
jquery.yiigridview.js
447 ms
TitilliumText22L001-webfont.ttf
138 ms
ga.js
21 ms
main_logo.png
125 ms
290_thumbnail_1326923136.jpg
125 ms
92_thumbnail_1319754741.png
235 ms
nophoto.png
126 ms
184_thumbnail_1324332575.jpg
164 ms
416_thumbnail_1330352889.jpg
163 ms
5_thumbnail_1339297752.jpg
173 ms
rw_hover.png
172 ms
ff_hover.png
173 ms
110_thumbnail_1319757749.jpg
311 ms
167_thumbnail_1323653603.jpg
311 ms
85_thumbnail_1319730249.jpg
423 ms
149_thumbnail_1321479039.jpg
329 ms
136_thumbnail_1351811126.jpg
309 ms
77_thumbnail_1319708851.jpg
402 ms
112_thumbnail_1319763031.jpg
403 ms
298_thumbnail_1327081288.jpg
406 ms
199_thumbnail_1326262432.jpg
440 ms
97_thumbnail_1321790954.jpg
412 ms
136_thumbnail_1320117916.jpg
530 ms
102_thumbnail_1319739153.jpg
493 ms
227_thumbnail_1326274537.jpg
530 ms
129_thumbnail_1319911782.jpg
530 ms
387_thumbnail_1328984894.jpg
547 ms
126_thumbnail_1319877716.jpg
572 ms
117_thumbnail_1319780245.jpg
605 ms
147_thumbnail_1320893706.jpg
656 ms
320_thumbnail_1327267728.jpg
656 ms
101_thumbnail_1320169996.jpg
661 ms
247_thumbnail_1335195603.jpg
674 ms
131_thumbnail_1319976812.jpg
666 ms
138_thumbnail_1320148958.jpg
687 ms
gtm.js
113 ms
43_thumbnail_1361409329.jpg
765 ms
95_thumbnail_1319738198.jpg
759 ms
__utm.gif
44 ms
69_thumbnail_1340063530.png
786 ms
87_thumbnail_1319735846.jpg
670 ms
257_thumbnail_1326315242.jpg
677 ms
94_thumbnail_1319734862.jpg
682 ms
TitilliumText22L006-webfont.ttf
772 ms
TitilliumText22L004-webfont.ttf
744 ms
all.js
282 ms
TitilliumText22L005-webfont.ttf
740 ms
TitilliumText22L003-webfont.ttf
748 ms
311_thumbnail_1327265292.jpeg
756 ms
widgets.js
13 ms
29_thumbnail_1306712930.jpg
838 ms
widgets.js
135 ms
cb=gapi.loaded_0
12 ms
7YzohYgKO4m334xaeIGwaQ.js
155 ms
27 ms
208 ms
111 ms
cb=gapi.loaded_1
30 ms
fastbutton
76 ms
243_thumbnail_1326297822.jpg
714 ms
6_thumbnail_1341599593.png
786 ms
254_thumbnail_1326315469.jpg
682 ms
148_thumbnail_1321311866.jpg
726 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
164 ms
79 ms
postmessageRelay
71 ms
141_thumbnail_1320414149.jpg
703 ms
feedback-tab.png
25 ms
cb=gapi.loaded_0
17 ms
cb=gapi.loaded_1
17 ms
pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf
42 ms
tab-left-dark-e89fceb89af232658b40362993385936.png
19 ms
badge_su.js
157 ms
badges_su.css
160 ms
1_thumbnail_1345666290.jpg
706 ms
348_thumbnail_1327344543.jpg
727 ms
3193398744-postmessagerelay.js
35 ms
rpc:shindig_random.js
82 ms
399_thumbnail_1329872218.jpg
727 ms
78_thumbnail_1319820428.jpg
745 ms
139_thumbnail_1333071367.jpg
702 ms
164_thumbnail_1323041754.jpg
737 ms
cb=gapi.loaded_0
17 ms
247 ms
1369_thumbnail_1339792877.jpg
723 ms
xd_arbiter.php
222 ms
xd_arbiter.php
441 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
44 ms
songsprouts_476.jpg
705 ms
231_thumbnail_1326285162.jpg
717 ms
radio.png
688 ms
wing_left.png
689 ms
badgeRect74x18.png
69 ms
wing_right.png
682 ms
bg_main_tree.png
801 ms
logo_banner.png
655 ms
hypetree.com
1376 ms
progress.png
662 ms
progress-full.png
658 ms
jot
91 ms
controls.jpg
661 ms
ui-icons_888888_256x240.png
709 ms
ui-bg_flat_75_ffffff_40x100.png
635 ms
print.css
49 ms
roundtrip.js
25 ms
track.js
157 ms
M444QK2SWJEKBIT7BMH5OE.js
489 ms
like.php
195 ms
qeKvIRsJabD.js
492 ms
LVx-xkvaJ0b.png
555 ms
fbevents.hashing.js
70 ms
out
9 ms
19 ms
out
6 ms
out
9 ms
out
8 ms
out
10 ms
out
10 ms
out
10 ms
out
10 ms
u.php
154 ms
adsct
96 ms
pixel
71 ms
sync
4 ms
33 ms
377928.gif
28 ms
sd
28 ms
22 ms
in
6 ms
hypetree.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hypetree.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Hypetree.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.
hypetree.com
Open Graph data is detected on the main page of Hypetree. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: