Tools & Wizards About Us
lezgo.io screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

lezgo.io

Lezgo

Page Load Speed

5.7 sec in total

First Response

272 ms

Resources Loaded

4.8 sec

Page Rendered

569 ms

lezgo.io screenshot

About Website

Click here to check amazing Lezgo content. Otherwise, check out these important facts you probably never knew about lezgo.io

Visit lezgo.io

Key Findings

We analyzed Lezgo.io page load time and found that the first response time was 272 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

lezgo.io performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value110 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

lezgo.io

272 ms

lezgo.io

534 ms

application-fe7db0ed843d4bf8f4448bbc3b2fc491e7e88d1f032cb13be199ee9ff3a9b30e.css

87 ms

es-module-shims.min-4ca9b3dd5e434131e3bb4b0c1d7dff3bfd4035672a5086deec6f73979a49be73.js

174 ms

bootstrap.min.css

36 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 84% of them (43 requests) were addressed to the original Lezgo.io, 6% (3 requests) were made to Cdn.jsdelivr.net and 4% (2 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Lezgo.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 485.9 kB (26%)

Content Size

1.9 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lezgo.io main page is 1.9 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. 45% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 27.0 kB

  • Original 33.9 kB
  • After minification 25.1 kB
  • After compression 6.9 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 8.8 kB, which is 26% 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 27.0 kB or 80% of the original size.

Image Optimization

-19%

Potential reduce by 311.3 kB

  • Original 1.7 MB
  • After minification 1.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. Obviously, Lezgo needs image optimization as it can save up to 311.3 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-55%

Potential reduce by 16.7 kB

  • Original 30.2 kB
  • After minification 27.1 kB
  • After compression 13.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 16.7 kB or 55% of the original size.

CSS Optimization

-79%

Potential reduce by 130.9 kB

  • Original 164.7 kB
  • After minification 108.4 kB
  • After compression 33.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. Lezgo.io needs all CSS files to be minified and compressed as it can save up to 130.9 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (39%)

Requests Now

46

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lezgo.io

lezgo.io

272 ms

lezgo.io

lezgo.io

534 ms

application-fe7db0ed843d4bf8f4448bbc3b2fc491e7e88d1f032cb13be199ee9ff3a9b30e.css

application-fe7db0ed843d4bf8f4448bbc3b2fc491e7e88d1f032cb13be199ee9ff3a9b30e.css

87 ms

es-module-shims.min-4ca9b3dd5e434131e3bb4b0c1d7dff3bfd4035672a5086deec6f73979a49be73.js

es-module-shims.min-4ca9b3dd5e434131e3bb4b0c1d7dff3bfd4035672a5086deec6f73979a49be73.js

174 ms

bootstrap.min.css

bootstrap.min.css

36 ms

css

css

61 ms

animate.min.css

animate.min.css

55 ms

aos.css

aos.css

59 ms

main.css

main.css

259 ms

utilities.css

utilities.css

259 ms

home.css

home.css

536 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

53 ms

popper.min.js

popper.min.js

44 ms

bootstrap.min.js

bootstrap.min.js

44 ms

aos.js

aos.js

65 ms

home.js

home.js

357 ms

logo.svg

logo.svg

88 ms

essential.svg

essential.svg

94 ms

header-logo.svg

header-logo.svg

92 ms

cross.svg

cross.svg

89 ms

google.svg

google.svg

180 ms

apple.svg

apple.svg

182 ms

vector.svg

vector.svg

171 ms

der.svg

der.svg

173 ms

institut.svg

institut.svg

537 ms

lux.svg

lux.svg

376 ms

usaid.svg

usaid.svg

514 ms

trade.svg

trade.svg

428 ms

attirer.svg

attirer.svg

713 ms

mesurer.svg

mesurer.svg

1786 ms

impacter.svg

impacter.svg

841 ms

underline.svg

underline.svg

523 ms

fil.png

fil.png

1109 ms

pilotage.png

pilotage.png

770 ms

bmc.png

bmc.png

631 ms

agenda.png

agenda.png

726 ms

gantt.png

gantt.png

1076 ms

finance.png

finance.png

811 ms

espace.png

espace.png

1111 ms

fonc-item-image.svg

fonc-item-image.svg

901 ms

carine.jpg

carine.jpg

935 ms

quote.svg

quote.svg

996 ms

mathieu.jpg

mathieu.jpg

1028 ms

valentin.jpg

valentin.jpg

1084 ms

fb.svg

fb.svg

1122 ms

insta.svg

insta.svg

1165 ms

twi.svg

twi.svg

1174 ms

in.svg

in.svg

1193 ms

Gilroy-Bold.ttf

Gilroy-Bold.ttf

1345 ms

Gilroy-Medium.ttf

Gilroy-Medium.ttf

1194 ms

Gilroy-Regular.ttf

Gilroy-Regular.ttf

1408 ms

Accessibility Review

lezgo.io accessibility score

71

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

Heading elements are not in a sequentially-descending order

Internationalization and localization

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

Impact

Issue

High

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

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

Best Practices

lezgo.io best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

lezgo.io SEO score

77

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lezgo.io 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 Lezgo.io main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

lezgo.io

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