Analyze

support.en.belgacom.be: Site Maintenance in progress

Configure Internet, use MyProximus or another question? We gladly help you

Page load speed analysis

  • 62/100

    Normal result
  • 6

    Successful tests
  • 2

    Failed tests
  • First response

    295 ms

  • Resources loaded

    3.4 sec

  • Page rendered

    303 ms

  • Total page load time

    4 sec

Visit support.en.belgacom.be now to see the best up-to-date Support En Belgacom content for Belgium and also check out these interesting facts you probably never knew about support.en.belgacom.be

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

Page optimization

  • HTML 67.2 kB
    Images 0 B
    Javascripts 351.5 kB
    CSS 0 B

    In fact, the total size of Support.en.belgacom.be main page is 418.7 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. 45% of websites need less resources to load. Javascripts take 351.5 kB which makes up the majority of the site volume.

    • Original 67.2 kB
    • After minification 61.2 kB
    • After compression 12.4 kB

    HTML optimization

    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 54.8 kB or 82% of the original size.

    • Original 351.5 kB
    • After minification 350.3 kB
    • After compression 104.5 kB

    JavaScript optimization

    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 247.0 kB or 70% of the original size.

Network requests diagram

  • support.en.belgacom.be
  • support.html
  • dtagent61_gxjnpr23t_8387.js
  • ecr-iportal-css-pack.2016-03-01-12-03-00-122.cache.css
  • cis-iportal-css-pack.2016-03-17-08-50-45-934.cache.css
  • modernizr.js
  • loader.js
  • ecr-iportal-js-pack.2016-03-15-15-54-00-998.cache.js
  • cis-iportal-js-pack.2016-03-17-10-20-47-670.cache.js
  • autocomplete.js
  • utag.js
  • proximus.png
  • support_settings.jpg
  • support_go.jpg
  • support_myproximus.jpg
  • 2_women_yellow_hat_curls_smartphone.jpg
  • logo-proximus-white.png
  • proximus_icon_my_proximus.png
  • proximus_icon_tv.png
  • proximus_icon_11.png
  • proximus_icon_wifi_spot.png
  • proximus_icon_cloud.png
  • Proximus-Regular.woff
  • PxIcon.woff
  • mother_daughter_trampoline_outdoor-s-en.jpg
  • overlapFrame20-60.png
  • Proximus-Bold.woff
  • set-cookie
  • utag.182.js
  • utag.105.js
  • utag.215.js
  • utag.239.js
  • utag.262.js
  • utag.147.js
  • utag.166.js
  • utag.322.js
  • searchZoneTemplate.html
  • rd
  • analytics.js
  • activityi;src=2799794;type=accue0;cat=cbu_p0;ord=7428492798935.622
  • fbevents.js
  • conversion_async.js
  • ntpagetag.gif
  • byside_webcare.js
  • mother_daughter_trampoline_outdoor-xl-en.jpg
  • ec.js
  • collect
  • collect
  • collect
  • collect
  • collect
  • dynaTraceMonitor
  • collect
  • wtid.php
  • ga-audiences
  • ga-audiences
  • id
  • s66038328781723

Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Support.en.belgacom.be, 45% (28 requests) were made to Proximus.be and 15% (9 requests) were made to Tags.tiqcdn.com. The less responsive or slowest element that took the longest time to load (877 ms) relates to the external source Proximus.be.

Additional info on support.en.belgacom.be

Requests

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

23

Javascripts

24

Images

2

CSS

4

AJAX

53

All

Possible request optimization

1

Javascripts

15

Images

2

CSS

4

AJAX

31

Optimized

22

All

Normal result

Redirects

As for redirects, our browser was forwarded to http://support.en.proximus.be/ before it reached this domain.

IP address

This IP address is dedicated to Support.en.belgacom.be. This is the best domain hosting practice .

Good result

IP Trace

DNS records

Type Host Target/ip TTL Other
A

onlinesupport-res-en.custhelp.com

74.117.207.205 899
CNAME

support.en.belgacom.be

onlinesupport-res-en.custhelp.com 1799

Language and encoding

Normal result

Language

N/A  language flag

Detected

EN en language flag

Claimed

Encoding

UTF-8

Claimed

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Support.en.belgacom.be can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Support.en.belgacom.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.

HTTPS certificate

SSL Certificate

Support.en.belgacom.be has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Poor result

Visitor World Map

Country of origin for 98.1% of all visits is Belgium. Unfortunately, we cannot track the location of Support.en.belgacom.be server and thus cannot define if the distance between their user base and server can potentially affect the page load time

Good result

Poor result

Social Sharing Optimization

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

support.en.belgacom.be

Share this report in social media

Analyze another website

Analyze