1.3 sec in total
229 ms
686 ms
372 ms
Visit thomm.es now to see the best up-to-date Thomm content and also check out these interesting facts you probably never knew about thomm.es
Visit thomm.esWe analyzed Thomm.es page load time and found that the first response time was 229 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
thomm.es performance score
229 ms
9 ms
23 ms
21 ms
15 ms
Our browser made a total of 31 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Thomm.es, 45% (14 requests) were made to Assets.tumblr.com and 13% (4 requests) were made to 41.media.tumblr.com. The less responsive or slowest element that took the longest time to load (369 ms) relates to the external source 40.media.tumblr.com.
Page size can be reduced by 422.0 kB (38%)
1.1 MB
691.5 kB
In fact, the total size of Thomm.es main page is 1.1 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. 45% of websites need less resources to load. Javascripts take 588.7 kB which makes up the majority of the site volume.
Potential reduce by 29.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. This page needs HTML code to be minified as it can gain 6.3 kB, which is 17% 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 29.2 kB or 79% of the original size.
Potential reduce by 8.8 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. Thomm images are well optimized though.
Potential reduce by 381.5 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 381.5 kB or 65% of the original size.
Potential reduce by 2.5 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. Thomm.es needs all CSS files to be minified and compressed as it can save up to 2.5 kB or 82% of the original size.
Number of requests can be reduced by 10 (38%)
26
16
The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thomm. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
thomm.es
229 ms
pre_tumblelog.js
9 ms
jquery-1.9.1.min.js
23 ms
infinitescrolling.js
21 ms
tumblelog_post_message_queue.js
15 ms
stylesheet.css
15 ms
stylesheet.css
16 ms
index.js
16 ms
tumblr_nn8a791veo1u0amrdo1_1280.jpg
206 ms
tumblr_ncxifaxokT1u0amrdo2_r1_1280.jpg
369 ms
impixu
99 ms
impixu
97 ms
tumblr_ncxifaxokT1u0amrdo3_r2_400.jpg
338 ms
tumblr_nlqcjn0XPV1u0amrdo1_1280.jpg
167 ms
tumblr_nl45vlRpwh1u0amrdo1_1280.jpg
178 ms
tumblr_ncxifaxokT1u0amrdo1_1280.jpg
260 ms
analytics.html
107 ms
Calluna-Regular-webfont.woff
29 ms
Calluna-Black-webfont.woff
93 ms
Gibson-SemiBold-webfont.woff
23 ms
Gibson-Regular-webfont.woff
23 ms
login_check.html
28 ms
cube_closed_40.png
14 ms
iframe_logo.png
16 ms
rapid-3.36.js
29 ms
rapidworker-1.2.js
38 ms
ga.js
71 ms
analytics.js
30 ms
cs.js
41 ms
__utm.gif
18 ms
cedexis.radar.js
5 ms
thomm.es 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 Thomm.es 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 Thomm.es 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.
thomm.es
Open Graph description is not detected on the main page of Thomm. 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: