Access ebase.com. FNZ Bank - Ihr moderner Banking Partner

Report Summary

About Website

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.com

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value540 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

ebase.com

346 ms

www.ebase.com

341 ms

fnz.de

736 ms

merged-b6238acd702084bcb50f04061f7f20fb-ed255793622b534290345c5581da962c.css.gzip

113 ms

merged-c5e258c764b92a0263f8f6092d597efb-89051ac19409b31b6e69ddacdbf74d63.css.gzip

332 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Ebase.com, 53% (31 requests) were made to Fnz.de and 14% (8 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Fnz.de.

Content Size

2.5 MB

After Optimization

1.8 MB

In fact, the total size of Ebase.com main page is 2.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. 55% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 99.4 kB

Original 121.6 kB
After minification 116.7 kB
After compression 22.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. 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 99.4 kB or 82% of the original size.

Image Optimization

-37%

Potential reduce by 673.8 kB

Original 1.8 MB
After minification 1.2 MB

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 673.8 kB or 37% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 1.4 kB

Original 584.7 kB
After minification 584.7 kB
After compression 583.3 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. This website has mostly compressed JavaScripts.

CSS Optimization

-50%

Potential reduce by 1.9 kB

Original 3.7 kB
After minification 3.7 kB
After compression 1.9 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 1.9 kB or 50% of the original size.

Requests Now

After Optimization

The browser has sent 51 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 25 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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.

High

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

DE
Language Claimed

DE
Encoding

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.

Social Sharing Optimization

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:

Report Summary

Performance

Accessibility

Best Practices

SEO

FNZ Bank - Ihr moderner Banking Partner

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)