Proximus - Proximus.be

Overview

Snoop Summary for proximus.be

This is a free and comprehensive report about proximus.be. The domain proximus.be is currently hosted on a server located in Belgium with the IP address 195.13.15.25, where EUR is the local currency and the local language is German. Our records indicate that proximus.be is owned/operated by Proximus NV/SA. Proximus.be is expected to earn an estimated $143 USD per day from advertising revenue. The sale of proximus.be would possibly be worth $104,548 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Proximus.be receives an estimated 33,863 unique visitors every day - a massive amount of traffic! This report was last updated 27th May, 2021.

About proximus.be

Site Preview:
Title:	Proximus
Description:	Proximus offers you the best quality network and wide mobile coverage within Belgium. You’ll also benefit from a top-quality 24/7 service!
Keywords and Tags:	internet services, popular
Related Terms:
Fav Icon:
Age:	Over 27 years old
Domain Created:	5th July, 1996
Domain Updated:
Domain Expires:

Review

Snoop Score

4/5 (Excellent!)

Valuation

$104,548 USD

Note: All valuation figures are estimates.

Popularity

High

Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank:	22,543
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority:	0
Moz Page Authority:	0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors:	33,863
Monthly Visitors:	1,030,683
Yearly Visitors:	12,359,995

Note: All visitors figures are estimates.

Visitors By Country

Revenue

Daily Revenue:	$143 USD
Monthly Revenue:	$4,359 USD
Yearly Revenue:	$52,269 USD

Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top Ranking Keywords (US)

Domain Analysis

	Value	Length
Domain:	proximus.be	11
Domain Name:	proximus	8
Extension (TLD):	be	2

Page Speed Analysis

Average Load Time:	2.38 seconds
Load Time Comparison:	Faster than 33% of sites

Avg. (All Categories)

Performance

Accessibility

Best Practices

SEO

Progressive Web App

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

URL: https://www.proximus.be/en/personal/

Updated: 27th May, 2021

1.62 seconds

First Contentful Paint (FCP)

53%

37%

10%

0.02 seconds

First Input Delay (FID)

92%

4%

Simulate loading on desktop

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for proximus.be. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.7 s
The time taken for the first image or text on the page to be rendered.

Time to Interactive — 1.6 s
The time taken for the page to become fully interactive.

Total Blocking Time — 90 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 1.5 s
The time taken for the page's main thread to be quiet enough to handle input.

First Meaningful Paint — 0.7 s
The time taken for the primary content of the page to be rendered.

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive proximus.be as laggy when the latency is higher than 0.05 seconds.

Network Requests
Below is a list of network requests that were made during page load.

URL	Protocol	Start Time (Ms)	End Time (Ms)	Transfer Size (Bytes)	Resource Size (Bytes)	Status Code	MIME Type	Resource Type
http://proximus.be/	http/1.1	0	293.88599982485	277	0	301	text/html
https://www.proximus.be/	http/1.1	294.29399967194	1091.768999584	258	0	302
https://www.proximus.be/en/personal/?	http/1.1	1092.3049999401	1883.6779999547	40048	217126	200	text/html	Document
https://www.proximus.be/resources/cdn/brand/fonts/Proximus-Regular.woff2	http/1.1	1898.1009996496	2730.1629995927	18255	17768	200	application/font-woff2	Font
https://www.proximus.be/resources/cdn/brand/fonts/Proximus-Bold.woff2	http/1.1	1898.3759996481	2733.0089998432	18647	18160	200	application/font-woff2	Font
https://www.proximus.be/resources/cdn/brand/fonts/Proximus-Light.woff2	http/1.1	1898.6199996434	2418.6759996228	21617	21128	200	application/font-woff2	Font
https://www.proximus.be/resources/cdn/brand/fonts/Proximus-ExtraB.woff2	http/1.1	1898.8949996419	2509.9449995905	20855	20368	200	application/font-woff2	Font
https://www.proximus.be/resources/cdn/brand/fonts/PxIcon.woff2?v=3.2.1.2.98.2	http/1.1	1899.1099996492	2924.5839999057	71755	71268	200	application/font-woff2	Font
https://www.proximus.be/.resources/cdn/cis/css/iportal-all-css-pack~2019-04-11-12-47-03-619~cache.css	http/1.1	1901.9120000303	3305.430999957	147949	1148626	200	text/css	Stylesheet
https://www.proximus.be/.resources/cdn/webcomponents/packs/iportal-optimized-pack.js	http/1.1	1911.5309999324	3441.397999879	325188	1050832	200	application/javascript	Script
	data	3376.0949997231	3376.2969998643	0	4906	200	image/png	Image
	data	3376.6199997626	3376.739999745	0	4072	200	image/png	Image
	data	3376.9299997948	3376.9879997708	0	2014	200	image/jpeg	Image
	data	3377.1609999239	3377.1909996867	0	42	200	image/gif	Image
	data	3380.6539997458	3380.7129999623	0	88	200	image/svg+xml	Image
https://www.proximus.be/dam/jcr:a0b34927-c51c-4b04-a88b-1de2bfb05c47/cdn/sites/iportal/images/content-header/res/epic-combo-perso-tb-1904/epic-combo-perso-tb-1904-l-en~2019-03-28-16-09-06~cache.jpg	http/1.1	3392.9369999096	3916.5909998119	46527	46196	200	image/jpeg	Image
	data	3395.8979998715	3395.9659999236	0	418	200	image/svg+xml	Image
https://www.proximus.be/resources/cdn/brand/fonts/PxIcon.woff2?v=3.2.1.2.115.0	http/1.1	3407.1319997311	3998.7019998953	71665	71268	200	application/font-woff2	Font

Show Details

Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.

Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.

Tasks
Below is a list of the top-level main thread tasks that executed during page load.

Start Time (Ms)	End Time (Ms)
1915.479	8.842
3337.979	39.656
3377.65	20.338
3399.219	10.662
3415.306	70.209
3491.483	24.725
3547.146	350.234
4028.231	14.214

Show Details

Diagnostics
Below is a collection of useful page vitals.
View Data

Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Proximus.be should consider serving more appropriate-sized images.

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Proximus.be should consider lazy-loading offscreen and hidden images.

Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Proximus.be should consider minifying CSS files.

Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Proximus.be should consider minifying JS files.

Remove unused CSS — Potential savings of 138 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Proximus.be should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.

URL	Transfer Size (Bytes)	Potential Savings (Bytes)
https://www.proximus.be/.resources/cdn/cis/css/iportal-all-css-pack~2019-04-11-12-47-03-619~cache.css	147949	141382

Show Details

Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.

Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.

Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.

Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.

Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.

URL	Potential Savings (Bytes)
https://www.proximus.be/.resources/cdn/webcomponents/packs/iportal-optimized-pack.js	52

Show Details

Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

URL	Potential Savings (Ms)
https://www.proximus.be/dam/jcr:a0b34927-c51c-4b04-a88b-1de2bfb05c47/cdn/sites/iportal/images/content-header/res/epic-combo-perso-tb-1904/epic-combo-perso-tb-1904-l-en~2019-03-28-16-09-06~cache.jpg	0

Show Details

Diagnostics

Avoids enormous network payloads — Total size was 765 KiB
Large network payloads can cost users money and are linked to long load times.

URL	Transfer Size (Bytes)
https://www.proximus.be/.resources/cdn/webcomponents/packs/iportal-optimized-pack.js	325188
https://www.proximus.be/.resources/cdn/cis/css/iportal-all-css-pack~2019-04-11-12-47-03-619~cache.css	147949
https://www.proximus.be/resources/cdn/brand/fonts/PxIcon.woff2?v=3.2.1.2.98.2	71755
https://www.proximus.be/resources/cdn/brand/fonts/PxIcon.woff2?v=3.2.1.2.115.0	71665
https://www.proximus.be/dam/jcr:a0b34927-c51c-4b04-a88b-1de2bfb05c47/cdn/sites/iportal/images/content-header/res/epic-combo-perso-tb-1904/epic-combo-perso-tb-1904-l-en~2019-03-28-16-09-06~cache.jpg	46527
https://www.proximus.be/en/personal/?	40048
https://www.proximus.be/resources/cdn/brand/fonts/Proximus-Light.woff2	21617
https://www.proximus.be/resources/cdn/brand/fonts/Proximus-ExtraB.woff2	20855
https://www.proximus.be/resources/cdn/brand/fonts/Proximus-Bold.woff2	18647
https://www.proximus.be/resources/cdn/brand/fonts/Proximus-Regular.woff2	18255

Show Details

Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Proximus.be should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.

JavaScript execution time — 0.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

URL	Total CPU Time (Ms)	Script Evaluation (Ms)	Script Parse (Ms)
https://www.proximus.be/.resources/cdn/webcomponents/packs/iportal-optimized-pack.js	361.113	238.317	22.017
https://www.proximus.be/en/personal/?	162.34	18.082	3.422

Show Details

Minimizes main-thread work — 0.6 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

Category	Time Spent (Ms)
Script Evaluation	257.495
Style & Layout	167.385
Other	70.798
Parse HTML & CSS	47.183
Script Parsing & Compilation	25.567
Rendering	22.555
Garbage Collection	6.663

Show Details

Keep request counts low and transfer sizes small — 12 requests • 765 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.

Resource Type	Requests	Transfer Size (Bytes)
Total	12	783041
Script	1	325188
Font	6	222794
Stylesheet	1	147949
Image	1	46527
Document	1	40048
Other	2	535
Media	0	0
Third-party	0	0

Show Details

Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.

Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).

Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.

Element
epic combo At home & on the go I go for it € 59 /month during 6 months

Show Details

Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.

Element	CLS Contribution
Contact Webmail EN	0.00013295152935753
EN	2.0670909158061E-5
i	1.6278340961973E-5
i	1.6278340961973E-5
i	1.6278340961973E-5

Show Details

Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.

Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.

Avoid long main-thread tasks — 1 long task found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.

URL	Start Time (Ms)	Duration (Ms)
https://www.proximus.be/.resources/cdn/webcomponents/packs/iportal-optimized-pack.js	1500	175

Show Details

Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.

Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Largest Contentful Paint — 1.6 s
The timing of the largest text or image that is painted.

Other

Max Potential First Input Delay — 180 ms
Users could experience a delay when interacting with the page.

Opportunities

Eliminate render-blocking resources — Potential savings of 180 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Proximus.be should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.

URL	Transfer Size (Bytes)	Potential Savings (Ms)
https://www.proximus.be/.resources/cdn/cis/css/iportal-all-css-pack~2019-04-11-12-47-03-619~cache.css	147949	190

Show Details

Remove unused JavaScript — Potential savings of 211 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.

URL	Transfer Size (Bytes)	Potential Savings (Bytes)
https://www.proximus.be/.resources/cdn/webcomponents/packs/iportal-optimized-pack.js	325188	215590

Show Details

Avoid multiple page redirects — Potential savings of 420 ms
Redirects can cause additional delays before the page can begin loading. Proximus.be should avoid multiple or unnecessary page redirects.

URL	Time Spent (Ms)
http://proximus.be/	190
https://www.proximus.be/	230
https://www.proximus.be/en/personal/?	0

Show Details

Preload key requests — Potential savings of 200 ms
Key requests can be preloaded by using '<link rel=preload>'. Proximus.be should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.

URL	Potential Savings (Ms)
https://www.proximus.be/resources/cdn/brand/fonts/PxIcon.woff2?v=3.2.1.2.115.0	200

Show Details

Diagnostics

Serve static assets with an efficient cache policy — 1 resource found
Proximus.be can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.

URL	Cache TTL (Ms)	Transfer Size (Bytes)
https://www.proximus.be/.resources/cdn/webcomponents/packs/iportal-optimized-pack.js	86400000	325188

Show Details

Avoid an excessive DOM size — 1,058 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.

Statistic	Element	Value
Total DOM Elements		1058
Maximum DOM Depth	(Inte…	20
Maximum Child Elements	Personal Business Large companies Contact Webmail EN Products Discover Support …	26

Show Details

Metrics

Speed Index — 2.6 s
The time taken for the page contents to be visibly populated.

Opportunities

Reduce initial server response time — Root document took 790 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.

URL	Time Spent (Ms)
https://www.proximus.be/en/personal/?	792.37

Show Details

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.

URL	Potential Savings (Ms)
https://www.proximus.be/resources/cdn/brand/fonts/PxIcon.woff2?v=3.2.1.2.115.0	591.57000016421

Show Details

Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

URL	Failing Elements
	Proximus home
	Huawei Mate 20 Lite
	Samsung Galaxy A7
	Apple Iphone 6S
	MyProximus application
	Proximus TV app
	Proximus 11 application
	Proximus Wi-Fi Hotspots app
	Proximus Cloud application
	img

Show Details

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of proximus.be. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.

The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.

`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.

No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.

`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.

`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.

ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.

ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.

Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.

`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.

`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.

ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.

ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.

`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.

ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.

No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.

`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.

Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.

`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.

Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.

`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.

Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.

Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.

List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.

Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.

`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.

`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Proximus.be may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.

Failing Elements
combo
Pack with endless data for your apps, internet at home and TV via app

Show Details

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.

Failing Elements
At home & on the go
Contact us

Show Details

Names and labels

Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Failing Elements
a
a
a
a
img

Show Details

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.

Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.

Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.

The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.

User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.

Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.

Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.

Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.

Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.

HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that proximus.be should incorporate. This includes practices such as protecting pages with HTTPS.

Passing (14)
Failing (4)

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.

Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.

Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Avoids Application Cache
Application cache is deprecated and is no longer recommended.

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.

Name	Version
jQuery	1.11.1
Modernizr	2.7.1
Lo-Dash	4.17.10
AngularJS	1.6.7
Hammer.js	2.0.4

Show Details

Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.

No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.

No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.

Insecure URL	Request Resolution
http://proximus.be/	Allowed

Show Details

Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Failing Anchors
Sports
Proximus TV

a
a
a
Consult the shopmag
Forum
Your Premium Club points
Carrier & Wholesale Solutions
Proximus Group
Jobs

Show Details

Includes front-end JavaScript libraries with known security vulnerabilities — 16 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Library Version	Vulnerability Count	Highest Severity
SHOW DETAILS	4	Medium
SHOW DETAILS	8	High
SHOW DETAILS	4	High

Show Details

Audits

Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.

URL	Map URL
https://www.proximus.be/.resources/cdn/webcomponents/packs/iportal-optimized-pack.js	https://www.proximus.be/.resources/cdn/webcomponents/packs/system.js.map

Show Details

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for proximus.be. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of proximus.be on mobile screens.

Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.

Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.

Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.

Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.

Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.

robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Links do not have descriptive text — 4 links found
Make use of descriptive link text to assist search engines in understanding the content.

Link destination	Link Text
https://www.proximus.be/support/en/id_scatr_tv/personal/support/television.html	More
https://www.proximus.be/support/en/id_scatr_internet/personal/support/internet.html	More
https://www.proximus.be/support/en/id_scatr_call/personal/support/mobile-telephony.html	More
https://www.proximus.be/support/en/id_scatr_customer_zone/personal/support/myproximus-and-billing.html	More

Show Details

Document doesn't have a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.

Show Details

Document does not have a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.

Crawling and Indexing

Page is blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Blocking Directive Source
SHOW DETAILS

Show Details

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of proximus.be. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Registers a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.

Configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data

Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of proximus.be on mobile screens.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.

Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.

Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.

Avg. (All Categories)

Performance

Accessibility

Best Practices

SEO

Progressive Web App

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

URL: https://www.proximus.be/en/personal/

Updated: 27th May, 2021

2.76 seconds

First Contentful Paint (FCP)

16%

64%

20%

0.09 seconds

First Input Delay (FID)

76%

12%

Simulate loading on mobile

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for proximus.be. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Proximus.be should consider serving more appropriate-sized images.

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Proximus.be should consider lazy-loading offscreen and hidden images.

Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Proximus.be should consider minifying CSS files.

Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Proximus.be should consider minifying JS files.

Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.

Serve images in next-gen formats — Potential savings of 15 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.

URL	Resource Size (Bytes)	Potential Savings (Bytes)
https://www.proximus.be/dam/jcr:cfd06ea2-3187-4c85-96de-de49f3bb5663/cdn/sites/iportal/images/content-header/res/epic-combo-perso-tb-1904/epic-combo-perso-tb-1904-s-en~2019-03-28-16-14-27~cache.jpg	46357	14997

Show Details

Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.

Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.

Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.

URL	Potential Savings (Bytes)
https://www.proximus.be/.resources/cdn/webcomponents/packs/iportal-optimized-pack.js	52

Show Details

Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

URL	Potential Savings (Ms)
https://www.proximus.be/dam/jcr:cfd06ea2-3187-4c85-96de-de49f3bb5663/cdn/sites/iportal/images/content-header/res/epic-combo-perso-tb-1904/epic-combo-perso-tb-1904-s-en~2019-03-28-16-14-27~cache.jpg	0

Show Details

Diagnostics

Avoids enormous network payloads — Total size was 765 KiB
Large network payloads can cost users money and are linked to long load times.

URL	Transfer Size (Bytes)
https://www.proximus.be/.resources/cdn/webcomponents/packs/iportal-optimized-pack.js	325188
https://www.proximus.be/.resources/cdn/cis/css/iportal-all-css-pack~2019-04-11-12-47-03-619~cache.css	147951
https://www.proximus.be/resources/cdn/brand/fonts/PxIcon.woff2?v=3.2.1.2.98.2	71757
https://www.proximus.be/resources/cdn/brand/fonts/PxIcon.woff2?v=3.2.1.2.115.0	71666
https://www.proximus.be/dam/jcr:cfd06ea2-3187-4c85-96de-de49f3bb5663/cdn/sites/iportal/images/content-header/res/epic-combo-perso-tb-1904/epic-combo-perso-tb-1904-s-en~2019-03-28-16-14-27~cache.jpg	46689
https://www.proximus.be/en/personal/?	40046
https://www.proximus.be/resources/cdn/brand/fonts/Proximus-Light.woff2	21617
https://www.proximus.be/resources/cdn/brand/fonts/Proximus-ExtraB.woff2	20855
https://www.proximus.be/resources/cdn/brand/fonts/Proximus-Bold.woff2	18647
https://www.proximus.be/resources/cdn/brand/fonts/Proximus-Regular.woff2	18257

Show Details

Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Proximus.be should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.

JavaScript execution time — 0.9 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

URL	Total CPU Time (Ms)	Script Evaluation (Ms)	Script Parse (Ms)
https://www.proximus.be/.resources/cdn/webcomponents/packs/iportal-optimized-pack.js	1114.58	732.64	94.12
https://www.proximus.be/en/personal/?	493.624	56.604	12.036
https://www.proximus.be/.resources/cdn/cis/css/iportal-all-css-pack~2019-04-11-12-47-03-619~cache.css	150.708	0	0
Unattributable	120.284	4.448	0.932

Show Details

Minimizes main-thread work — 1.9 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

Category	Time Spent (Ms)
Script Evaluation	793.692
Style & Layout	479.084
Other	243.472
Parse HTML & CSS	179.912
Script Parsing & Compilation	107.088
Rendering	48.208
Garbage Collection	27.74

Show Details

Keep request counts low and transfer sizes small — 12 requests • 765 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.

Resource Type	Requests	Transfer Size (Bytes)
Total	12	783184
Script	1	325188
Font	6	222799
Stylesheet	1	147951
Image	1	46689
Document	1	40046
Other	2	511
Media	0	0
Third-party	0	0

Show Details

Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.

Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).

Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.

Element
epic combo At home & on the go € 59 /month during 6 months I go for it

Show Details

Avoid large layout shifts — 3 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.

Element	CLS Contribution
0 MENU	0.00018345747999455
EN	0.00010022626485948
li	6.4529239019119E-5

Show Details

Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.

Avoid long main-thread tasks — 3 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.

URL	Start Time (Ms)	Duration (Ms)
https://www.proximus.be/.resources/cdn/webcomponents/packs/iportal-optimized-pack.js	6000	539
https://www.proximus.be/.resources/cdn/cis/css/iportal-all-css-pack~2019-04-11-12-47-03-619~cache.css	2820	151
https://www.proximus.be/en/personal/?	1841	101

Show Details

Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.

Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Other

Network Requests
Below is a list of network requests that were made during page load.

URL	Protocol	Start Time (Ms)	End Time (Ms)	Transfer Size (Bytes)	Resource Size (Bytes)	Status Code	MIME Type	Resource Type
http://proximus.be/	http/1.1	0	293.1099999696	277	0	301	text/html
https://www.proximus.be/	http/1.1	293.51300001144	828.29299999867	234	0	302
https://www.proximus.be/en/personal/?	http/1.1	828.90600000974	1470.3899999149	40046	217126	200	text/html	Document
https://www.proximus.be/resources/cdn/brand/fonts/Proximus-Regular.woff2	http/1.1	1482.3849999812	2301.1260000058	18257	17768	200	application/font-woff2	Font
https://www.proximus.be/resources/cdn/brand/fonts/Proximus-Bold.woff2	http/1.1	1482.6549999416	1983.2310000202	18647	18160	200	application/font-woff2	Font
https://www.proximus.be/resources/cdn/brand/fonts/Proximus-Light.woff2	http/1.1	1482.8930000076	1999.570999993	21617	21128	200	application/font-woff2	Font
https://www.proximus.be/resources/cdn/brand/fonts/Proximus-ExtraB.woff2	http/1.1	1483.2879999885	1988.0089999642	20855	20368	200	application/font-woff2	Font
https://www.proximus.be/resources/cdn/brand/fonts/PxIcon.woff2?v=3.2.1.2.98.2	http/1.1	1483.4750000155	2490.1479999535	71757	71268	200	application/font-woff2	Font
https://www.proximus.be/.resources/cdn/cis/css/iportal-all-css-pack~2019-04-11-12-47-03-619~cache.css	http/1.1	1485.503999982	2333.547999966	147951	1148626	200	text/css	Stylesheet
https://www.proximus.be/.resources/cdn/webcomponents/packs/iportal-optimized-pack.js	http/1.1	1491.5909999982	2746.4959999779	325188	1050832	200	application/javascript	Script
https://www.proximus.be/resources/cdn/brand/fonts/PxIcon.woff2?v=3.2.1.2.115.0	http/1.1	2400.8049999829	3012.7329999814	71666	71268	200	application/font-woff2	Font
	data	2417.454999988	2417.6619999344	0	4906	200	image/png	Image
	data	2418.0169999599	2418.1389999576	0	4072	200	image/png	Image
	data	2418.3600000106	2418.4399999212	0	2014	200	image/jpeg	Image
	data	2418.6109999428	2418.646999984	0	42	200	image/gif	Image
	data	2422.470999998	2422.5209999131	0	88	200	image/svg+xml	Image
https://www.proximus.be/dam/jcr:cfd06ea2-3187-4c85-96de-de49f3bb5663/cdn/sites/iportal/images/content-header/res/epic-combo-perso-tb-1904/epic-combo-perso-tb-1904-s-en~2019-03-28-16-14-27~cache.jpg	http/1.1	2427.4609999266	2951.2029999169	46689	46357	200	image/jpeg	Image
	data	2430.188999977	2430.2419999149	0	418	200	image/svg+xml	Image

Show Details

Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.

Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.

Tasks
Below is a list of the top-level main thread tasks that executed during page load.

Start Time (Ms)	End Time (Ms)
1506.563	6.609
2369.962	37.677
2407.655	19.066
2427.995	15.783
2443.891	11.873
2456.947	50.655
2836.602	269.444
3110.461	10.556

Show Details

Diagnostics
Below is a collection of useful page vitals.
View Data

Metrics
Below is a collection of metrics.
View Data

Metrics

First Contentful Paint — 2.7 s
The time taken for the first image or text on the page to be rendered.

Time to Interactive — 6.4 s
The time taken for the page to become fully interactive.

Total Blocking Time — 440 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

First CPU Idle — 6.2 s
The time taken for the page's main thread to be quiet enough to handle input.

First Meaningful Paint — 2.7 s
The time taken for the primary content of the page to be rendered.

Estimated Input Latency — 90 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive proximus.be as laggy when the latency is higher than 0.05 seconds.

First Contentful Paint (3G) — 5520 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Remove unused CSS — Potential savings of 139 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Proximus.be should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.

URL	Transfer Size (Bytes)	Potential Savings (Bytes)
https://www.proximus.be/.resources/cdn/cis/css/iportal-all-css-pack~2019-04-11-12-47-03-619~cache.css	147951	142816

Show Details

Diagnostics

Serve static assets with an efficient cache policy — 1 resource found
Proximus.be can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.

URL	Cache TTL (Ms)	Transfer Size (Bytes)
https://www.proximus.be/.resources/cdn/webcomponents/packs/iportal-optimized-pack.js	86400000	325188

Show Details

Avoid an excessive DOM size — 1,064 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.

Statistic	Element	Value
Total DOM Elements		1064
Maximum DOM Depth	(Inte…	20
Maximum Child Elements	Personal EN 0 MENU epic combo At home & on the go € 59 /month during 6 months I…	26

Show Details

Metrics

Speed Index — 6.0 s
The time taken for the page contents to be visibly populated.

Largest Contentful Paint — 6.8 s
The timing of the largest text or image that is painted.

Other

Max Potential First Input Delay — 540 ms
Users could experience a delay when interacting with the page.

Opportunities

Eliminate render-blocking resources — Potential savings of 890 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Proximus.be should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.

URL	Transfer Size (Bytes)	Potential Savings (Ms)
https://www.proximus.be/.resources/cdn/cis/css/iportal-all-css-pack~2019-04-11-12-47-03-619~cache.css	147951	930

Show Details

Remove unused JavaScript — Potential savings of 211 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.

URL	Transfer Size (Bytes)	Potential Savings (Bytes)
https://www.proximus.be/.resources/cdn/webcomponents/packs/iportal-optimized-pack.js	325188	215599

Show Details

Reduce initial server response time — Root document took 640 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.

URL	Time Spent (Ms)
https://www.proximus.be/en/personal/?	642.48

Show Details

Avoid multiple page redirects — Potential savings of 1,410 ms
Redirects can cause additional delays before the page can begin loading. Proximus.be should avoid multiple or unnecessary page redirects.

URL	Time Spent (Ms)
http://proximus.be/	630
https://www.proximus.be/	780
https://www.proximus.be/en/personal/?	0

Show Details

Preload key requests — Potential savings of 1,050 ms
Key requests can be preloaded by using '<link rel=preload>'. Proximus.be should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.

URL	Potential Savings (Ms)
https://www.proximus.be/resources/cdn/brand/fonts/PxIcon.woff2?v=3.2.1.2.115.0	1050

Show Details

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.

URL	Potential Savings (Ms)
https://www.proximus.be/resources/cdn/brand/fonts/PxIcon.woff2?v=3.2.1.2.115.0	611.92799999844

Show Details

Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.

Source
SHOW DETAILS

Show Details

Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

URL	Failing Elements
	Proximus home
	Huawei Mate 20 Lite
	Samsung Galaxy A7
	Apple Iphone 6S
	serie
	myProximus
	MyProximus application
	Proximus TV app
	Proximus 11 application
	Proximus Wi-Fi Hotspots app
	Proximus Cloud application
	img