7.9 sec in total
246 ms
7.4 sec
206 ms
Click here to check amazing Homebank content. Otherwise, check out these important facts you probably never knew about homebank.be
Veilig inloggen? Controleer het internetadres, houd je inloggegevens geheim, laat niemand meekijken en doe niks op verzoek. Regel al je bankzaken makkelijk zelf.
Visit homebank.beWe analyzed Homebank.be page load time and found that the first response time was 246 ms and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
homebank.be performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value16.6 s
0/100
25%
Value5.7 s
50/100
10%
Value2,560 ms
4/100
30%
Value0.511
15/100
15%
Value18.2 s
3/100
10%
246 ms
182 ms
582 ms
275 ms
283 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Homebank.be, 2% (1 request) were made to Www3s.ing.be. The less responsive or slowest element that took the longest time to load (4.3 sec) relates to the external source Ing.be.
Page size can be reduced by 1.0 MB (68%)
1.5 MB
485.0 kB
In fact, the total size of Homebank.be main page is 1.5 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 912.9 kB which makes up the majority of the site volume.
Potential reduce by 41.3 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 6.5 kB, which is 12% 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 41.3 kB or 78% of the original size.
Potential reduce by 5.7 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. Homebank images are well optimized though.
Potential reduce by 691.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 691.4 kB or 76% of the original size.
Potential reduce by 284.0 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. Homebank.be needs all CSS files to be minified and compressed as it can save up to 284.0 kB or 73% of the original size.
Number of requests can be reduced by 42 (70%)
60
18
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Homebank. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
login
246 ms
open.min.css
182 ms
open.min.js
582 ms
optimum-content.min.css
275 ms
content.min.css
283 ms
HtmlEditorStyles.css
366 ms
csseditor.min.css
279 ms
migration-fixes.css
282 ms
branding.css
362 ms
branding.js
366 ms
search.config.min.js
366 ms
ing-k2-cookie-law.min.js
367 ms
cm-lib-base.css
539 ms
cm-lib-uilib.css
454 ms
cm-master.css
455 ms
cm-master-fix.css
455 ms
CCR-Fix.css
455 ms
Login_box.css
543 ms
satelliteLib-9c1b5720bd68d7959813ad2ac4e25efea33297d1.js
722 ms
cardreader-loader.js
542 ms
angular.min.js
759 ms
SSO.js
714 ms
SSO.css
632 ms
jquery-ui.min.js
898 ms
jquery.nestedsortable.min.js
664 ms
cm-lib-tabs.js
748 ms
cm-master.js
753 ms
ApplyOnlinePopup.js
801 ms
fix-dropdown.js
808 ms
ssonumberfix.js
811 ms
sslstrip.js
842 ms
hb4all-lionaccount-fix.js
844 ms
ing.k2.metrics.min.js
888 ms
mbox-contents-31ad9395290c6b2cf352d3d8d966be910c13d560.js
163 ms
blank.gif
104 ms
CardStop.png
104 ms
febelfin_logo_fr.png
104 ms
BankOfTheYear.gif
105 ms
beCommerce.gif
105 ms
seperator.png
4324 ms
sideline.png
4327 ms
picto-socialmedia.png
4308 ms
arrows.png
4309 ms
dvu-min.js
4273 ms
ssoccr.css
4262 ms
sso-resources-en.json
817 ms
ssohttphandler.ashx
1191 ms
INGID.png
180 ms
dropdown_arrow.png
90 ms
CardID.png
179 ms
c-icon-sprite.png
92 ms
Cardreader_03.png
94 ms
Identify_11.png
92 ms
OK_07.png
179 ms
cm-cookie-popin-close.gif
180 ms
cm-check-fff.png
180 ms
cm-cookie-law-corner.png
180 ms
ingtag-min.js
259 ms
s_code-min.js
91 ms
s58622103261295
185 ms
print.min.css
96 ms
homebank.be accessibility score
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.
homebank.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
homebank.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 Homebank.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 Homebank.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.
homebank.be
Open Graph description is not detected on the main page of Homebank. 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: