Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 84

    SEO

    Google-friendlier than
    60% of websites

sudpresse.be

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

Page Load Speed

4.3 sec in total

First Response

125 ms

Resources Loaded

2.9 sec

Page Rendered

1.3 sec

sudpresse.be screenshot

About Website

Click here to check amazing Sudpresse content for Belgium. Otherwise, check out these important facts you probably never knew about sudpresse.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 sudpresse.be

Key Findings

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

Performance Metrics

sudpresse.be performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value5,230 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value16.1 s

6/100

10%

Network Requests Diagram

www.sudpresse.be

125 ms

www.sudinfo.be

578 ms

css_a71d72d19e98177bfb7aaa9281d23e54_0.css

11 ms

css_dc9b7df1a3e3aa2d9b8718079697bab7_31.css

16 ms

js_1280a9822c76c84a237a8f940f4d67af_2.js

78 ms

Our browser made a total of 235 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Sudpresse.be, 47% (110 requests) were made to Si.rosselcdn.net and 13% (31 requests) were made to Football.sudpresse.be. The less responsive or slowest element that took the longest time to load (593 ms) relates to the external source Football.sudpresse.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (47%)

Content Size

3.3 MB

After Optimization

1.7 MB

In fact, the total size of Sudpresse.be main page is 3.3 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 287.8 kB

  • Original 364.9 kB
  • After minification 348.2 kB
  • After compression 77.1 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 287.8 kB or 79% of the original size.

Image Optimization

-7%

Potential reduce by 102.8 kB

  • Original 1.4 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. Sudpresse images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 515.5 kB

  • Original 729.0 kB
  • After minification 662.0 kB
  • After compression 213.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 515.5 kB or 71% of the original size.

CSS Optimization

-84%

Potential reduce by 624.4 kB

  • Original 740.9 kB
  • After minification 659.8 kB
  • After compression 116.5 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. Sudpresse.be needs all CSS files to be minified and compressed as it can save up to 624.4 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

215

After Optimization

156

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

Accessibility Review

sudpresse.be accessibility score

69

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

sudpresse.be best practices score

67

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

sudpresse.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 Sudpresse.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 Sudpresse.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 Sudpresse. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: