Tools & Wizards About Us
proximus-spearit.be screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

proximus-spearit.be

ICT for large companies and public sector | Proximus NXT

Page Load Speed

3.6 sec in total

First Response

329 ms

Resources Loaded

2.9 sec

Page Rendered

367 ms

proximus-spearit.be screenshot

About Website

Visit proximus-spearit.be now to see the best up-to-date Proximus Spearit content and also check out these interesting facts you probably never knew about proximus-spearit.be

Transform your business with our solutions and advice from our ICT experts. Integrate cloud, data, or cybersecurity within your company with Proximus NXT.

Visit proximus-spearit.be

Key Findings

We analyzed Proximus-spearit.be page load time and found that the first response time was 329 ms and then it took 3.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

proximus-spearit.be performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value12.0 s

0/100

25%

SI (Speed Index)

Value10.9 s

6/100

10%

TBT (Total Blocking Time)

Value3,190 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.075

95/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

Network Requests Diagram

proximus-spearit.be

329 ms

www.proximus-spearit.be

560 ms

companies-and-public-sector

1100 ms

ruxitagentjs_ICA2NQVfghjqrtux_10285240307101407.js

495 ms

install.js

17 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Proximus-spearit.be, 76% (28 requests) were made to Proximus.be and 8% (3 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Proximus.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 76.6 kB (24%)

Content Size

325.2 kB

After Optimization

248.7 kB

  • HTML
  • JavaScript

In fact, the total size of Proximus-spearit.be main page is 325.2 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. 20% of websites need less resources to load. Javascripts take 227.5 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 76.2 kB

  • Original 97.7 kB
  • After minification 85.3 kB
  • After compression 21.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 12.4 kB, which is 13% 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 76.2 kB or 78% of the original size.

JavaScript Optimization

-0%

Potential reduce by 330 B

  • Original 227.5 kB
  • After minification 227.5 kB
  • After compression 227.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 21 (62%)

Requests Now

34

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

proximus-spearit.be

proximus-spearit.be

329 ms

www.proximus-spearit.be

www.proximus-spearit.be

560 ms

companies-and-public-sector

companies-and-public-sector

1100 ms

ruxitagentjs_ICA2NQVfghjqrtux_10285240307101407.js

ruxitagentjs_ICA2NQVfghjqrtux_10285240307101407.js

495 ms

install.js

install.js

17 ms

utag.sync.js

utag.sync.js

70 ms

iportal-all-css-pack~2024-09-10-03-45-06-365~cache.css

iportal-all-css-pack~2024-09-10-03-45-06-365~cache.css

651 ms

mecor~2021-11-10-17-16-26~cache.css

mecor~2021-11-10-17-16-26~cache.css

288 ms

unicaJSModule.min~2024-10-01-16-40-06-000~cache.js

unicaJSModule.min~2024-10-01-16-40-06-000~cache.js

201 ms

nboEventHandlers.min~2024-10-01-16-40-06-000~cache.js

nboEventHandlers.min~2024-10-01-16-40-06-000~cache.js

290 ms

otSDKStub.js

otSDKStub.js

122 ms

iportal-all-pack-simplified~2024-10-03-04-45-00-528~cache.js

iportal-all-pack-simplified~2024-10-03-04-45-00-528~cache.js

871 ms

homePageRes.rslib.process~2021-07-12-12-16-47-075~cache.js

homePageRes.rslib.process~2021-07-12-12-16-47-075~cache.js

327 ms

showOverlayerForIE.min~2024-10-01-16-40-06-000~cache.js

showOverlayerForIE.min~2024-10-01-16-40-06-000~cache.js

333 ms

persoBannerLoadingLib.min~2024-10-01-16-40-06-000~cache.js

persoBannerLoadingLib.min~2024-10-01-16-40-06-000~cache.js

390 ms

dalAnswerReaction.min~2024-08-22-03-47-34-140~cache.js

dalAnswerReaction.min~2024-08-22-03-47-34-140~cache.js

439 ms

storageFlushCookieDelete.min~2024-08-22-03-47-34-160~cache.js

storageFlushCookieDelete.min~2024-08-22-03-47-34-160~cache.js

440 ms

persoMessageBox.min~2024-08-22-03-47-34-148~cache.js

persoMessageBox.min~2024-08-22-03-47-34-148~cache.js

487 ms

nboApp.min~2024-08-22-03-47-34-144~cache.js

nboApp.min~2024-08-22-03-47-34-144~cache.js

507 ms

radioButtonsSelectBoxApp.min~2024-08-22-03-47-34-150~cache.js

radioButtonsSelectBoxApp.min~2024-08-22-03-47-34-150~cache.js

519 ms

transitionEffect.min~2024-08-22-03-47-34-152~cache.js

transitionEffect.min~2024-08-22-03-47-34-152~cache.js

527 ms

radioButtonsToDeviceFinder.min~2024-08-22-03-47-34-158~cache.js

radioButtonsToDeviceFinder.min~2024-08-22-03-47-34-158~cache.js

614 ms

news-js-pack~2023-08-10-04-08-00-926~cache.js

news-js-pack~2023-08-10-04-08-00-926~cache.js

615 ms

mockPersoDataModule.min~2024-08-22-03-47-34-136~cache.js

mockPersoDataModule.min~2024-08-22-03-47-34-136~cache.js

628 ms

E2ePersoSessionStorageSet.min~2024-08-22-03-47-34-126~cache.js

E2ePersoSessionStorageSet.min~2024-08-22-03-47-34-126~cache.js

646 ms

utag.js

utag.js

118 ms

end-to-end-support-illu-2311~2023-11-13-14-21-00~cache.png

end-to-end-support-illu-2311~2023-11-13-14-21-00~cache.png

99 ms

sustainability-commitment-illu-2311~2023-11-13-14-21-00~cache.png

sustainability-commitment-illu-2311~2023-11-13-14-21-00~cache.png

98 ms

quality-guaranty-illu-2311~2023-11-13-14-21-00~cache.png

quality-guaranty-illu-2311~2023-11-13-14-21-00~cache.png

104 ms

davinsi-logo-pos.2023-11-13-16-13-13.png

davinsi-logo-pos.2023-11-13-16-13-13.png

114 ms

codit-logo-pos~2024-05-29-15-18-02~cache.2024-05-29-15-18-02.png

codit-logo-pos~2024-05-29-15-18-02~cache.2024-05-29-15-18-02.png

135 ms

telindus-logo-pos~2024-05-29-15-18-49~cache.2024-05-29-15-18-49.png

telindus-logo-pos~2024-05-29-15-18-49~cache.2024-05-29-15-18-49.png

197 ms

clear-media-logo-pos~2024-05-29-15-17-55~cache.2024-05-29-15-17-55.png

clear-media-logo-pos~2024-05-29-15-17-55~cache.2024-05-29-15-17-55.png

199 ms

myproximus-macbook-retina-2311-content.2023-11-14-09-29-41.png

myproximus-macbook-retina-2311-content.2023-11-14-09-29-41.png

290 ms

b4a1319a-035d-4902-b3c6-5585b36e3b7e.json

b4a1319a-035d-4902-b3c6-5585b36e3b7e.json

25 ms

location

location

33 ms

otBannerSdk.js

otBannerSdk.js

22 ms

Accessibility Review

proximus-spearit.be accessibility score

92

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 IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

proximus-spearit.be best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

proximus-spearit.be SEO score

91

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

proximus-spearit.be

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