Report Summary

  • 85

    Performance

    Renders faster than
    89% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

essor.ml

Lessor.ml - Actualités et Infos au Mali et dans le monde

Page Load Speed

15.9 sec in total

First Response

2.4 sec

Resources Loaded

12.7 sec

Page Rendered

754 ms

essor.ml screenshot

About Website

Visit essor.ml now to see the best up-to-date Essor content for Mali and also check out these interesting facts you probably never knew about essor.ml

L'Essor - 1er site d'information. Les articles du journal et toute l'actualité en continu : International, Mali, Société, Economie, Culture, Environnement, Blogs ...

Visit essor.ml

Key Findings

We analyzed Essor.ml page load time and found that the first response time was 2.4 sec and then it took 13.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

essor.ml performance score

85

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

70/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value3.3 s

94/100

10%

Network Requests Diagram

www.essor.ml

2440 ms

wp-emoji-release.min.js

238 ms

theme-my-login.css

174 ms

dashicons.min.css

373 ms

jquery-ui-dialog.min.css

197 ms

Our browser made a total of 207 requests to load all elements on the main page. We found that 85% of them (176 requests) were addressed to the original Essor.ml, 6% (13 requests) were made to Scontent.xx.fbcdn.net and 5% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Essor.ml.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (39%)

Content Size

4.4 MB

After Optimization

2.7 MB

In fact, the total size of Essor.ml main page is 4.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. 70% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 272.3 kB

  • Original 304.5 kB
  • After minification 210.9 kB
  • After compression 32.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 93.5 kB, which is 31% 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 272.3 kB or 89% of the original size.

Image Optimization

-7%

Potential reduce by 175.5 kB

  • Original 2.4 MB
  • After minification 2.3 MB

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. Essor images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 578.4 kB

  • Original 838.8 kB
  • After minification 812.5 kB
  • After compression 260.5 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 578.4 kB or 69% of the original size.

CSS Optimization

-84%

Potential reduce by 665.1 kB

  • Original 793.1 kB
  • After minification 637.0 kB
  • After compression 128.0 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. Essor.ml needs all CSS files to be minified and compressed as it can save up to 665.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 53 (27%)

Requests Now

193

After Optimization

140

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

Accessibility Review

essor.ml accessibility score

64

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.

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

Document doesn't have a <title> element

High

Image elements do not have [alt] attributes

High

<object> elements do not have alternate text

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

essor.ml best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

essor.ml 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

Document doesn't have a <title> element

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

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 Essor.ml 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 Essor.ml 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

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