2.9 sec in total
203 ms
2 sec
670 ms
Welcome to whowillsurvive2012.com homepage info - get ready to check Whowillsurvive 2012 best content right away, or after learning these important things about whowillsurvive2012.com
2012 - From Roland Emmerich, director of THE DAY AFTER TOMORROW and INDEPENDENCE DAY, comes the ultimate action-adventure film, exploding with groundbreaking special effects. As the world faces a cata...
Visit whowillsurvive2012.comWe analyzed Whowillsurvive2012.com page load time and found that the first response time was 203 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
whowillsurvive2012.com performance score
203 ms
90 ms
300 ms
25 ms
568 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Whowillsurvive2012.com, 84% (59 requests) were made to Sonypictures.com and 7% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (941 ms) relates to the external source Sonypictures.com.
Page size can be reduced by 458.3 kB (50%)
918.8 kB
460.5 kB
In fact, the total size of Whowillsurvive2012.com main page is 918.8 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. 45% of websites need less resources to load. Javascripts take 374.3 kB which makes up the majority of the site volume.
Potential reduce by 14.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 14.8 kB or 76% of the original size.
Potential reduce by 17.6 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. Whowillsurvive 2012 images are well optimized though.
Potential reduce by 278.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 278.9 kB or 75% of the original size.
Potential reduce by 146.9 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. Whowillsurvive2012.com needs all CSS files to be minified and compressed as it can save up to 146.9 kB or 87% of the original size.
Number of requests can be reduced by 17 (27%)
62
45
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whowillsurvive 2012. 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 from 8 to 1 for CSS and as a result speed up the page load time.
whowillsurvive2012.com
203 ms
90 ms
300 ms
css
25 ms
jquery.jscrollpane.css
568 ms
portal.css
573 ms
title.css
218 ms
title-1024.css
77 ms
title-800.css
75 ms
title-480.css
150 ms
title-320.css
148 ms
jquery-1.4.2.min.js
941 ms
swfobject2.js
219 ms
jquery.jscrollpane.min.js
365 ms
jquery.mousewheel.js
285 ms
iscroll.js
366 ms
sp.js
359 ms
portal.js
627 ms
title.js
628 ms
s_code.js
515 ms
onesheet-background.jpg
627 ms
onesheet.jpg
636 ms
watch-now.jpg
639 ms
buynow_thumb_374x222.jpg
647 ms
onesheet-thumb.jpg
663 ms
onesheet-thumb.jpg
670 ms
onesheet-thumb.jpg
716 ms
onesheet-thumb.jpg
718 ms
noise.png
587 ms
bg-portal-nav.png
156 ms
sony-splogo-header.png
165 ms
button-get-updates.png
207 ms
follow-facebook.gif
207 ms
follow-twitter.gif
230 ms
follow-youtube.gif
239 ms
follow-googleplus.gif
279 ms
button-search.png
280 ms
bg-contentcontainer.gif
304 ms
bg-widgets-strip.png
313 ms
button-calltoaction-plus.png
352 ms
bg-buynow-top.png
353 ms
bg-buynow-bottom.png
580 ms
bg-buynow-content.png
583 ms
buynow-amazon.png
662 ms
buynow-itunes.png
586 ms
bg-widgets-container.png
587 ms
bg-widget.jpg
587 ms
bg-recommendations-gradient.jpg
588 ms
bg-footer-pattern.gif
589 ms
icon-footer-nav.png
590 ms
icon-usa.jpg
591 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
26 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
36 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
45 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
52 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
76 ms
iframe_api
214 ms
interstitials.json
220 ms
quick-view-left-arrow.png
75 ms
quick-view-right-arrow.png
75 ms
sony.gif
77 ms
button-videoplayer-close.gif
78 ms
bg-subcontent.png
76 ms
sonypicturesstore.jpg
148 ms
widget-carousel-previous.png
146 ms
widget-carousel-next.png
147 ms
widget-carousel-page.png
151 ms
s22748523789923
85 ms
www-widgetapi.js
27 ms
s21463767990935
86 ms
whowillsurvive2012.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whowillsurvive2012.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 Whowillsurvive2012.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.
whowillsurvive2012.com
Open Graph description is not detected on the main page of Whowillsurvive 2012. 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: