2.2 sec in total
194 ms
1.8 sec
154 ms
Visit slooom.net now to see the best up-to-date Slooom content and also check out these interesting facts you probably never knew about slooom.net
Slooom is not a band.
Visit slooom.netWe analyzed Slooom.net page load time and found that the first response time was 194 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
slooom.net performance score
194 ms
33 ms
31 ms
51 ms
47 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Slooom.net, 22% (20 requests) were made to Pbs.twimg.com and 19% (18 requests) were made to Scontent.cdninstagram.com. The less responsive or slowest element that took the longest time to load (862 ms) relates to the external source Scontent.cdninstagram.com.
Page size can be reduced by 838.6 kB (42%)
2.0 MB
1.2 MB
In fact, the total size of Slooom.net main page is 2.0 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. Javascripts take 964.8 kB which makes up the majority of the site volume.
Potential reduce by 27.9 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 27.9 kB or 76% of the original size.
Potential reduce by 11.1 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. Slooom images are well optimized though.
Potential reduce by 645.8 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 645.8 kB or 67% of the original size.
Potential reduce by 153.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. Slooom.net needs all CSS files to be minified and compressed as it can save up to 153.8 kB or 86% of the original size.
Number of requests can be reduced by 31 (36%)
86
55
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Slooom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
slooom.net
194 ms
pre_tumblelog.js
33 ms
font-awesome.min.css
31 ms
jquery-1.9.1.min.js
51 ms
infinitescrolling.js
47 ms
tumblelog_post_message_queue.js
45 ms
stylesheet.css
47 ms
stylesheet.css
42 ms
slim-081711.css
44 ms
instansive.js
380 ms
index.js
45 ms
Bandcamp_icon.png
196 ms
126746715
94 ms
widgets.js
173 ms
player.js
135 ms
player.css
121 ms
ga.js
52 ms
vuid.min.js
111 ms
__utm.gif
35 ms
ArquitectaBook-webfont.woff
33 ms
ArquitectaBold-webfont.woff
24 ms
Gibson-SemiBold-webfont.woff
23 ms
Gibson-Regular-webfont.woff
20 ms
fontawesome-webfont.woff
22 ms
proxy.html
44 ms
529354615.jpg
597 ms
lightwidget.js
187 ms
impixu
79 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
124 ms
impixu
20 ms
analytics.html
36 ms
login_check.html
6 ms
c55b2fa8b9bd58fca3ab63f26ca80166.html
103 ms
rapid-3.36.js
38 ms
rapidworker-1.2.js
42 ms
analytics.js
81 ms
cs.js
89 ms
__utm.gif
45 ms
yql
187 ms
12558277_1806257106268193_1827853608_n.jpg
275 ms
analytics.js
51 ms
12543189_1642318392688024_1123306483_n.jpg
441 ms
12545329_1213105412050220_2118005191_n.jpg
446 ms
12424456_220298844975548_1522696230_n.jpg
487 ms
1516072_146278672411732_282055580_n.jpg
495 ms
10311313_160568914308442_1557005409_n.jpg
460 ms
12353868_1532001460445308_1308971367_n.jpg
492 ms
12224634_472368939625832_1060585912_n.jpg
572 ms
12299008_552509494901179_1429272887_n.jpg
560 ms
12558277_1806257106268193_1827853608_n.jpg
695 ms
12543189_1642318392688024_1123306483_n.jpg
689 ms
12545329_1213105412050220_2118005191_n.jpg
609 ms
12424456_220298844975548_1522696230_n.jpg
725 ms
1516072_146278672411732_282055580_n.jpg
795 ms
10311313_160568914308442_1557005409_n.jpg
774 ms
12353868_1532001460445308_1308971367_n.jpg
862 ms
12224634_472368939625832_1060585912_n.jpg
861 ms
12299008_552509494901179_1429272887_n.jpg
821 ms
syndication
125 ms
692398870379249664
253 ms
collect
19 ms
proxy.jpg
29 ms
1f918-1f3fe.png
160 ms
1f483-1f3ff.png
157 ms
1f483-1f3fd.png
180 ms
proxy.jpg
146 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
36 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
88 ms
RbIaXdLN_normal.jpeg
195 ms
s5MtK8yd_normal.png
262 ms
KwT4rccx_normal.jpg
294 ms
Mv4fgDci_normal.jpg
312 ms
VMJFLjka_normal.jpg
316 ms
wLHliJY-_normal.jpg
486 ms
HAG86aqt_normal.jpg
318 ms
DKIgQwJR_normal.jpg
322 ms
aca80e6n_normal.jpg
322 ms
ZRLJg2ie_normal.png
338 ms
pf1uSINm_normal.png
348 ms
bmjUDUrH_normal.png
350 ms
N_eNSBXi_normal.jpg
352 ms
VHT0GdjC_normal.jpg
384 ms
CdWFTvsWEAAUIIJ.jpg:large
411 ms
CcF6gRdUAAAbieJ.jpg:small
407 ms
CcRqpWRUYAAj51V.jpg:large
469 ms
CcGWnn1UYAA19p3.jpg:small
515 ms
Cbe8qn_VAAASYuH.jpg:large
519 ms
CbRT4QOUYAA26Al.jpg:small
532 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
50 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
58 ms
proxy.jpg
58 ms
jot.html
27 ms
cedexis.radar.js
4 ms
slooom.net 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 Slooom.net 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 Slooom.net 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.
slooom.net
Open Graph data is detected on the main page of Slooom. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: