4.4 sec in total
56 ms
4.1 sec
190 ms
Welcome to fournaise.info homepage info - get ready to check Fournaise best content for France right away, or after learning these important things about fournaise.info
L'actualité d'un volcan très actif à la Réunion, au jour le jour ! Éruptions, randonnées, pédagogie, médiathèque; de très nombreuses ressources pour petits et grands.
Visit fournaise.infoWe analyzed Fournaise.info page load time and found that the first response time was 56 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
fournaise.info performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value10.0 s
0/100
25%
Value12.4 s
3/100
10%
Value3,450 ms
2/100
30%
Value1.003
2/100
15%
Value24.3 s
0/100
10%
56 ms
1765 ms
437 ms
424 ms
35 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 88% of them (82 requests) were addressed to the original Fournaise.info, 4% (4 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Fournaise.info.
Page size can be reduced by 727.6 kB (24%)
3.1 MB
2.4 MB
In fact, the total size of Fournaise.info main page is 3.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. Only a small number of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 718.7 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 718.7 kB or 87% of the original size.
Potential reduce by 1.1 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. Fournaise images are well optimized though.
Potential reduce by 2.3 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. This website has mostly compressed JavaScripts.
Potential reduce by 5.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. Fournaise.info has all CSS files already compressed.
Number of requests can be reduced by 52 (66%)
79
27
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fournaise. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
fournaise.info
56 ms
fournaise.info
1765 ms
dfd_icon_set.css
437 ms
style.min.css
424 ms
style.css
35 ms
post-group.css
334 ms
post-trisec.css
337 ms
post-slider.css
57 ms
extendify-utilities.css
66 ms
wonderplugincarouselengine.css
85 ms
jquery.fancyNews.min.css
100 ms
font-awesome.min.css
109 ms
font-awesome.min.css
31 ms
ticker-style.min.css
120 ms
slick.min.css
132 ms
slick-theme.min.css
141 ms
styled-button.css
153 ms
default.css
166 ms
js_composer.min.css
212 ms
visual-composer.css
226 ms
app.css
251 ms
mobile-responsive.css
290 ms
style.css
607 ms
jquery.min.js
95 ms
jquery-migrate.min.js
116 ms
swiper-bundle.min.js
119 ms
wonderplugincarouselskins.js
131 ms
wonderplugincarousel.js
594 ms
core.min.js
444 ms
image-autorefresh.js
143 ms
slick.min.js
156 ms
tweecool.min.js
173 ms
nb-frontend.min.js
184 ms
nb-subscribe.min.js
197 ms
26070.js
236 ms
26069.css
227 ms
css
99 ms
iframe_api
81 ms
email-decode.min.js
190 ms
css
76 ms
v4-shims.min.css
203 ms
all.min.css
512 ms
css
75 ms
rs6.css
516 ms
jquery.form.min.js
214 ms
script.js
225 ms
rbtools.min.js
241 ms
rs6.min.js
388 ms
jquery.ticker.min.js
681 ms
compresed.min.js
395 ms
jquery.onepagescroll.min.js
409 ms
js_composer_front.min.js
719 ms
ultimate_bg.min.js
421 ms
logo-fournaise-info.jpg
37 ms
logo-fournaise-info-111x53.jpg
346 ms
flag-reunion.jpg
37 ms
flag-english.jpg
345 ms
flag-allemand.jpg
346 ms
Accueil-Fournaise-Info-1.jpg
37 ms
350532970_749581650508172_6574314003327558629_n-1024x683-900x600-1.jpg
48 ms
OLL-2-1024x681-900x600-1.jpg
58 ms
269837556_1597981000552972_551325918154466736_n-900x600-1.jpg
73 ms
10-900x600-1.jpg
91 ms
aline-peltier-900x600-1.jpg
722 ms
Frog-900x600-1.jpg
127 ms
Publication.Planetair-900x600-1.jpg
128 ms
fournaise.12.2020-11-900x600-1.jpg
130 ms
246449009_420893682735505_8139996180335423889_n-1024x469.jpg
140 ms
JLA2-900x600-1.jpg
139 ms
dummy.png
169 ms
logo-region-reunion-transparent.png
616 ms
texgyreadventor-regular-webfont.svg
582 ms
texgyreadventor-regular-webfont.woff
740 ms
fontawesome-webfont.woff
24 ms
fontawesome-webfont.woff
813 ms
0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqs.woff
35 ms
0QI6MX1D_JOuGQbT0gvTJPa787wsuxJBkqs.woff
36 ms
0QI6MX1D_JOuGQbT0gvTJPa787zAvBJBkqs.woff
51 ms
0QI6MX1D_JOuGQbT0gvTJPa787z5vBJBkqs.woff
52 ms
dfd_icon_set.svg
904 ms
dfd_icon_set.woff
1378 ms
www-widgetapi.js
18 ms
Remerciements-Founaise-Ingo.jpg
532 ms
dfd-added-font-icon.svg
899 ms
dfd-added-font-icon.ttf
992 ms
fa-solid-900.woff
1084 ms
fa-regular-400.woff
1036 ms
fa-brands-400.woff
1208 ms
froogaloop2.min.js
1083 ms
ajax-loader.gif
1099 ms
mhfontello.css
1194 ms
arrows-28-28-0.png
1098 ms
bullet-12-12-1.png
1099 ms
fournaise.info accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
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
Links do not have a discernible name
fournaise.info best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Page has valid source maps
fournaise.info SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
![]()
FR
![]()
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fournaise.info can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Fournaise.info 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.
fournaise.info
Open Graph data is detected on the main page of Fournaise. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: