Tools & Wizards About Us
agrex.mu screenshot

Report Summary

  • 62

    Performance

    Renders faster than
    76% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

agrex.mu

Agrex Limited – Value added agricultural supplies

Page Load Speed

8 sec in total

First Response

387 ms

Resources Loaded

7.4 sec

Page Rendered

259 ms

agrex.mu screenshot

About Website

Click here to check amazing Agrex content. Otherwise, check out these important facts you probably never knew about agrex.mu

Agrex is a subsidiary company of ENL Agri Limited. We bring value added agricultural intrants and equipment to the Mauritian growers who believe in quality and innovation.

Visit agrex.mu

Key Findings

We analyzed Agrex.mu page load time and found that the first response time was 387 ms and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

agrex.mu performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

42/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.141

78/100

15%

TTI (Time to Interactive)

Value7.4 s

49/100

10%

Network Requests Diagram

agrex.mu

387 ms

agrex

3706 ms

global.css

133 ms

media.css

201 ms

jquery-1.11.3.min.js

270 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Agrex.mu, 78% (36 requests) were made to Enl.mu and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source Enl.mu.

Page Optimization Overview & Recommendations

Page size can be reduced by 167.3 kB (23%)

Content Size

732.8 kB

After Optimization

565.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Agrex.mu main page is 732.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 415.6 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 145.1 kB

  • Original 161.4 kB
  • After minification 98.7 kB
  • After compression 16.3 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 62.7 kB, which is 39% 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 145.1 kB or 90% of the original size.

Image Optimization

-3%

Potential reduce by 11.7 kB

  • Original 415.6 kB
  • After minification 403.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. Agrex images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 3.0 kB

  • Original 106.8 kB
  • After minification 106.8 kB
  • After compression 103.8 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. This website has mostly compressed JavaScripts.

CSS Optimization

-15%

Potential reduce by 7.5 kB

  • Original 49.0 kB
  • After minification 49.0 kB
  • After compression 41.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. Agrex.mu needs all CSS files to be minified and compressed as it can save up to 7.5 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (28%)

Requests Now

43

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

agrex.mu

agrex.mu

387 ms

agrex

agrex

3706 ms

global.css

global.css

133 ms

media.css

media.css

201 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

270 ms

jquery.cookieBar.js

jquery.cookieBar.js

281 ms

cookieBar.css

cookieBar.css

2509 ms

copypastesubscribeformlogic.js

copypastesubscribeformlogic.js

11 ms

plugins.js

plugins.js

283 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

219 ms

custom.js

custom.js

219 ms

waypoints.min.js

waypoints.min.js

282 ms

jquery.counterup.min.js

jquery.counterup.min.js

284 ms

analytics.js

analytics.js

211 ms

icn-btn-brands.svg

icn-btn-brands.svg

310 ms

icn-btn-magazine.svg

icn-btn-magazine.svg

312 ms

curve.svg

curve.svg

311 ms

logo.svg

logo.svg

310 ms

cleanup-day.jpg

cleanup-day.jpg

321 ms

enl-foundation-porlwi.jpg

enl-foundation-porlwi.jpg

310 ms

about-rogers-foundation.jpg

about-rogers-foundation.jpg

414 ms

enlighten_logo.svg

enlighten_logo.svg

404 ms

jobs.jpg

jobs.jpg

445 ms

jobs1.jpg

jobs1.jpg

455 ms

agrex.jpg

agrex.jpg

456 ms

alban-de-speville.jpg

alban-de-speville.jpg

406 ms

field-good.png

field-good.png

453 ms

field-good.jpg

field-good.jpg

466 ms

diversey.jpg

diversey.jpg

482 ms

dsc_0150.jpg

dsc_0150.jpg

520 ms

whatsapp-image-2020-04-26-at-145518.jpeg

whatsapp-image-2020-04-26-at-145518.jpeg

531 ms

share.svg

share.svg

530 ms

s_facebook.svg

s_facebook.svg

529 ms

s_twitter.svg

s_twitter.svg

536 ms

s_linkdin.svg

s_linkdin.svg

553 ms

dsc_0126.jpg

dsc_0126.jpg

593 ms

whatsapp-image-2020-04-08-at-122444.jpeg

whatsapp-image-2020-04-08-at-122444.jpeg

603 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

553 ms

courbe-search.svg

courbe-search.svg

475 ms

www-widgetapi.js

www-widgetapi.js

175 ms

fbevents.js

fbevents.js

176 ms

insight.min.js

insight.min.js

193 ms

collect

collect

36 ms

1880948528642477

1880948528642477

38 ms

collect

collect

31 ms

15 ms

Accessibility Review

agrex.mu accessibility score

57

Accessibility Issues

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

agrex.mu best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

agrex.mu SEO score

90

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Agrex.mu can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Agrex.mu 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

agrex.mu

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