Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

Page Load Speed

2.4 sec in total

First Response

292 ms

Resources Loaded

2 sec

Page Rendered

155 ms

ebanking.bkb.ch screenshot

About Website

Visit ebanking.bkb.ch now to see the best up-to-date Ebanking Bkb content for Switzerland and also check out these interesting facts you probably never knew about ebanking.bkb.ch

Visit ebanking.bkb.ch

Key Findings

We analyzed Ebanking.bkb.ch page load time and found that the first response time was 292 ms and then it took 2.1 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.

Performance Metrics

ebanking.bkb.ch performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

16/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value420 ms

66/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

ebanking.bkb.ch

292 ms

ebanking.bkb.ch

398 ms

108 ms

140 ms

p

100 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that all of those requests were addressed to Ebanking.bkb.ch and no external sources were called. The less responsive or slowest element that took the longest time to load (398 ms) belongs to the original domain Ebanking.bkb.ch.

Page Optimization Overview & Recommendations

Page size can be reduced by 19.4 kB (72%)

Content Size

27.0 kB

After Optimization

7.6 kB

In fact, the total size of Ebanking.bkb.ch main page is 27.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 5% of websites need less resources to load. CSS take 13.5 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 9.6 kB

  • Original 13.5 kB
  • After minification 11.5 kB
  • After compression 3.9 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 1.9 kB, which is 14% 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 9.6 kB or 71% of the original size.

CSS Optimization

-73%

Potential reduce by 9.8 kB

  • Original 13.5 kB
  • After minification 10.4 kB
  • After compression 3.7 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. Ebanking.bkb.ch needs all CSS files to be minified and compressed as it can save up to 9.8 kB or 73% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

6

After Optimization

6

The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ebanking Bkb. According to our analytics all requests are already optimized.

Accessibility Review

ebanking.bkb.ch accessibility score

84

Accessibility Issues

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

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

High

ARIA IDs are not unique

Best Practices

ebanking.bkb.ch best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

ebanking.bkb.ch SEO score

73

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    IT

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ebanking.bkb.ch can be misinterpreted by Google and other search engines. Our service has detected that Italian 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 Ebanking.bkb.ch 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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Ebanking Bkb. 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: