5.2 sec in total
1.3 sec
3.4 sec
501 ms
Click here to check amazing Plantosurvive 2012 content. Otherwise, check out these important facts you probably never knew about plantosurvive2012.com
2012 May Not Be The "End of The World"... But Are You Prepared To Survive Any Upcoming Disasters And Hard Times???
Visit plantosurvive2012.comWe analyzed Plantosurvive2012.com page load time and found that the first response time was 1.3 sec and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
plantosurvive2012.com performance score
1278 ms
132 ms
145 ms
172 ms
253 ms
Our browser made a total of 131 requests to load all elements on the main page. We found that 43% of them (56 requests) were addressed to the original Plantosurvive2012.com, 8% (11 requests) were made to Forms.aweber.com and 7% (9 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Plantosurvive2012.com.
Page size can be reduced by 937.5 kB (60%)
1.6 MB
626.8 kB
In fact, the total size of Plantosurvive2012.com main page is 1.6 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 721.9 kB which makes up the majority of the site volume.
Potential reduce by 89.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 89.6 kB or 85% of the original size.
Potential reduce by 66.2 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, Plantosurvive 2012 needs image optimization as it can save up to 66.2 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 447.7 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 447.7 kB or 62% of the original size.
Potential reduce by 334.1 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. Plantosurvive2012.com needs all CSS files to be minified and compressed as it can save up to 334.1 kB or 83% of the original size.
Number of requests can be reduced by 84 (72%)
116
32
The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Plantosurvive 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 45 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
plantosurvive2012.com
1278 ms
style.css
132 ms
style.css
145 ms
main.css
172 ms
styles.css
253 ms
sociable.css
151 ms
css
28 ms
farbtastic.css
178 ms
styles.css
208 ms
facebookinviter-style.css
245 ms
frontend.css
259 ms
jquery.fancybox-1.3.4.css
262 ms
polls-css.css
243 ms
style.css
329 ms
post.css
336 ms
styles.css
350 ms
wpgfxm-general-styles.css
331 ms
jam-js.js
417 ms
jam-style.css
373 ms
jquery.min.js
9 ms
sociable.js
434 ms
vuible.js
435 ms
addtofavorites.js
434 ms
amazon-lightbox.js
455 ms
jquery.fitvids.min.js
472 ms
frontend.min.js
549 ms
jquery.fancybox-1.3.4.js
525 ms
jquery-ui.min.js
10 ms
button.fade.js
568 ms
button.fade.js
568 ms
index.php
1473 ms
amazon-lightbox.css
587 ms
optincrusher.css
607 ms
optincrusher.js
624 ms
plusone.js
35 ms
font-awesome.min.css
654 ms
style.css
650 ms
js
24 ms
jquery.gmap.js
671 ms
flexslider.css
704 ms
jquery.flexslider-min.js
711 ms
866184112.js
64 ms
widgets.js
80 ms
in.js
14 ms
hostedbadge.php
152 ms
9591095.js
59 ms
1705972837.js
60 ms
style.css
692 ms
plusone.js
59 ms
cb=gapi.loaded_0
6 ms
common.js
24 ms
util.js
25 ms
geocoder.js
25 ms
analytics.js
23 ms
ga.js
22 ms
NWn2U.gif
96 ms
enterdetailsred.jpg
94 ms
image-3143852-10985537
24 ms
image-3143852-10952537
20 ms
image-3143852-10952609
20 ms
image-3143852-10980617
22 ms
image-3143852-10985847
20 ms
image-3143852-10985828
21 ms
image-3143852-10979707
20 ms
bg-body.jpg
185 ms
bg-wrap.jpg
202 ms
bg-header-top.gif
88 ms
bg-menu.gif
89 ms
bg-menu-a.gif
87 ms
ad_bg.png
90 ms
more.png
187 ms
closelabel.png
183 ms
twitter.png
192 ms
facebook.png
192 ms
googleplus.png
254 ms
youtube.png
254 ms
linkedin.png
311 ms
feed.png
266 ms
rss-icon.jpg
366 ms
f00.png
67 ms
displays.htm
68 ms
10952537-1435164727388
68 ms
10952609-1435164664950
67 ms
10979707-1418407265539
64 ms
10985828-1417814780334
64 ms
10985537-1417814773235
65 ms
graublauwebbold-webfont.woff
293 ms
linkid.js
27 ms
__utm.gif
17 ms
option1_32.png
300 ms
YVe8Iji7DxY
114 ms
collect
162 ms
collect
34 ms
secureAnonymousFramework
105 ms
widgets.js
72 ms
header.png
20 ms
body.png
17 ms
07c.png
17 ms
displays.htm
75 ms
freereport-large2.jpg
373 ms
like.php
176 ms
button.png
110 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
204 ms
cb=gapi.loaded_1
33 ms
fastbutton
125 ms
header.png
19 ms
displays.htm
71 ms
bg-footer-bottom.gif
186 ms
192 ms
www-embed-player-vflfNyN_r.css
86 ms
www-embed-player.js
138 ms
postmessageRelay
154 ms
share
146 ms
sprite_connect_v14.png
149 ms
cb=gapi.loaded_0
81 ms
cb=gapi.loaded_1
65 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
108 ms
qeKvIRsJabD.js
109 ms
LVx-xkvaJ0b.png
129 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
59 ms
ad_status.js
59 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
49 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
49 ms
3193398744-postmessagerelay.js
49 ms
rpc:shindig_random.js
62 ms
badge_su.js
156 ms
badges_su.css
158 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
45 ms
cb=gapi.loaded_0
7 ms
badgeRound65x18.png
71 ms
jot
85 ms
plantosurvive2012.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Plantosurvive2012.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 Plantosurvive2012.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.
plantosurvive2012.com
Open Graph data is detected on the main page of Plantosurvive 2012. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: