Tools & Wizards About Us
m.agropolis.fr screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

m.agropolis.fr

Agropolis International

Page Load Speed

3.5 sec in total

First Response

373 ms

Resources Loaded

2.7 sec

Page Rendered

402 ms

m.agropolis.fr screenshot

About Website

Visit m.agropolis.fr now to see the best up-to-date M Agropolis content for Burkina Faso and also check out these interesting facts you probably never knew about m.agropolis.fr

Visit m.agropolis.fr

Key Findings

We analyzed M.agropolis.fr page load time and found that the first response time was 373 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

m.agropolis.fr performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.9 s

0/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value920 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

Network Requests Diagram

m.agropolis.fr

373 ms

www.agropolis.fr

752 ms

bootstrap.min.css

452 ms

bootstrap.min.js

459 ms

slick.min.css

42 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original M.agropolis.fr, 78% (43 requests) were made to Agropolis.fr and 5% (3 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (824 ms) relates to the external source Agropolis.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 847.5 kB (42%)

Content Size

2.0 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of M.agropolis.fr main page is 2.0 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. 30% of websites need less resources to load. Images take 917.9 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 37.9 kB

  • Original 47.0 kB
  • After minification 33.7 kB
  • After compression 9.2 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 13.3 kB, which is 28% 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 37.9 kB or 81% of the original size.

Image Optimization

-4%

Potential reduce by 39.8 kB

  • Original 917.9 kB
  • After minification 878.1 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. M Agropolis images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 561.1 kB

  • Original 784.5 kB
  • After minification 710.4 kB
  • After compression 223.3 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 561.1 kB or 72% of the original size.

CSS Optimization

-84%

Potential reduce by 208.7 kB

  • Original 248.4 kB
  • After minification 230.6 kB
  • After compression 39.8 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. M.agropolis.fr needs all CSS files to be minified and compressed as it can save up to 208.7 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (62%)

Requests Now

53

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of M Agropolis. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

m.agropolis.fr

m.agropolis.fr

373 ms

www.agropolis.fr

www.agropolis.fr

752 ms

bootstrap.min.css

bootstrap.min.css

452 ms

bootstrap.min.js

bootstrap.min.js

459 ms

slick.min.css

slick.min.css

42 ms

slick-theme.css

slick-theme.css

54 ms

spip.css

spip.css

275 ms

lity.css

lity.css

278 ms

lity.mediabox.css

lity.mediabox.css

279 ms

lity.css

lity.css

283 ms

barre_outils.css

barre_outils.css

366 ms

cssdyn-css_barre_outils_icones_css-9ecedb72.css

cssdyn-css_barre_outils_icones_css-9ecedb72.css

370 ms

oembed.css

oembed.css

371 ms

jquery.js

jquery.js

824 ms

jquery.form.js

jquery.form.js

549 ms

jquery.autosave.js

jquery.autosave.js

462 ms

jquery.placeholder-label.js

jquery.placeholder-label.js

463 ms

ajaxCallback.js

ajaxCallback.js

543 ms

js.cookie.js

js.cookie.js

546 ms

lity.js

lity.js

644 ms

lity.mediabox.js

lity.mediabox.js

645 ms

spip.mediabox.js

spip.mediabox.js

640 ms

jquery.markitup_pour_spip.js

jquery.markitup_pour_spip.js

640 ms

jquery.previsu_spip.js

jquery.previsu_spip.js

640 ms

jsdyn-javascript_porte_plume_start_js-36896680.js

jsdyn-javascript_porte_plume_start_js-36896680.js

733 ms

main.css

main.css

734 ms

slick.css

slick.css

46 ms

css2

css2

34 ms

tarteaucitron.min.js

tarteaucitron.min.js

734 ms

slick.min.js

slick.min.js

14 ms

e572efb8ac.js

e572efb8ac.js

64 ms

counter.js

counter.js

40 ms

logo_agropolis.png

logo_agropolis.png

97 ms

hd_facebook-07.png

hd_facebook-07.png

96 ms

hd_linkedin-10.png

hd_linkedin-10.png

97 ms

instantane-5036f.png

instantane-5036f.png

817 ms

bt_bg_bleu_petit.png

bt_bg_bleu_petit.png

95 ms

img_agropolis.png

img_agropolis.png

97 ms

img_ambitions-15-15_1_.png

img_ambitions-15-15_1_.png

369 ms

bt_bg_clair_petit.png

bt_bg_clair_petit.png

190 ms

logo_region-24684.jpg

logo_region-24684.jpg

187 ms

logo_3m-2-f96ee.png

logo_3m-2-f96ee.png

191 ms

cirvert_l230px-3d166.png

cirvert_l230px-3d166.png

192 ms

inrae-2-4c9f1.png

inrae-2-4c9f1.png

281 ms

logo-ird-bf400.jpg

logo-ird-bf400.jpg

283 ms

mediaelementplayer.min.css

mediaelementplayer.min.css

279 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

458 ms

bg_bleu.png

bg_bleu.png

94 ms

analytics.js

analytics.js

23 ms

t.php

t.php

148 ms

collect

collect

12 ms

js

js

60 ms

mejs-controls.svg

mejs-controls.svg

95 ms

tarteaucitron.css

tarteaucitron.css

95 ms

tarteaucitron.en.js

tarteaucitron.en.js

95 ms

Accessibility Review

m.agropolis.fr accessibility score

71

Accessibility Issues

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

High

[aria-*] attributes do not have valid values

High

ARIA IDs are not unique

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

High

<object> elements do not have alternate text

Best Practices

m.agropolis.fr best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

m.agropolis.fr SEO score

67

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

High

Document uses plugins

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise M.agropolis.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 M.agropolis.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.

Social Sharing Optimization

m.agropolis.fr

Open Graph description is not detected on the main page of M Agropolis. 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: