2.8 sec in total
513 ms
1.1 sec
1.2 sec
Click here to check amazing Obliteratiparty content. Otherwise, check out these important facts you probably never knew about obliteratiparty.com
Tumblr. Pure effervescent enrichment. Old internet energy. Home of the Reblogs. All the art you never knew you needed. All the fandoms you could wish for. Enough memes to knock out a moderately-sized ...
Visit obliteratiparty.comWe analyzed Obliteratiparty.com page load time and found that the first response time was 513 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
obliteratiparty.com performance score
513 ms
17 ms
11 ms
13 ms
10 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Obliteratiparty.com, 35% (20 requests) were made to Static.tumblr.com and 14% (8 requests) were made to Assets.tumblr.com. The less responsive or slowest element that took the longest time to load (513 ms) belongs to the original domain Obliteratiparty.com.
Page size can be reduced by 445.7 kB (26%)
1.7 MB
1.3 MB
In fact, the total size of Obliteratiparty.com main page is 1.7 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. 60% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 79.6 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 79.6 kB or 79% of the original size.
Potential reduce by 41.9 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. Obliteratiparty images are well optimized though.
Potential reduce by 319.1 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 319.1 kB or 65% of the original size.
Potential reduce by 5.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. Obliteratiparty.com needs all CSS files to be minified and compressed as it can save up to 5.0 kB or 78% of the original size.
Number of requests can be reduced by 18 (35%)
51
33
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Obliteratiparty. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
obliteratiparty.com
513 ms
pre_tumblelog.js
17 ms
jquery.fancybox-tumblr.css
11 ms
jquery-1.3.2.min.js
13 ms
fluid.js
10 ms
jquery.fancybox-1.2.1.pack.js
12 ms
cufon-min.js
10 ms
tg.js
38 ms
tumblelog_post_message_queue.js
36 ms
stylesheet.css
36 ms
index.js
86 ms
obliteratihomeimage2.png
498 ms
tumblr_nn2fo5fJS11qatda9o1_500.jpg
315 ms
tumblr_nj7wzc08O11qatda9o1_500.jpg
202 ms
tumblr_ndwn1uWivy1qatda9o1_500.jpg
166 ms
false
195 ms
avatar_a3ba92646bf1_64.png
372 ms
impixu
286 ms
PDF_icon.png
459 ms
tumblr_ndyc3tpLbr1qz9s3do1_500.jpg
310 ms
tumblr_n6164gdNYP1qz9s3do1_500.jpg
354 ms
tumblr_n1cu62FibX1qatda9o1_500.jpg
356 ms
tumblr_n1csra0tKa1qz9s3do1_500.jpg
356 ms
tumblr_n030orn7zH1qatda9o1_r2_500.jpg
321 ms
tumblr_muigk2kiRo1qz9s3do1_500.jpg
355 ms
tumblr_mnd167RzLz1qz9s3do1_500.jpg
426 ms
background-body-repeat.png
141 ms
background-top.jpg
156 ms
background-main-top-bottom.png
142 ms
background-main-repeat.png
141 ms
post-icons.png
141 ms
icon-zoom.png
142 ms
background-container.png
141 ms
icon-reblogged.png
149 ms
icon-linkpost-arrow.png
152 ms
background-sidebar-heading.png
147 ms
background-user-portrait.png
148 ms
background-load-more-posts.png
150 ms
button-next.png
150 ms
impixu
274 ms
tumblr_mu1pkpq6Gr1qatda9o1_500.jpg
151 ms
tumblr_mrzgn5ZxpT1qz9s3do1_500.jpg
148 ms
tumblr_mr67pdhuII1qatda9o1_500.jpg
150 ms
analytics.html
264 ms
new-spinner-still.png
39 ms
login_check.html
33 ms
tumblr_n5kud2WpYD1qatda9o1_500.png
116 ms
tumblr_n5kud2WpYD1qatda9o2_r1_500.png
261 ms
avatar_a3ba92646bf1_40.png
109 ms
iframe_logo.png
27 ms
rapid-3.36.js
39 ms
rapidworker-1.2.js
43 ms
ga.js
62 ms
analytics.js
44 ms
cs.js
56 ms
__utm.gif
19 ms
cedexis.radar.js
4 ms
obliteratiparty.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Obliteratiparty.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 Obliteratiparty.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.
obliteratiparty.com
Open Graph data is detected on the main page of Obliteratiparty. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: