Tools & Wizards About Us
legizz.com screenshot

Report Summary

  • 88

    Performance

    Renders faster than
    90% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

legizz.com

Gilles Gissinger - Marketing Digital, productivité et gestion de projets.

Page Load Speed

4 sec in total

First Response

943 ms

Resources Loaded

2.2 sec

Page Rendered

796 ms

legizz.com screenshot

About Website

Visit legizz.com now to see the best up-to-date Legizz content and also check out these interesting facts you probably never knew about legizz.com

Blog professionnel de Gilles Gissinger - on y parle marketing digital, productivité et gestion de projet.

Visit legizz.com

Key Findings

We analyzed Legizz.com page load time and found that the first response time was 943 ms and then it took 3 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

legizz.com performance score

88

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

78/100

25%

SI (Speed Index)

Value3.9 s

82/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value4.2 s

86/100

10%

Network Requests Diagram

legizz.com

943 ms

wp-emoji-release.min.js

260 ms

styles.css

179 ms

checkbox.min.css

179 ms

genericons.css

274 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 48% of them (23 requests) were addressed to the original Legizz.com, 6% (3 requests) were made to S.gravatar.com and 4% (2 requests) were made to I0.wp.com. The less responsive or slowest element that took the longest time to load (943 ms) belongs to the original domain Legizz.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 687.4 kB (66%)

Content Size

1.0 MB

After Optimization

351.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Legizz.com main page is 1.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. 40% of websites need less resources to load. Javascripts take 498.2 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 37.1 kB

  • Original 53.4 kB
  • After minification 51.5 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 37.1 kB or 69% of the original size.

Image Optimization

-0%

Potential reduce by 390 B

  • Original 85.6 kB
  • After minification 85.2 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. Legizz images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 327.5 kB

  • Original 498.2 kB
  • After minification 470.4 kB
  • After compression 170.7 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 327.5 kB or 66% of the original size.

CSS Optimization

-80%

Potential reduce by 322.4 kB

  • Original 401.6 kB
  • After minification 380.2 kB
  • After compression 79.2 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. Legizz.com needs all CSS files to be minified and compressed as it can save up to 322.4 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (66%)

Requests Now

44

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Legizz. 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 12 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

legizz.com

legizz.com

943 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

260 ms

styles.css

styles.css

179 ms

checkbox.min.css

checkbox.min.css

179 ms

genericons.css

genericons.css

274 ms

nprogress.css

nprogress.css

186 ms

jetpack-sharing-enhancements.css

jetpack-sharing-enhancements.css

219 ms

style.css

style.css

290 ms

form.min.css

form.min.css

279 ms

jetpack.css

jetpack.css

400 ms

jquery.js

jquery.js

424 ms

jquery-migrate.min.js

jquery-migrate.min.js

369 ms

nprogress.js

nprogress.js

398 ms

enhanced-comment-form.js

enhanced-comment-form.js

397 ms

jquery.cycle.js

jquery.cycle.js

445 ms

slideshow-shortcode.js

slideshow-shortcode.js

415 ms

photon.js

photon.js

454 ms

jquery.form.min.js

jquery.form.min.js

462 ms

scripts.js

scripts.js

460 ms

devicepx-jetpack.js

devicepx-jetpack.js

3 ms

gprofiles.js

gprofiles.js

52 ms

wpgroho.js

wpgroho.js

460 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

462 ms

e-201611.js

e-201611.js

3 ms

style.css

style.css

368 ms

334 ms

wakeup-awesome.jpg

wakeup-awesome.jpg

742 ms

simple-smile.png

simple-smile.png

242 ms

legizz.png

legizz.png

470 ms

image.png

image.png

367 ms

image1.png

image1.png

548 ms

free-seo-report.jpg

free-seo-report.jpg

689 ms

EqgBCrMKdUg

EqgBCrMKdUg

200 ms

Genericons.svg

Genericons.svg

200 ms

8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=

8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=

108 ms

analytics.js

analytics.js

108 ms

1f609.png

1f609.png

112 ms

hovercard.css

hovercard.css

38 ms

services.css

services.css

64 ms

py0ASoupf10

py0ASoupf10

115 ms

g.gif

g.gif

18 ms

collect

collect

12 ms

www-embed-player-vflRGs1ko.css

www-embed-player-vflRGs1ko.css

60 ms

www-embed-player.js

www-embed-player.js

81 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

21 ms

ad_status.js

ad_status.js

23 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

63 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

65 ms

Accessibility Review

legizz.com accessibility score

74

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

[role] values are not valid

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

Tables and lists

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

Impact

Issue

High

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

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

legizz.com 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

legizz.com SEO score

100

Search Engine Optimization Advices

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 Legizz.com 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 Legizz.com 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

legizz.com

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