1.8 sec in total
281 ms
1.3 sec
215 ms
Visit mozfr.org now to see the best up-to-date Mozfr content for France and also check out these interesting facts you probably never knew about mozfr.org
Bienvenue sur le site de la communauté Mozilla francophone, aidez-nous et rejoignez-nous pour promouvoir un internet libre et ouvert à tous !
Visit mozfr.orgWe analyzed Mozfr.org page load time and found that the first response time was 281 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
mozfr.org performance score
name
value
score
weighting
Value1.5 s
96/100
10%
Value2.2 s
94/100
25%
Value1.8 s
100/100
10%
Value10 ms
100/100
30%
Value0
100/100
15%
Value3.3 s
94/100
10%
281 ms
93 ms
607 ms
310 ms
180 ms
Our browser made a total of 31 requests to load all elements on the main page. We found that 90% of them (28 requests) were addressed to the original Mozfr.org, 3% (1 request) were made to Soutien.laquadrature.net and 3% (1 request) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (607 ms) relates to the external source Soutien.laquadrature.net.
Page size can be reduced by 191.3 kB (45%)
425.0 kB
233.6 kB
In fact, the total size of Mozfr.org main page is 425.0 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. 35% of websites need less resources to load. Images take 181.4 kB which makes up the majority of the site volume.
Potential reduce by 9.1 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 2.4 kB, which is 19% 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 9.1 kB or 71% of the original size.
Potential reduce by 18.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. Mozfr images are well optimized though.
Potential reduce by 123.2 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 123.2 kB or 68% of the original size.
Potential reduce by 40.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. Mozfr.org needs all CSS files to be minified and compressed as it can save up to 40.9 kB or 82% of the original size.
Number of requests can be reduced by 4 (15%)
26
22
The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mozfr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
mozfr.org
281 ms
style.css
93 ms
support_lqdn_250_B_fr.png
607 ms
jquery-1.7.2.min.js
310 ms
tabzilla.js
180 ms
nav-main.js
178 ms
FFx-Australis_banner_300x250.png
308 ms
newsletter.png
263 ms
tabzilla.css
93 ms
sandstone.css
177 ms
widgets.js
34 ms
bg-sky.png
91 ms
tab.png
91 ms
mozfr.png
92 ms
twitter_logo_32.png
92 ms
firefox_48px.png
112 ms
nightly_48px.png
114 ms
play_48px.png
176 ms
iTunes_44x15.png
177 ms
thunderbird_48px.png
182 ms
mozfr_32px.png
183 ms
notreinternet_32px.png
199 ms
firefoxos_32px.png
199 ms
bidouilleux_32px.png
269 ms
geckozone_32px.png
268 ms
logo-mozilla.png
269 ms
OpenSans-Regular-webfont.woff
507 ms
OpenSans-Bold-webfont.woff
424 ms
OpenSans-Semibold-webfont.woff
424 ms
OpenSans-Light-webfont.woff
406 ms
piwik.js
488 ms
mozfr.org 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
Image elements do not have [alt] attributes
mozfr.org 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
General
Impact
Issue
Detected JavaScript libraries
mozfr.org SEO score
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
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
Tap targets are not sized appropriately
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mozfr.org 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 Mozfr.org 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.
mozfr.org
Open Graph description is not detected on the main page of Mozfr. 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: