6.4 sec in total
544 ms
4.7 sec
1.1 sec
Visit fellowgeek.tumblr.com now to see the best up-to-date Fellow GEEK Tumblr content for United States and also check out these interesting facts you probably never knew about fellowgeek.tumblr.com
Visit fellowgeek.tumblr.comWe analyzed Fellowgeek.tumblr.com page load time and found that the first response time was 544 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
fellowgeek.tumblr.com performance score
544 ms
15 ms
22 ms
30 ms
23 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fellowgeek.tumblr.com, 27% (20 requests) were made to Static.tumblr.com and 20% (15 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Fellowgeek.com.
Page size can be reduced by 631.8 kB (67%)
941.7 kB
309.9 kB
In fact, the total size of Fellowgeek.tumblr.com main page is 941.7 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. 60% of websites need less resources to load. Javascripts take 714.4 kB which makes up the majority of the site volume.
Potential reduce by 122.8 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 122.8 kB or 87% of the original size.
Potential reduce by 8.4 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, Fellow GEEK Tumblr needs image optimization as it can save up to 8.4 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 463.2 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 463.2 kB or 65% of the original size.
Potential reduce by 37.3 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. Fellowgeek.tumblr.com needs all CSS files to be minified and compressed as it can save up to 37.3 kB or 82% of the original size.
Number of requests can be reduced by 33 (45%)
74
41
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fellow GEEK Tumblr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
fellowgeek.tumblr.com
544 ms
pre_tumblelog.js
15 ms
reset-min.css
22 ms
solaris.css
30 ms
jquery.fancybox-1.3.1.tumblr.css
23 ms
nivo-slider.css
26 ms
custom-nivo-slider.css
22 ms
jquery-1.4.4.min.js
42 ms
jquery.blend-min.js
26 ms
jquery.timeago.js
32 ms
jquery.fancybox-1.3.1.pack.js
76 ms
jquery.jscrollpane-min.js
77 ms
jquery.nivo.slider.pack.js
77 ms
cufon-yui.js
77 ms
league-gothic.font.js
107 ms
solaris.js
106 ms
tumblelog_post_message_queue.js
14 ms
stylesheet.css
21 ms
widgets.js
162 ms
index.js
66 ms
ga.js
469 ms
divider.png
437 ms
search-go.png
437 ms
top-nav.png
438 ms
top-media.png
440 ms
sprite.png
468 ms
post-icons-small.png
439 ms
impixu
513 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
254 ms
impixu
145 ms
analytics.html
165 ms
login_check.html
48 ms
__utm.gif
112 ms
like.php
261 ms
like.php
318 ms
like.php
317 ms
like.php
280 ms
like.php
300 ms
like.php
485 ms
avatar_d0d3b99ccdc4_40.png
79 ms
iframe_logo.png
28 ms
like.php
369 ms
like.php
379 ms
like.php
378 ms
like.php
427 ms
like.php
425 ms
like.php
463 ms
rapid-3.36.js
91 ms
rapidworker-1.2.js
95 ms
like.php
462 ms
like.php
414 ms
like.php
384 ms
ga.js
278 ms
analytics.js
96 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
193 ms
TY3MhkXpWJ-.js
713 ms
LVx-xkvaJ0b.png
777 ms
cs.js
281 ms
yql
417 ms
__utm.gif
70 ms
1553 ms
1498 ms
1274 ms
jot.html
35 ms
1555 ms
1535 ms
1621 ms
1578 ms
1730 ms
2175 ms
1791 ms
1090 ms
1147 ms
894 ms
cedexis.radar.js
4 ms
fellowgeek.tumblr.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fellowgeek.tumblr.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 Fellowgeek.tumblr.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.
fellowgeek.tumblr.com
Open Graph data is detected on the main page of Fellow GEEK Tumblr. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: