5 sec in total
352 ms
4.2 sec
497 ms
Welcome to 2go.be homepage info - get ready to check 2 Go best content right away, or after learning these important things about 2go.be
Professionele webhosting, cloud hosting en servers voor Linux en Windows met domeinnaam. 24/7 gratis premium support! Combell, dé hosting specialist.
Visit 2go.beWe analyzed 2go.be page load time and found that the first response time was 352 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
2go.be performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value8.9 s
1/100
25%
Value8.5 s
17/100
10%
Value3,840 ms
1/100
30%
Value0.004
100/100
15%
Value19.8 s
2/100
10%
352 ms
423 ms
727 ms
813 ms
207 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original 2go.be, 12% (9 requests) were made to and 7% (5 requests) were made to Images01.combell.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Combell.com.
Page size can be reduced by 951.2 kB (55%)
1.7 MB
772.2 kB
In fact, the total size of 2go.be main page is 1.7 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. 40% of websites need less resources to load. Javascripts take 780.9 kB which makes up the majority of the site volume.
Potential reduce by 56.4 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 7.4 kB, which is 11% 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 56.4 kB or 83% of the original size.
Potential reduce by 17.4 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. 2 Go images are well optimized though.
Potential reduce by 515.4 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 515.4 kB or 66% of the original size.
Potential reduce by 362.1 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. 2go.be needs all CSS files to be minified and compressed as it can save up to 362.1 kB or 85% of the original size.
Number of requests can be reduced by 23 (40%)
57
34
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 2 Go. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
www.combell.com
352 ms
nl
423 ms
responsive.min.css
727 ms
website.min.js
813 ms
jbv6gum.js
207 ms
2205010518.js
289 ms
d
268 ms
flag_be.png
1076 ms
flag_nl.png
1074 ms
logo.png
1080 ms
dropdown_arrow.png
1072 ms
icomoon.ttf
691 ms
combell-performancehosting.png
1105 ms
drupal.png
1041 ms
wordpress.png
1038 ms
umbraco-hosting.png
1043 ms
smartbusiness.png
1042 ms
ispgids.png
1091 ms
drupal-webhosting.png
997 ms
magento-webhosting.png
997 ms
concrete5-hosting.png
1684 ms
be.png
807 ms
immo.png
781 ms
online.png
940 ms
wordpress-hosting.png
1100 ms
social_twitter.png
1090 ms
googleplaces.png
1028 ms
social_facebook.png
1030 ms
clients.jpg
1095 ms
pcmag.png
1089 ms
social_rss.png
1086 ms
joomla.png
1021 ms
loader.gif
1023 ms
payments.png
1030 ms
social_youtube.png
1036 ms
prestashop-hosting.png
1098 ms
webhostersnl.png
1083 ms
social_linkedin.png
1087 ms
deloitte.png
1085 ms
magento.png
1014 ms
winmagpro.png
1085 ms
flag_nl.png
1021 ms
flag_be.png
1082 ms
promo.jpg
1000 ms
combell_bg.png
1039 ms
event
459 ms
EMZpFpuZrNbHKYw1xyLW+95PW7UD4FFLKAIoopoZQyyqmgkirLmGpqqKWOehZZvvtZwtLfLvrv+M858RMRB8rZAAAA
206 ms
4zznxExEHytkAAAA=
205 ms
jPOfETEQfK2QAAAA==
204 ms
3pXPwHVnRn5AAAA
203 ms
1rH4BDtkYGgAA
202 ms
3pXPwH15RoJAAAA
201 ms
96Vz8B9eUaCQAAAA==
201 ms
jPOfETEQfK2QAAAA==
199 ms
4zznxExEHytkAAAA=
198 ms
dc.js
421 ms
hotjar-33962.js
452 ms
gtm.js
465 ms
rest
618 ms
btt-arrow.svg
489 ms
p.gif
235 ms
__utm.gif
38 ms
modules-043c1e6abe660c48857202e419ff9d8a.js
77 ms
analytics.js
82 ms
ga-audiences
69 ms
collect
23 ms
collect
23 ms
ga-audiences
16 ms
collect
27 ms
collect
21 ms
ga-audiences
17 ms
visit-data
204 ms
roundtrip.js
142 ms
2go.be accessibility score
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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
2go.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
Page has valid source maps
2go.be SEO score
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
NL
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 2go.be can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 2go.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.
2go.be
Open Graph data is detected on the main page of 2 Go. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: