4.4 sec in total
617 ms
3.4 sec
289 ms
Click here to check amazing OCH content. Otherwise, check out these important facts you probably never knew about och.fr
Nous sommes au service des personnes malades, handicapées, de leurs familles et de leurs amis.
Visit och.frWe analyzed Och.fr page load time and found that the first response time was 617 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
och.fr performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value8.2 s
2/100
25%
Value6.1 s
45/100
10%
Value0 ms
100/100
30%
Value0.001
100/100
15%
Value4.9 s
78/100
10%
617 ms
81 ms
157 ms
160 ms
160 ms
Our browser made a total of 134 requests to load all elements on the main page. We found that 76% of them (102 requests) were addressed to the original Och.fr, 7% (10 requests) were made to Static.xx.fbcdn.net and 4% (6 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Och.fr.
Page size can be reduced by 965.8 kB (34%)
2.8 MB
1.9 MB
In fact, the total size of Och.fr main page is 2.8 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 58.9 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 58.9 kB or 78% of the original size.
Potential reduce by 127.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. OCH images are well optimized though.
Potential reduce by 438.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 438.4 kB or 68% of the original size.
Potential reduce by 340.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. Och.fr needs all CSS files to be minified and compressed as it can save up to 340.5 kB or 83% of the original size.
Number of requests can be reduced by 59 (45%)
130
71
The browser has sent 130 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OCH. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
och.fr
617 ms
system.base.css
81 ms
system.menus.css
157 ms
system.messages.css
160 ms
system.theme.css
160 ms
shadowbox.css
162 ms
simplenews.css
164 ms
comment.css
165 ms
date.css
233 ms
datepicker.1.7.css
235 ms
field.css
237 ms
footer_sitemap.css
236 ms
node.css
242 ms
search.css
243 ms
user.css
308 ms
views.css
311 ms
ckeditor.css
313 ms
ctools.css
313 ms
textsize.css
319 ms
layout.css
320 ms
style.css
458 ms
colors.css
386 ms
print.css
390 ms
all.css
626 ms
jquery.js
643 ms
jquery.once.js
400 ms
drupal.js
464 ms
shadowbox.js
634 ms
shadowbox_auto.js
482 ms
fr_mxcth1yEhEti1WogFBdq_ltKu38t4kkIhqH6R6HdGmA.js
535 ms
jquery.textsize.js
543 ms
jquery.cookie.js
564 ms
googleanalytics.js
612 ms
jquery1.9.0.js
858 ms
jquery-ui-1.10.2.custom.min.js
663 ms
main.js
922 ms
jquery.cookie.js
702 ms
och.js
643 ms
analytics.js
6 ms
collect
13 ms
banniereecoute-conseil-home.jpg
749 ms
vn38GlwqXzw
161 ms
video_bouton.jpg
819 ms
intentions-de-priere.png
986 ms
couv_ol210.jpg
1215 ms
bloc_lourdes.gif
898 ms
RADIO.png
903 ms
TV.png
901 ms
MP3.png
910 ms
DOC.png
986 ms
rcf_logo_statut_quadri.png
1146 ms
logo_rnd.jpg
1313 ms
logo_kto.png
996 ms
banniere210.gif
1283 ms
bg-header-panel.png
128 ms
bg-panel-holder.jpg
102 ms
sprite.png
377 ms
a-plus.png
126 ms
a-moins.png
126 ms
fondation-och-logo.png
196 ms
bg-slogan.png
182 ms
banniere_home2.jpg
620 ms
menu-leaf.png
194 ms
menu-expanded.png
194 ms
bg-heading.png
376 ms
arcabas-noces-de-cana_0.jpg
628 ms
fotolia_103108921_xs.jpg
538 ms
5recouvrement.png
762 ms
conf-hibon-1.png
492 ms
affiche_40x60_jmj2016_x3_1.jpg
507 ms
img_6539.jpg
726 ms
mamans-rvb72.jpg
665 ms
bg-gallery-frame.png
617 ms
arcabas-noces-de-cana_0.jpg
698 ms
fotolia_103108921_xs.jpg
698 ms
5recouvrement.png
708 ms
conf-hibon-1.png
746 ms
affiche_40x60_jmj2016_x3_1.jpg
777 ms
img_6539.jpg
777 ms
mamans-rvb72.jpg
790 ms
btn-carrousel.png
802 ms
bg-heading-1.png
826 ms
sprite-2.png
841 ms
bg-title.gif
855 ms
hibon-9_mars-webdiff.jpg
857 ms
divider.gif
871 ms
affiche_veillee_de_priere_2016_recto.jpg
879 ms
_18z7783.jpg
903 ms
t_debonnaire_7777.jpg
923 ms
all.js
56 ms
mamans-rvb72.jpg
847 ms
droidsans-webfont.woff
841 ms
papa.jpg
855 ms
vieaffec-fotolia.jpg
856 ms
249 ms
mon_pere_ma_mere_-_2015.jpg
858 ms
xd_arbiter.php
23 ms
xd_arbiter.php
45 ms
www-embed-player-vflfNyN_r.css
55 ms
www-embed-player.js
82 ms
base.js
103 ms
marchi-steffens-rvb.jpg
830 ms
vanier.jpg
827 ms
bg-title-1.gif
829 ms
bg-title-2.png
847 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
78 ms
ad_status.js
70 ms
divider-1.gif
666 ms
bg-sub-menu.png
694 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
43 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
83 ms
bg-slider-1.gif
603 ms
bg-slider.gif
593 ms
bg-nav.png
563 ms
bg-drop.png
505 ms
separator.gif
503 ms
ping
45 ms
like_box.php
304 ms
ebiMDO3r-8l.css
54 ms
jGc-59L_9lo.css
61 ms
q68gy-v_YMF.js
70 ms
8w-1WQE8wsO.js
67 ms
0wM5s1Khldu.js
66 ms
1bNoFZUdlYZ.js
65 ms
11407032_993028110715590_7560988229051638890_n.jpg
52 ms
61483_520907317927674_379101767_n.jpg
18 ms
717_763197300491607_2756358878772013752_n.jpg
19 ms
1902063_1419299668371245_1675808146419102225_n.jpg
15 ms
402980_300420270077497_913635045_n.jpg
25 ms
1379841_10150004552801901_469209496895221757_n.jpg
14 ms
wL6VQj7Ab77.png
13 ms
s7jcwEQH7Sx.png
12 ms
I6-MnjEovm5.js
5 ms
pQrUxxo5oQp.js
4 ms
och.fr 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.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
och.fr 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
och.fr 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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Och.fr 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 Och.fr 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.
och.fr
Open Graph description is not detected on the main page of OCH. 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: