Access chuliege.be. CHU de Liège

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

23/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value200 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.181

67/100

15%

TTI (Time to Interactive)

Value15.2 s

7/100

10%

chuliege.be

272 ms

chu-de-liege

642 ms

csspacker.jsp

270 ms

csspacker.jsp

261 ms

main.css

352 ms

Our browser made a total of 126 requests to load all elements on the main page. We found that 99% of them (125 requests) were addressed to the original Chuliege.be, 1% (1 request) were made to Cdn.polyfill.io. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Cdn.polyfill.io.

Content Size

2.9 MB

After Optimization

2.3 MB

In fact, the total size of Chuliege.be main page is 2.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. 65% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 80.2 kB

Original 98.7 kB
After minification 87.6 kB
After compression 18.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 11.1 kB, which is 11% 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 80.2 kB or 81% of the original size.

Image Optimization

-11%

Potential reduce by 219.7 kB

Original 2.0 MB
After minification 1.8 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, CHU Liege needs image optimization as it can save up to 219.7 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-43%

Potential reduce by 310.4 kB

Original 725.6 kB
After minification 680.1 kB
After compression 415.2 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 310.4 kB or 43% of the original size.

CSS Optimization

-15%

Potential reduce by 5.1 kB

Original 35.2 kB
After minification 35.2 kB
After compression 30.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. Chuliege.be needs all CSS files to be minified and compressed as it can save up to 5.1 kB or 15% of the original size.

Requests Now

121

After Optimization

The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CHU Liege. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 86 to 1 for JavaScripts and from 5 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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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 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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

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

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 Chuliege.be 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 Chuliege.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

chuliege.be

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

Report Summary

Performance

Accessibility

Best Practices

SEO

CHU de Liège - Internet

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

chuliege.be

chu-de-liege

csspacker.jsp

csspacker.jsp

main.css

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

chuliege.be

chu-de-liege

csspacker.jsp

csspacker.jsp

main.css

fixInternetNew.css

polyfill.min.js

modernizr-custom.js

jquery.min.js

jalios-init.js

jquery-migrate.min.js

jquery-fix.js

elementQuery.js

jquery-ui.min.js

jquery-browser.js

imagesloaded.pkgd.js

moment.js

moment-timezone-with-data-1970-2030.js

jsonrpc.js

prototype1.7.3MR.js

history.adapter.jquery.js

history.js

util.js

channel.js

widget.js

jquery.ajaxQueue.js

jquery.console.js

jquery.idle-timer.js

jquery.cookie.js

jalios-properties-js.jsp

jalios-common.js

jalios-i18n-js.jsp

jalios-i18n.js

jalios-data-broker.js

jalios-data-toggle.js

jalios-sortable.js

jalios-sortable-portal.js

jalios-sortable-widget.js

jalios-tooltip.js

jalios-browser.js

jalios-submit.js

jalios-clickable.js

transition.js