4.5 sec in total
271 ms
3.9 sec
326 ms
Visit if-benin.com now to see the best up-to-date If Benin content for Benin and also check out these interesting facts you probably never knew about if-benin.com
Visit if-benin.comWe analyzed If-benin.com page load time and found that the first response time was 271 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 65% of websites can load faster.
if-benin.com performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value9.8 s
0/100
25%
Value6.5 s
39/100
10%
Value250 ms
84/100
30%
Value1.77
0/100
15%
Value10.1 s
26/100
10%
271 ms
1222 ms
266 ms
177 ms
208 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 44% of them (43 requests) were addressed to the original If-benin.com, 20% (19 requests) were made to Pbs.twimg.com and 10% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain If-benin.com.
Page size can be reduced by 596.3 kB (26%)
2.3 MB
1.7 MB
In fact, the total size of If-benin.com main page is 2.3 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 1.4 MB which makes up the majority of the site volume.
Potential reduce by 157.6 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 157.6 kB or 79% of the original size.
Potential reduce by 31.9 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. If Benin images are well optimized though.
Potential reduce by 406.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 406.9 kB or 66% of the original size.
Number of requests can be reduced by 37 (40%)
93
56
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of If Benin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
if-benin.com
271 ms
www.if-benin.com
1222 ms
base-cachekey-73567d86285590d99714e11be7b6b0f6.css
266 ms
resourceplone.app.jquerytools.dateinput-cachekey-60f4702ca1de9c2559350754dd335862.css
177 ms
resourcecollective.js.fancyboxjquery.fancybox-cachekey-215dab21b27808374c3d1c76a1b4898d.css
208 ms
resourceContentWellPortlets.stylesContentWellPortlets-cachekey-2b9bfe4cf59915034eaeb4997230a68b.css
192 ms
global.css
344 ms
minisite-cachekey-30de39feaff684e6839b06fa999a3bde.css
291 ms
ploneCustom-cachekey-ce2814c03b02d5213f0c09d308c4f5bf.css
275 ms
at-cachekey-b6cfeff8f6058f3525b32a22a21c5b8d.kss
279 ms
resourceplone.app.jquery-cachekey-ad4a33fe349255aded6d91b60cb6773c.js
545 ms
resourcedropdown-menu-cachekey-1fd17b96f3a22fa488a767af533fcb34.js
353 ms
ckeditor_vars-cachekey-36de54adafa50d78ef8bc1667a2a85a5.js
358 ms
jquery.galleriffic-cachekey-389065c5f21a433ce8152db1471e1809.js
369 ms
addthis_widget.js
9 ms
resourcejquery.google-analytics-cachekey-c2fe9a9af9fd90ac8324ba4c2aad5881.js
378 ms
++resource++collective.portletpage.css
113 ms
site-Plone.png
212 ms
body-suite.png
134 ms
body-motif.png
335 ms
benin1.jpg
544 ms
champ-recherche-suite.png
131 ms
bouton-recherche.png
130 ms
image_thumb
223 ms
image_thumb
231 ms
image_thumb
232 ms
image_thumb
232 ms
image_thumb
236 ms
image
330 ms
image
330 ms
champ-newsletter.png
329 ms
bouton-newsletter.png
330 ms
fond-sous-navigation.png
413 ms
puce-fleche-blanche-off.png
411 ms
calendrier-precedent.png
410 ms
calendrier-suivant.png
411 ms
sdk.js
57 ms
din-medium-webfont.woff
463 ms
dinboldtram-webfont.woff
653 ms
widgets.js
98 ms
300lo.json
50 ms
footer.png
617 ms
precedent-carousel.png
405 ms
suivant-carousel.png
417 ms
image_large
895 ms
sh.8e5f85691f9aaa082472a194.html
130 ms
196 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
186 ms
xd_arbiter.php
43 ms
xd_arbiter.php
112 ms
layers.e5ea973510bf60b3db41.js
40 ms
fleche-miniature-active.png
251 ms
syndication
109 ms
669882632470155264
184 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
29 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
78 ms
NDsUapkb_normal.jpg
147 ms
YgZtWHXK_normal.jpg
174 ms
CdmYTP_UAAIGvNX.jpg:small
228 ms
CdH3VaOW0AERgd2.jpg:small
277 ms
CdA5PKIXIAAnvqL.jpg:small
283 ms
Ccm8nizWAAAlJfv.jpg:small
300 ms
CcJvpbmUkAEKZYx.jpg:small
327 ms
Cb98wGVWwAENOiV.jpg:small
326 ms
CbkaPmSUYAAL0if.jpg:small
327 ms
Cb6Nyv-W0AAdeRm.jpg:small
329 ms
Cbge7wHUAAE9ors.jpg:small
341 ms
Ca6xrYfW4AACO2l.jpg:small
354 ms
Ca2I_aYXIAAdjNF.jpg:small
451 ms
CaXXzjzW0AQS-Fj.jpg:small
507 ms
CaW3jXsUEAAoc3v.jpg:small
748 ms
CZ55FNPUcAAGAcX.jpg:small
510 ms
CZzECncWcAAGfCE.jpg:small
517 ms
CZUODJ-WEAAlLqj.jpg:small
607 ms
CZKBzpDWkAAANWm.jpg:small
658 ms
jot
28 ms
ga.js
22 ms
__utm.gif
12 ms
image_large
664 ms
page.php
127 ms
ebiMDO3r-8l.css
28 ms
jGc-59L_9lo.css
49 ms
1kPfZUdGrka.js
66 ms
ri0J2Bo-htg.js
88 ms
Mpe38fuBVZ2.js
59 ms
n8qIhCw3vMx.js
65 ms
12510222_1104958289544930_2979502141818522073_n.jpg
51 ms
6347_514659121908186_872170568_n.jpg
21 ms
12687975_1963568963868644_1303360095127764315_n.jpg
18 ms
33792_1642539477790_4444482_n.jpg
22 ms
12313670_571556369662176_5918794346538723202_n.jpg
20 ms
12743577_10156620585215217_4356771924698091420_n.jpg
22 ms
65365_319762541471571_784785321_n.jpg
23 ms
wL6VQj7Ab77.png
14 ms
s7jcwEQH7Sx.png
14 ms
VXcANLwwL5J.js
6 ms
AmlxWlqMvlv.js
8 ms
if-benin.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
Form elements do not have associated labels
if-benin.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
if-benin.com 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise If-benin.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 If-benin.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.
if-benin.com
Open Graph description is not detected on the main page of If Benin. 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: