11.4 sec in total
793 ms
7.9 sec
2.8 sec
Visit jazi.fr now to see the best up-to-date Jazi content and also check out these interesting facts you probably never knew about jazi.fr
Petites annonces gratuites en France - publier une annonce gratuitement et sans inscription
Visit jazi.frWe analyzed Jazi.fr page load time and found that the first response time was 793 ms and then it took 10.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
jazi.fr performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value7.1 s
5/100
25%
Value4.6 s
70/100
10%
Value630 ms
47/100
30%
Value0
100/100
15%
Value8.7 s
36/100
10%
793 ms
16 ms
407 ms
405 ms
753 ms
Our browser made a total of 132 requests to load all elements on the main page. We found that 33% of them (44 requests) were addressed to the original Jazi.fr, 17% (23 requests) were made to Google-analytics.com and 5% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Netdna.bootstrapcdn.com.
Page size can be reduced by 857.1 kB (59%)
1.4 MB
585.9 kB
In fact, the total size of Jazi.fr main page is 1.4 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. Javascripts take 943.0 kB which makes up the majority of the site volume.
Potential reduce by 214.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 36.0 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 214.1 kB or 82% of the original size.
Potential reduce by 32.4 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, Jazi needs image optimization as it can save up to 32.4 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 588.1 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 588.1 kB or 62% of the original size.
Potential reduce by 22.4 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. Jazi.fr needs all CSS files to be minified and compressed as it can save up to 22.4 kB or 82% of the original size.
Number of requests can be reduced by 67 (55%)
121
54
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jazi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
jazi.fr
793 ms
cnt.share.js
16 ms
jquery.ui.min.css
407 ms
style.css
405 ms
jquery.min.js
753 ms
jquery.noscript.js
406 ms
jquery.ui.min.js
691 ms
jquery.validate.min.js
508 ms
jquery.cookie.js
508 ms
addthis_widget.js
37 ms
adsbygoogle.js
31 ms
widget-53578d7ce4b0229ec5c040cb-7506989
27 ms
analytics.js
40 ms
background.jpg
393 ms
hit;jazi
541 ms
watch.js
3 ms
jazi.png
221 ms
pictures.png
220 ms
logo;jazi
509 ms
ec.js
107 ms
ca-pub-0229508946954791.js
508 ms
zrt_lookup.html
360 ms
show_ads_impl.js
203 ms
dots.png
190 ms
7428184.jpg
181 ms
7427816.jpg
173 ms
7427846.jpg
173 ms
7427793.jpg
165 ms
7427787.jpg
308 ms
7427167.jpg
303 ms
7424391.jpg
303 ms
7424397.jpg
301 ms
7423287.jpg
297 ms
7423277.jpg
292 ms
7414602.jpg
440 ms
7414600.jpg
434 ms
thumbnail.jpg
434 ms
collect
101 ms
collect
163 ms
collect
251 ms
collect
241 ms
collect
240 ms
collect
250 ms
collect
249 ms
collect
250 ms
collect
307 ms
collect
306 ms
collect
307 ms
collect
302 ms
collect
301 ms
collect
302 ms
7411732.jpg
305 ms
ads
357 ms
osd.js
209 ms
collect
206 ms
7405218.jpg
200 ms
ads
729 ms
hit;jazi
238 ms
collect
160 ms
7405051.jpg
193 ms
collect
113 ms
7402128.jpg
250 ms
collect
48 ms
7387528.jpg
185 ms
collect
35 ms
7384271.jpg
238 ms
collect
10 ms
7381995.jpg
544 ms
collect
8 ms
7378256.jpg
536 ms
7377185.jpg
557 ms
7374456.jpg
563 ms
7363366.jpg
561 ms
7359819.jpg
1102 ms
7358891.jpg
610 ms
7356063.jpg
730 ms
css
1000 ms
m_js_controller.js
1263 ms
abg.js
1363 ms
7354396.jpg
719 ms
7354064.jpg
930 ms
7344181.jpg
929 ms
context.js
1344 ms
print.css
95 ms
favicon
304 ms
googlelogo_color_112x36dp.png
422 ms
mobile_unified_button_icon_white.png
60 ms
context_static_r1084.js
699 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
536 ms
x_button_blue2.png
235 ms
s
262 ms
Rf2QnA3orEL6Eez56HJgxRuQ77qJyxbefnbSCBE0iUQ.js
46 ms
watch.js
2 ms
111595
118 ms
ads
473 ms
platform.js
1010 ms
widgetcode-53578d7ce4b0229ec5c040cb-7506989
382 ms
wave.png
410 ms
300lo.json
1317 ms
jquery.min.js
664 ms
font-awesome.css
1427 ms
sh.953eb77977227bfd253ee158.html
268 ms
favicon
638 ms
nessie_icon_tiamat_white.png
272 ms
push
764 ms
activeview
306 ms
cb=gapi.loaded_0
96 ms
cb=gapi.loaded_1
128 ms
community
226 ms
postmessageRelay
115 ms
rs=AGLTcCNTA9pvh235nEs1DeG2WRtEx845Qg
61 ms
rs=AGLTcCP9IczaT7Rf-UGgqDPBu0TrwouL5A
58 ms
rs=AGLTcCNLAXuCqJFn8F0ZObXr7m3vSbg1og
242 ms
photo.jpg
475 ms
badges-eaefc7099b8352c2d91a1a3d728dcac7.png
409 ms
1077434459-postmessagerelay.js
434 ms
rpc:shindig_random.js
315 ms
grlryt2bdKIyfMSOhzd1eA.woff
399 ms
d-QWLnp4didxos_6urzFtg.woff
487 ms
vxNK-E6B13CyehuDCmvQvw.woff
486 ms
pixel
258 ms
rs=AGLTcCNLAXuCqJFn8F0ZObXr7m3vSbg1og
97 ms
layers.486057f6e3ab422798c9.js
372 ms
rs=AGLTcCNLAXuCqJFn8F0ZObXr7m3vSbg1og
158 ms
cb=gapi.loaded_0
142 ms
image-7506989-10414582
614 ms
fontawesome-webfont.woff
391 ms
fr.js
117 ms
rimacoco.jpg
328 ms
fql
296 ms
shares.json
276 ms
views2.json
517 ms
jazi.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.
jazi.fr 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
jazi.fr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
N/A
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jazi.fr can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is French. Our system also found out that Jazi.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.
jazi.fr
Open Graph description is not detected on the main page of Jazi. 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: