4 sec in total
369 ms
3.4 sec
225 ms
Click here to check amazing Survivre 2012 content. Otherwise, check out these important facts you probably never knew about survivre-2012.com
La fin du monde est annoncée pour 2012 ? Notre boutique propose l'équipement nécessaire à votre survie.
Visit survivre-2012.comWe analyzed Survivre-2012.com page load time and found that the first response time was 369 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
survivre-2012.com performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value7.5 s
4/100
25%
Value6.3 s
42/100
10%
Value710 ms
41/100
30%
Value0.017
100/100
15%
Value14.8 s
8/100
10%
369 ms
643 ms
88 ms
169 ms
36 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 34% of them (31 requests) were addressed to the original Survivre-2012.com, 13% (12 requests) were made to Static.xx.fbcdn.net and 10% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (694 ms) relates to the external source Bricozor.com.
Page size can be reduced by 375.2 kB (64%)
582.9 kB
207.7 kB
In fact, the total size of Survivre-2012.com main page is 582.9 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. 65% of websites need less resources to load. CSS take 244.2 kB which makes up the majority of the site volume.
Potential reduce by 24.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 4.7 kB, which is 15% 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 24.2 kB or 77% of the original size.
Potential reduce by 4.5 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. Survivre 2012 images are well optimized though.
Potential reduce by 143.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 143.9 kB or 60% of the original size.
Potential reduce by 202.6 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. Survivre-2012.com needs all CSS files to be minified and compressed as it can save up to 202.6 kB or 83% of the original size.
Number of requests can be reduced by 45 (53%)
85
40
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Survivre 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 34 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
survivre-2012.com
369 ms
www.survivre-2012.com
643 ms
screen.css
88 ms
boutique2012.css
169 ms
css
36 ms
plusone.js
68 ms
jquery-1.7.min.js
339 ms
jquery.fancybox-1.3.4.pack.js
182 ms
jquery.fancybox-1.3.4.css
177 ms
product.js
178 ms
cart.js
178 ms
application.js
247 ms
widgets.js
23 ms
all.js
284 ms
cb=gapi.loaded_0
5 ms
s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf
9 ms
EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf
42 ms
print.css
148 ms
ga.js
38 ms
logobz.gif
139 ms
cart.gif
139 ms
fondtexture.jpg
187 ms
texture.gif
139 ms
icone-respirer.gif
139 ms
icone-protection.gif
205 ms
icone-boire.gif
205 ms
icone-manger.gif
205 ms
pictos.gif
204 ms
arton6590-3dc6f.jpg
204 ms
arton7292-76903.jpg
257 ms
arton5467-7d349.jpg
412 ms
arton4973-097cf.jpg
409 ms
arton6874-ea407.jpg
410 ms
arton5098-ca181.jpg
410 ms
logobzbig.gif
407 ms
zO6E606pcKI
139 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
64 ms
price
691 ms
price
689 ms
price
693 ms
price
691 ms
price
694 ms
price
694 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
73 ms
cb=gapi.loaded_1
53 ms
fastbutton
95 ms
minipictos.gif
317 ms
barre.gif
340 ms
barrerouge.gif
339 ms
barrebrune.gif
339 ms
__utm.gif
29 ms
303 ms
xd_arbiter.php
281 ms
xd_arbiter.php
487 ms
postmessageRelay
63 ms
www-embed-player-vflfNyN_r.css
53 ms
www-embed-player.js
68 ms
base.js
103 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.fr.html
29 ms
cb=gapi.loaded_0
28 ms
cb=gapi.loaded_1
26 ms
3193398744-postmessagerelay.js
43 ms
rpc:shindig_random.js
39 ms
cb=gapi.loaded_0
140 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
62 ms
ad_status.js
99 ms
jot
136 ms
likebox.php
252 ms
like.php
285 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
80 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
81 ms
kyEKgjk51ZE.css
282 ms
xgj7bXhJNEH.css
352 ms
q68gy-v_YMF.js
488 ms
FJmpeSpHpjS.js
618 ms
0wM5s1Khldu.js
516 ms
1bNoFZUdlYZ.js
486 ms
05-jfvEi0Bv.js
638 ms
LVx-xkvaJ0b.png
457 ms
484045_407641752605200_1009753330_n.jpg
342 ms
383145_281939195175457_1852771321_n.jpg
470 ms
10409757_1518392835073812_1961448192556697010_n.jpg
538 ms
12642904_156248711421301_336852035011753436_n.jpg
566 ms
12745441_140667656320618_5195568462698947650_n.jpg
543 ms
11181340_707648519345000_8248950479542484056_n.jpg
586 ms
1891030_1383081791961709_1267291429_n.jpg
661 ms
1917476_585547218281215_3934322585693291617_n.jpg
544 ms
11012562_784463111682780_6423851394899311977_n.jpg
646 ms
wL6VQj7Ab77.png
71 ms
s7jcwEQH7Sx.png
70 ms
I6-MnjEovm5.js
71 ms
pQrUxxo5oQp.js
71 ms
survivre-2012.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
survivre-2012.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
survivre-2012.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
FR
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Survivre-2012.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Survivre-2012.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.
survivre-2012.com
Open Graph description is not detected on the main page of Survivre 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: