2.8 sec in total
553 ms
2.1 sec
175 ms
Click here to check amazing Connect content. Otherwise, check out these important facts you probably never knew about connect.be
Wij verbinden mens en omgeving vanuit ons kantoor in Hasselt. Sparren met een strategisch communicatiebureau over jouw communicatie-uitdagingen? Contacteer ons!
Visit connect.beWe analyzed Connect.be page load time and found that the first response time was 553 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
connect.be performance score
name
value
score
weighting
Value2.0 s
84/100
10%
Value12.7 s
0/100
25%
Value7.3 s
29/100
10%
Value1,530 ms
13/100
30%
Value0.002
100/100
15%
Value11.8 s
17/100
10%
553 ms
266 ms
618 ms
474 ms
347 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 97% of them (68 requests) were addressed to the original Connect.be, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (783 ms) belongs to the original domain Connect.be.
Page size can be reduced by 364.7 kB (30%)
1.2 MB
869.0 kB
In fact, the total size of Connect.be main page is 1.2 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. 30% of websites need less resources to load. Images take 777.5 kB which makes up the majority of the site volume.
Potential reduce by 30.7 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 30.7 kB or 81% of the original size.
Potential reduce by 36.0 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. Connect images are well optimized though.
Potential reduce by 283.7 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 283.7 kB or 71% of the original size.
Potential reduce by 14.2 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. Connect.be needs all CSS files to be minified and compressed as it can save up to 14.2 kB or 80% of the original size.
Number of requests can be reduced by 5 (7%)
68
63
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Connect. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
connect.be
553 ms
seBasis.css
266 ms
jquery-1.7.1.min.js
618 ms
jquery.cycle.all.min.js
474 ms
destijl_algemeen.css
347 ms
destijl_large.css
212 ms
WebResource.axd
428 ms
Telerik.Web.UI.WebResource.axd
302 ms
se3_basis_page_js.js
417 ms
logo.gif
128 ms
w500h500_ft204.jpg
128 ms
w500h500_ft163.jpg
192 ms
w500h500_ft186.jpg
130 ms
w500h500_ft164.jpg
321 ms
w500h500_ft165.jpg
198 ms
w500h500_ft187.jpg
214 ms
w500h500_ft166.jpg
313 ms
w500h500_ft167.jpg
291 ms
w500h500_ft189.jpg
283 ms
w500h500_ft168.jpg
384 ms
w500h500_ft169.jpg
324 ms
w500h500_ft190.jpg
378 ms
w500h500_ft191.jpg
387 ms
w500h500_ft170.jpg
509 ms
w500h500_ft193.jpg
420 ms
w500h500_ft241.jpg
432 ms
w500h500_ft171.jpg
483 ms
icon_blog_groot.gif
482 ms
icon_twitter_oranje.gif
491 ms
icon_linkedin_oranje.gif
518 ms
icon_nieuwsbrief_oranje.gif
533 ms
icon_activities.gif
581 ms
icon_connecttv.gif
583 ms
projecticonen.gif
586 ms
icon_history.gif
615 ms
w200h200_ft401.jpg
626 ms
w200h200_ft392.jpg
642 ms
w200h200_ft389.jpg
684 ms
w200h200_ft388.jpg
681 ms
w200h200_ft387.jpg
691 ms
w200h200_ft378.jpg
722 ms
w200h200_ft372.jpg
730 ms
w200h200_ft368.jpg
749 ms
w200h200_ft367.jpg
783 ms
w200h200_ft332.jpg
764 ms
ga.js
8 ms
__utm.gif
15 ms
helvet01-webfont.woff
666 ms
w200h200_ft279.jpg
698 ms
w200h200_ft280.jpg
699 ms
w200h200_ft282.jpg
665 ms
w200h200_ft139.jpg
687 ms
w200h200_ft141.jpg
674 ms
w200h200_ft294.jpg
607 ms
w200h200_ft326.jpg
639 ms
w200h200_ft327.jpg
614 ms
w200h200_ft146.jpg
632 ms
w200h200_ft152.jpg
667 ms
w200h200_ft295.jpg
622 ms
w200h200_ft154.jpg
610 ms
w200h200_ft156.jpg
636 ms
w200h200_ft158.jpg
613 ms
w200h200_ft160.jpg
638 ms
icon_books.gif
610 ms
icon_adres.gif
601 ms
icon_jobs.gif
621 ms
icon_maill.gif
621 ms
icon_phone.gif
642 ms
banner.gif
637 ms
playbut.gif
588 ms
connect.be accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
connect.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
connect.be SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
NL
NL
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Connect.be can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Connect.be main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
connect.be
Open Graph description is not detected on the main page of Connect. 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: