4.6 sec in total
208 ms
2.7 sec
1.7 sec
Welcome to fragil.org homepage info - get ready to check Fragil best content for France right away, or after learning these important things about fragil.org
Magazine collaboratif et citoyen produit dans la métropole nantaise dans le style Do It Yourself, Fragil anime aussi des ateliers d'éducation aux médias.
Visit fragil.orgWe analyzed Fragil.org page load time and found that the first response time was 208 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
fragil.org performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value12.4 s
0/100
25%
Value12.9 s
2/100
10%
Value530 ms
56/100
30%
Value0.124
83/100
15%
Value17.9 s
3/100
10%
208 ms
655 ms
78 ms
137 ms
137 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 97% of them (65 requests) were addressed to the original Fragil.org, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Fragil.org.
Page size can be reduced by 420.2 kB (5%)
9.1 MB
8.7 MB
In fact, the total size of Fragil.org main page is 9.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. 55% of websites need less resources to load. Images take 8.9 MB which makes up the majority of the site volume.
Potential reduce by 19.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 3.4 kB, which is 14% 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 19.1 kB or 77% of the original size.
Potential reduce by 215.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. Fragil images are well optimized though.
Potential reduce by 161.4 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 161.4 kB or 79% of the original size.
Potential reduce by 24.2 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. Fragil.org needs all CSS files to be minified and compressed as it can save up to 24.2 kB or 81% of the original size.
Number of requests can be reduced by 27 (42%)
65
38
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fragil. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
fragil.org
208 ms
www.fragil.org
655 ms
initial.css
78 ms
base.css
137 ms
layout.css
137 ms
header.css
137 ms
navigation.css
138 ms
spip_style.css
149 ms
home.css
152 ms
sections.css
205 ms
liste_focus.css
207 ms
api.js
208 ms
prototype.js
276 ms
scriptaculous.js
223 ms
ufo.js
230 ms
urchin.js
5 ms
builder.js
79 ms
effects.js
76 ms
dragdrop.js
75 ms
controls.js
82 ms
slider.js
73 ms
wrapper_background.gif
77 ms
logo.gif
136 ms
recherche.gif
72 ms
newsletter.gif
77 ms
arton2178.jpg
266 ms
arrow-up.gif
74 ms
participez_140.jpg
140 ms
arton2664.jpg
286 ms
rss.gif
159 ms
autocrop_200_100_BANportraits.jpg
182 ms
read_more.gif
204 ms
published.gif
208 ms
autocrop_200_100_BAN-2.jpg
242 ms
autocrop_200_100_BANMeisAlpha-WannFuzzyon1.jpg
256 ms
autocrop_200_100_BANAlphaWannFuzzyon13.jpg
273 ms
sidebar-top.png
276 ms
arton580.jpg
401 ms
arton2567.jpg
922 ms
arton2631.jpg
471 ms
arton2598.jpg
1425 ms
arton2647.jpg
610 ms
arton2605.jpg
421 ms
arton2599.jpg
555 ms
arton2583.jpg
1420 ms
arton2642.jpg
548 ms
arton2593.jpg
1352 ms
arton2524.jpg
1007 ms
arton2568.jpg
879 ms
arton2544.jpg
1089 ms
arton2589.png
1001 ms
arton2615.jpg
1086 ms
arton2517.jpg
1092 ms
arton2617.jpg
1161 ms
autocrop_240_120_NUMBAN.jpg
1158 ms
arton2654.jpg
1254 ms
arton2652.jpg
1213 ms
__utm.gif
3 ms
arton2651.jpg
1243 ms
arton2650.jpg
1308 ms
arton2637.jpg
1333 ms
autocrop_240_120_BAN_ETAU.jpg
1321 ms
arton2640.jpg
1301 ms
arton2638.jpg
1311 ms
comments.gif
1316 ms
quote-top-footer.png
1303 ms
quote-bottom-footer.png
1290 ms
fragil.org 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-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
fragil.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
Page has valid source maps
fragil.org 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
Tap targets are not sized appropriately
FR
FR
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fragil.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 Fragil.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
fragil.org
Open Graph description is not detected on the main page of Fragil. 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: