4.6 sec in total
509 ms
3.7 sec
475 ms
Click here to check amazing ONDAR content for France. Otherwise, check out these important facts you probably never knew about ondar.fr
Découvrez les meilleures conseils et astuces pour améliorer votre vie quotidienne. Des bons plans voyages, des tuto et de la culture générale
Visit ondar.frWe analyzed Ondar.fr page load time and found that the first response time was 509 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
ondar.fr performance score
509 ms
21 ms
143 ms
174 ms
181 ms
Our browser made a total of 126 requests to load all elements on the main page. We found that 22% of them (28 requests) were addressed to the original Ondar.fr, 8% (10 requests) were made to Static.xx.fbcdn.net and 6% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (880 ms) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 1.5 MB (65%)
2.3 MB
797.7 kB
In fact, the total size of Ondar.fr 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. 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. Javascripts take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 163.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 163.7 kB or 78% of the original size.
Potential reduce by 5.6 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. ONDAR images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 68% of the original size.
Potential reduce by 182.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. Ondar.fr needs all CSS files to be minified and compressed as it can save up to 182.2 kB or 79% of the original size.
Number of requests can be reduced by 79 (65%)
121
42
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ONDAR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 53 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
www.ondar.fr
509 ms
webfont.js
21 ms
wp-emoji-release.min.js
143 ms
gdsr.css.php
174 ms
rating.css
181 ms
subscriptions.css
180 ms
widgets.css
188 ms
style.css
194 ms
sharing.css
223 ms
genericons.css
332 ms
colorbox.min.css
262 ms
jquery.js
356 ms
jquery-migrate.min.js
279 ms
gdsr.js
288 ms
graphene.js
302 ms
show_ads.js
10 ms
css
26 ms
addthis_widget.js
9 ms
output.css
293 ms
devicepx-jetpack.js
3 ms
gprofiles.js
57 ms
wpgroho.js
354 ms
jquery.colorbox.1.5.9-min.js
358 ms
sharing.js
359 ms
e-201611.js
7 ms
e-201611.js
23 ms
analytics.js
43 ms
x20u7ik
546 ms
x20u7il
457 ms
x20u7ig
440 ms
x20u7ii
465 ms
x20u7ij
446 ms
news-ondar.jpg
548 ms
sprite_master.png
112 ms
sprite_h.png
110 ms
Bruno-Guillon-2-jury-ONDAR-France-2.jpg
341 ms
load_small.png
111 ms
list-style-image.png
110 ms
Logo-ONDAR-2.jpg
389 ms
zrt_lookup.html
32 ms
show_ads_impl.js
48 ms
VqvVqv1mv0Gr1Gr9Frul7xuyp+V8XvqnTyb1UoNRm4Af+FsAGNAEuwCFBYsQEBjlmxRgYrWCGwEFlLsBRSWCGwgFkdsAYrXFhZsBQrAAAAAVLP0T8AAA==
14 ms
genericons-regular-webfont.woff
189 ms
collect
16 ms
ads
262 ms
osd.js
80 ms
ads
268 ms
widgets.js
63 ms
ads
248 ms
count.js
82 ms
g.gif
116 ms
ajax.php
540 ms
hovercard.css
51 ms
services.css
90 ms
fql.query
251 ms
fql.query
416 ms
fql.query
524 ms
fql.query
735 ms
fql.query
735 ms
fql.query
734 ms
300lo.json
60 ms
fr.js
19 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
95 ms
overlay.png
109 ms
likebox.php
454 ms
main.8bc0b69923.css
102 ms
jquery.min.js
76 ms
playerv5-embed.js.v5b530410decb4d5f9
113 ms
dmp.aa8c53dee4b01d3bb05b.js
139 ms
sh.8e5f85691f9aaa082472a194.html
57 ms
count-data.js
69 ms
m_js_controller.js
126 ms
abg.js
149 ms
s_0RpkkOZZhN_719439273.html
162 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.fr.html
29 ms
css
107 ms
info.json
318 ms
googlelogo_color_112x36dp.png
210 ms
nessie_icon_tiamat_white.png
44 ms
s
29 ms
x_button_blue2.png
171 ms
dvbs_src.js
189 ms
dvtp_src.js
257 ms
creative_add_on.js
497 ms
56493d9dd1e6df032cef.dmp.js
250 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
70 ms
verify.js
255 ms
hDvwL1_H7g-.css
463 ms
56WNbrUYLbL.css
465 ms
q68gy-v_YMF.js
674 ms
8w-1WQE8wsO.js
880 ms
0wM5s1Khldu.js
777 ms
1bNoFZUdlYZ.js
776 ms
a4bde6a98cb92777bc207e0c241317e6.gif
215 ms
bst2tv3.html
145 ms
jot
303 ms
pebed.dm.gg
469 ms
dvtp_src_internal26.js
46 ms
pebed.dm.gg
472 ms
layers.e5ea973510bf60b3db41.js
121 ms
pebed.dm.gg
456 ms
pebed.dm.gg
450 ms
pebed.dm.gg
447 ms
surly.js
246 ms
t2tv7.html
85 ms
visit.js
185 ms
10013937_422469824563732_459531041_n.jpg
210 ms
999012_291679054309477_626157045_n.png
242 ms
11226184_937026686342527_1367715181401869667_n.jpg
283 ms
11152681_706377142817819_3914817075399260761_n.jpg
322 ms
11949476_920288554732148_6512529102743168332_n.jpg
324 ms
12096416_10207560219581708_5684988198330399453_n.jpg
323 ms
1922071_10202515563723070_1065936695_n.jpg
323 ms
10365932_1544860919139646_1724466297509619627_n.jpg
321 ms
wL6VQj7Ab77.png
49 ms
s7jcwEQH7Sx.png
51 ms
ba.html
26 ms
4.gif
36 ms
avs5639.js
14 ms
2532.js
79 ms
event.jpg
44 ms
box_19_top-right.png
10 ms
ci.png
17 ms
I6-MnjEovm5.js
41 ms
pQrUxxo5oQp.js
81 ms
ui
33 ms
ondar.fr SEO score
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ondar.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 Ondar.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.
ondar.fr
Open Graph description is not detected on the main page of ONDAR. 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: