Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

liege.lameuse.be

Sudinfo.be, l'information en continu, actualités, politique, régions, sport, buzz.

Page Load Speed

4.9 sec in total

First Response

130 ms

Resources Loaded

3.2 sec

Page Rendered

1.5 sec

liege.lameuse.be screenshot

About Website

Welcome to liege.lameuse.be homepage info - get ready to check Liege Lameuse best content for Belgium right away, or after learning these important things about liege.lameuse.be

Le site du journal sudinfo.be, premier site d'information en Belgique francophone. Actualité en continu, régions, sport, buzz, vidéos, résultats sportifs, ...

Visit liege.lameuse.be

Key Findings

We analyzed Liege.lameuse.be page load time and found that the first response time was 130 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

liege.lameuse.be performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value2,800 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.065

97/100

15%

TTI (Time to Interactive)

Value17.7 s

4/100

10%

Network Requests Diagram

liege.lameuse.be

130 ms

liege

645 ms

css_27bc49b2c88af610138e690cf5274ed2_0.css

11 ms

css_dc9b7df1a3e3aa2d9b8718079697bab7_31.css

15 ms

psuniversaltag.js

308 ms

Our browser made a total of 115 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Liege.lameuse.be, 59% (68 requests) were made to Si.rosselcdn.net and 12% (14 requests) were made to Abs.proxistore.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Ls.hit.gemius.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 437.5 kB (44%)

Content Size

986.5 kB

After Optimization

549.0 kB

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

HTML Optimization

-79%

Potential reduce by 142.1 kB

  • Original 179.5 kB
  • After minification 170.6 kB
  • After compression 37.4 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 142.1 kB or 79% of the original size.

Image Optimization

-7%

Potential reduce by 30.1 kB

  • Original 421.3 kB
  • After minification 391.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. Liege Lameuse images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 149.4 kB

  • Original 241.1 kB
  • After minification 240.9 kB
  • After compression 91.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 149.4 kB or 62% of the original size.

CSS Optimization

-80%

Potential reduce by 115.9 kB

  • Original 144.5 kB
  • After minification 141.6 kB
  • After compression 28.6 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. Liege.lameuse.be needs all CSS files to be minified and compressed as it can save up to 115.9 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (24%)

Requests Now

112

After Optimization

85

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

Accessibility Review

liege.lameuse.be accessibility score

67

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

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

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

The document uses <meta http-equiv="refresh">

Best Practices

liege.lameuse.be 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

liege.lameuse.be SEO score

84

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

High

Tap targets are not sized appropriately

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 Liege.lameuse.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 Liege.lameuse.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

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