27.1 sec in total
392 ms
18.7 sec
8 sec
Click here to check amazing Ebase content for Germany. Otherwise, check out these important facts you probably never knew about ebase.com
Die FNZ Bank bietet smarte Lösungen für die Vermögensanlage. Unsere Partner profitieren von Lösungen im Depotgeschäft, Einlagensicherung und Portfolioverwaltung - auf Wunsch im White-Label.
Visit ebase.comWe analyzed Ebase.com page load time and found that the first response time was 392 ms and then it took 26.7 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
ebase.com performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value9.9 s
0/100
25%
Value10.2 s
8/100
10%
Value490 ms
59/100
30%
Value0.068
96/100
15%
Value16.2 s
6/100
10%
392 ms
345 ms
2366 ms
561 ms
6790 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 67% of them (35 requests) were addressed to the original Ebase.com, 29% (15 requests) were made to Portal.ebase.com and 2% (1 request) were made to Responder.wt-safetag.com. The less responsive or slowest element that took the longest time to load (6.8 sec) relates to the external source Portal.ebase.com.
Page size can be reduced by 739.9 kB (34%)
2.2 MB
1.4 MB
In fact, the total size of Ebase.com main page is 2.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. 45% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 32.8 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 32.8 kB or 80% of the original size.
Potential reduce by 232.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. Obviously, Ebase needs image optimization as it can save up to 232.7 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 312.9 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 312.9 kB or 71% of the original size.
Potential reduce by 161.5 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. Ebase.com needs all CSS files to be minified and compressed as it can save up to 161.5 kB or 80% of the original size.
Number of requests can be reduced by 27 (64%)
42
15
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ebase. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
ebase.com
392 ms
www.ebase.com
345 ms
www.ebase.com
2366 ms
merged-42d923ce763295bd4408748f341ec608-d69505ab6035063fc28ece440b208f09.css.gzip
561 ms
marktdaten
6790 ms
merged-e21e79dc6cec9977235a91bece1ce561-022cb7ed7831214e28da832c421f7dca.js.gzip
1676 ms
merged-29a489dad5f47cd38fdd478ba2286534-957b85020bbf475d9a7ac8c305d881de.js.gzip
2724 ms
merged-ce6561d0eca69ba49dd25d840a0df2ea-233e3722b179bed90ec4d14df1fde3fc.js.gzip
2705 ms
webtrekk_v4.min-c448d6399104c009afc6029759ae76ce.js.gzip
2579 ms
cb_indexedsearch_autocomplete.js
2494 ms
cb_indexedsearch_autocomplete.css
2559 ms
logo.png
2493 ms
Slider_Sparplaene_966x250.jpg
2576 ms
Slider_WPD_966x250.png
6548 ms
Slider_VL_Sparen_966x250.png
6546 ms
twitter-icon.png
2577 ms
envelope-icon.png
2576 ms
Kontakt___Hilfe.jpg
6349 ms
sparplaene.png
6468 ms
icon-kununu.png
6128 ms
icon-xing.png
6128 ms
icon-twitter.png
6384 ms
icon-linkedin.png
6464 ms
icon-gplus.png
6467 ms
icon-youtube.png
6412 ms
lupe.png
6046 ms
icon-people-white.png
6046 ms
arrow-right-dark.png
6046 ms
icon-login.png
5951 ms
arrow-down-white.png
5950 ms
menu-arrow-down-white.png
5951 ms
markenwinkel.png
5996 ms
dax.woff
6277 ms
eox-btn.woff
4715 ms
dax-md.woff
4728 ms
727919845443971
4343 ms
styles.css
1175 ms
modernizr.js
1314 ms
jquery.min.js
2847 ms
jquery.scrollTo.min.js
3863 ms
common.js
3862 ms
styles_teledata.css
3864 ms
milonic_menu_code.js
3862 ms
wt
4063 ms
ico_alert.gif
435 ms
ico_bullet_a.gif
434 ms
0.gif
389 ms
dax-bd.woff
883 ms
dax-md.woff
879 ms
dax.woff
879 ms
gi.aspx
314 ms
ebase.css
1133 ms
ebase.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
ebase.com 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
Missing source maps for large first-party JavaScript
ebase.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ebase.com can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Ebase.com 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.
ebase.com
Open Graph data is detected on the main page of Ebase. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: