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

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value18.2 s

0/100

25%

SI (Speed Index)

Value16.4 s

0/100

10%

TBT (Total Blocking Time)

Value17,900 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.052

99/100

15%

TTI (Time to Interactive)

Value33.4 s

0/100

10%

lessor.ml

248 ms

lessor.ml

1594 ms

js

148 ms

icons.css

636 ms

adsbygoogle.js

77 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 16% of them (15 requests) were addressed to the original Lessor.ml, 41% (38 requests) were made to Admin.journalessor.ml and 14% (13 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source Admin.journalessor.ml.

Content Size

5.0 MB

After Optimization

2.9 MB

In fact, the total size of Lessor.ml main page is 5.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. Only a small number of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 115.4 kB

Original 130.9 kB
After minification 79.7 kB
After compression 15.5 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 51.2 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 115.4 kB or 88% of the original size.

Image Optimization

-23%

Potential reduce by 619.0 kB

Original 2.7 MB
After minification 2.1 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. Obviously, Lessor needs image optimization as it can save up to 619.0 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-19%

Potential reduce by 105.8 kB

Original 543.9 kB
After minification 543.9 kB
After compression 438.0 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 105.8 kB or 19% of the original size.

CSS Optimization

-77%

Potential reduce by 1.3 MB

Original 1.7 MB
After minification 1.6 MB
After compression 388.1 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. Lessor.ml needs all CSS files to be minified and compressed as it can save up to 1.3 MB or 77% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

[aria-hidden="true"] elements contain focusable descendents

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

FR
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lessor.ml can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lessor.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

lessor.ml

Open Graph data is detected on the main page of Lessor. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

Report Summary

Performance

Accessibility

Best Practices

SEO

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

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

lessor.ml

lessor.ml

js

icons.css

adsbygoogle.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

lessor.ml

lessor.ml

js

icons.css

adsbygoogle.js

article.css

home.css

slider.css

splide.min.css

sweetalert2@8

paper.svg

font-awesome.min.css

bootstrap.bundle.min.js

jquery-3.6.0.min.js

splide.min.js

common.bundle.js

visibilityChange.js

imgSlider.js

accounts.js

jquery.min.js

1728230372.jpg

BPWoqLVL4Lo

pyY5UIboZuo

Rum2JjYzPnw

bOKTJG1jYjc

18fcL-oLXM8

1641550401.jpg

1728230140.jpg

1728230063.jpg

1728229973.jpg

1728229909.jpg

1720962687.jpg

1720548863.jpg

1720548137.jpg

1720543885.jpg

1720114768.jpg

1728229826.jpg

1728168475.jpg

1728168008.jpg

1727890215.jpg

1727801227.jpg

1728231324.jpg

1728231126.jpg