6 sec in total
327 ms
2.2 sec
3.5 sec
Visit planete.drupalfr.org now to see the best up-to-date Planete Drupal Fr content for France and also check out these interesting facts you probably never knew about planete.drupalfr.org
Visit planete.drupalfr.orgWe analyzed Planete.drupalfr.org page load time and found that the first response time was 327 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
planete.drupalfr.org performance score
name
value
score
weighting
Value5.4 s
6/100
10%
Value5.7 s
17/100
25%
Value6.4 s
41/100
10%
Value270 ms
82/100
30%
Value0
100/100
15%
Value8.0 s
43/100
10%
327 ms
160 ms
164 ms
165 ms
166 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 49% of them (46 requests) were addressed to the original Planete.drupalfr.org, 23% (21 requests) were made to Vincentliefooghe.net and 5% (5 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Vincentliefooghe.net.
Page size can be reduced by 713.6 kB (28%)
2.6 MB
1.8 MB
In fact, the total size of Planete.drupalfr.org main page is 2.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. 65% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 166.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 166.7 kB or 80% of the original size.
Potential reduce by 374.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. Obviously, Planete Drupal Fr needs image optimization as it can save up to 374.5 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 80.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 80.2 kB or 60% of the original size.
Potential reduce by 92.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. Planete.drupalfr.org needs all CSS files to be minified and compressed as it can save up to 92.1 kB or 82% of the original size.
Number of requests can be reduced by 45 (49%)
92
47
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Planete Drupal Fr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
planete.drupalfr.org
327 ms
system.base.css
160 ms
system.menus.css
164 ms
system.messages.css
165 ms
system.theme.css
166 ms
book.css
167 ms
codefilter.css
233 ms
comment.css
238 ms
date.css
245 ms
field.css
245 ms
mollom.css
247 ms
node.css
246 ms
scald_file.css
311 ms
search.css
316 ms
forum.css
326 ms
views.css
326 ms
ctools.css
326 ms
boilerplate.css
327 ms
layout.css
390 ms
style.css
394 ms
blocks.css
408 ms
user.css
406 ms
pages.css
409 ms
js_UWQINlriydSoeSiGQxToOUdv493zEa7dpsXC1OtYlZU.js
577 ms
js_xnaB0jBYrGI0G159tJmr4dCKw1naro5R-LaIgsgzruY.js
468 ms
js_2cwCDxXxrfswfow3JZPU2QgYvBLlQn0JC2UWRC5gcLk.js
473 ms
js_ypPaO9eWjHoc7jTOSUIN4nUdjGQf8tXA0J8-SgtDJtY.js
487 ms
widgets.js
4 ms
analytics.js
42 ms
6opJ27r_Yv0
104 ms
Drupal-geoMapping_053.png
976 ms
migration_d8_0.jpg
600 ms
premiere-alpha-de-mon-module-de-pronostics-sous-drupal-8-mespronos.png
598 ms
feed.png
208 ms
Drupal-geoMapping_054.png
934 ms
Drupal-geoMapping_056.png
915 ms
Drupal-geoMapping_057.png
838 ms
Drupal-geoMapping_058.png
1121 ms
Drupal-geoMapping_059.png
953 ms
Drupal-geoMapping_060.png
1103 ms
Drupal-geoMapping_061.png
1003 ms
Drupal-geoMapping_062.png
1031 ms
Drupal-geoMapping_063.png
1138 ms
Drupal-geoMapping_001.png
1147 ms
Drupal-geoMapping_002.png
1092 ms
Drupal-geoMapping_003.png
1222 ms
Drupal-geoMapping_004.png
1270 ms
Drupal-geoMapping_005.png
1281 ms
Drupal-geoMapping_014.png
1213 ms
Drupal-geoMapping_016.png
1327 ms
Drupal-geoMapping_010.png
1235 ms
Drupal-geoMapping_008.png
1311 ms
Drupal-geoMapping_013.png
1323 ms
Drupal-geoMapping_009.png
1414 ms
cover.jpg
864 ms
section1-bg.gif
98 ms
logo.png
99 ms
logo_13.png
101 ms
logo_2014_bis_512.png
99 ms
drupalfr_user.png
98 ms
marker-2.gif
99 ms
74443_497368248487_4110950_n.jpg
203 ms
logo_6.png
201 ms
x-office-document.png
204 ms
paysage_wide.jpg
354 ms
yky-njwc.jpeg
205 ms
update_security01_0.png
358 ms
update_security02_0.png
457 ms
update_security03_1.png
381 ms
update_security04.png
380 ms
update_security05.png
458 ms
Cfijn4G6uWA
92 ms
LmYGd5FW1e8
92 ms
SWwzQGqgxJ0
93 ms
yuC_TOpbC0g
93 ms
search.png
351 ms
clients-bg.png
349 ms
collect
50 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
22 ms
arrows.png
264 ms
syndication
85 ms
599864995044790273
263 ms
proxy.jpg
24 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
2 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
4 ms
m9s8f16t4bzn9cfzyiuz_normal.png
46 ms
b3bf321228b1ea102c97aee8dfd99ff9_normal.png
44 ms
9wB8N-YG_normal.png
44 ms
hello4_normal.jpg
45 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
36 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
40 ms
proxy.jpg
4 ms
jot.html
2 ms
planete.drupalfr.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
[role] values are not valid
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
Form elements do not have associated labels
Links do not have a discernible name
planete.drupalfr.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
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
planete.drupalfr.org SEO score
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 Planete.drupalfr.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 Planete.drupalfr.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.
planete.drupalfr.org
Open Graph description is not detected on the main page of Planete Drupal Fr. 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: