Tools & Wizards About Us
proximus11.be screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

proximus11.be

Le sport à la télé, en direct ou différé - Proximus Pickx

Page Load Speed

3.4 sec in total

First Response

384 ms

Resources Loaded

2.7 sec

Page Rendered

276 ms

proximus11.be screenshot

About Website

Visit proximus11.be now to see the best up-to-date Proximus 11 content for France and also check out these interesting facts you probably never knew about proximus11.be

Suivez toute l'actualité sportive et programmes télé sur Proximus Pickx : football, cyclisme, basket, hockey, auto-moto en direct ou jusqu’à 7 jours en replay.

Visit proximus11.be

Key Findings

We analyzed Proximus11.be page load time and found that the first response time was 384 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

proximus11.be performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.7 s

0/100

25%

SI (Speed Index)

Value13.8 s

1/100

10%

TBT (Total Blocking Time)

Value4,150 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.135

80/100

15%

TTI (Time to Interactive)

Value26.5 s

0/100

10%

Network Requests Diagram

proximus11.be

384 ms

www.proximus11.be

633 ms

minify.php

719 ms

minify.php

641 ms

minify.php

671 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 14% of them (2 requests) were addressed to the original Proximus11.be, 71% (10 requests) were made to Staticproximus11.be and 7% (1 request) were made to Common.staticskynet.be. The less responsive or slowest element that took the longest time to load (809 ms) relates to the external source Staticproximus11.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 232.2 kB (39%)

Content Size

601.6 kB

After Optimization

369.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-73%

Potential reduce by 17.0 kB

  • Original 23.3 kB
  • After minification 22.0 kB
  • After compression 6.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 17.0 kB or 73% of the original size.

Image Optimization

-3%

Potential reduce by 9.8 kB

  • Original 289.5 kB
  • After minification 279.7 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. Proximus 11 images are well optimized though.

JavaScript Optimization

-40%

Potential reduce by 34.5 kB

  • Original 86.0 kB
  • After minification 86.0 kB
  • After compression 51.5 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 34.5 kB or 40% of the original size.

CSS Optimization

-84%

Potential reduce by 170.8 kB

  • Original 202.7 kB
  • After minification 201.1 kB
  • After compression 31.9 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. Proximus11.be needs all CSS files to be minified and compressed as it can save up to 170.8 kB or 84% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

8

After Optimization

8

  • Images
  • JavaScript
  • CSS

The browser has sent 8 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Proximus 11. According to our analytics all requests are already optimized.

Network Requests Diagram

proximus11.be

proximus11.be

384 ms

www.proximus11.be

www.proximus11.be

633 ms

minify.php

minify.php

719 ms

minify.php

minify.php

641 ms

minify.php

minify.php

671 ms

jquery.min.js

jquery.min.js

30 ms

top-header-bg-lg.png

top-header-bg-lg.png

353 ms

logo-11.png

logo-11.png

91 ms

splash-desktop.jpg

splash-desktop.jpg

179 ms

foot.png

foot.png

573 ms

proximus-regular.woff

proximus-regular.woff

250 ms

proximus-bold.woff

proximus-bold.woff

286 ms

icomoon-ce.woff

icomoon-ce.woff

809 ms

proximus-light.woff

proximus-light.woff

228 ms

Accessibility Review

proximus11.be accessibility score

82

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

[aria-*] attributes do not match their roles

High

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

proximus11.be best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

proximus11.be SEO score

86

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

Document doesn't have a valid hreflang

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Proximus11.be can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed English language. Our system also found out that Proximus11.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

proximus11.be

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