Access enaos.be. www.enaos.be

name

value

score

weighting

FCP (First Contentful Paint)

Value8.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value9.7 s

10/100

10%

TBT (Total Blocking Time)

Value190 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0.127

82/100

15%

TTI (Time to Interactive)

Value10.7 s

22/100

10%

www.enaos.be

750 ms

js

63 ms

jquery-1.9.1.js

457 ms

jquery.fancybox.js

306 ms

BootStrap.min.js

283 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 96% of them (101 requests) were addressed to the original Enaos.be, 2% (2 requests) were made to Cdn.jsdelivr.net and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (750 ms) belongs to the original domain Enaos.be.

Content Size

793.8 kB

After Optimization

489.7 kB

In fact, the total size of Enaos.be main page is 793.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. 60% of websites need less resources to load. Images take 316.7 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 169.3 kB

Original 198.9 kB
After minification 197.7 kB
After compression 29.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. 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 169.3 kB or 85% of the original size.

Image Optimization

-14%

Potential reduce by 45.4 kB

Original 316.7 kB
After minification 271.3 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. Obviously, Enaos needs image optimization as it can save up to 45.4 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-30%

Potential reduce by 64.6 kB

Original 212.2 kB
After minification 205.2 kB
After compression 147.6 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 64.6 kB or 30% of the original size.

CSS Optimization

-38%

Potential reduce by 24.8 kB

Original 66.0 kB
After minification 46.6 kB
After compression 41.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. Enaos.be needs all CSS files to be minified and compressed as it can save up to 24.8 kB or 38% of the original size.

Requests Now

102

After Optimization

The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Enaos. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 8 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-*] attributes do not match their roles

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

Buttons do not have an accessible name

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 the interpretation of your content by users in different locales.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

Search Engine Optimization Advices

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

High

Links do not have descriptive text

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

High

Links are not crawlable

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

EN
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Enaos.be 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 Enaos.be 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

enaos.be

Open Graph data is detected on the main page of Enaos. 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

www.enaos.be

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

www.enaos.be

js

jquery-1.9.1.js

jquery.fancybox.js

BootStrap.min.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

www.enaos.be

js

jquery-1.9.1.js

jquery.fancybox.js

BootStrap.min.js

BootStrap.min.css

BootStrap-theme.min.css

jquery.fancybox.css

Visiteurs.min.css

WebResource.axd

Chargement.min.js

CompteurVisiteBloc.min.js

PartagePage.min.js

jqxcore.js

jqx.base.css

jqxcombobox.js

jqxbuttons.js

jqxlistbox.js

jqxscrollbar.js

jqxdata.js

jqx.classic.css

jqx.bootstrap.css

Polyfill.min.js

RechercheDynamiqueV3.min.js

RechercheDynamiqueVisiteur.min.js

BoutonUnClic.min.js

Personne-LienDynamique.min.js

cookieinfo.min.js

materialdesignicons.min.css

Enaos2_visiteurs.png

GB.Gif

BEfr.gif

FR.gif

BEnl.gif

GB.gif

ES.gif

Thumb-Photo.jpg

Thumb-Photo084622.jpg

Thumb-Photo104539.png

Thumb-Photo024308.jpg

Thumb-Photo092020.jpg

Thumb-Photo061034.jpg

Thumb-Photo104231.jpg