5 sec in total
349 ms
4.5 sec
139 ms
Visit gkb.ch now to see the best up-to-date Gkb content for Liechtenstein and also check out these interesting facts you probably never knew about gkb.ch
Graubündner Kantonalbank – Die Partnerin für Finanzierungen, Anlagen, Vermögensverwaltung und Vorsorge.
Visit gkb.chWe analyzed Gkb.ch page load time and found that the first response time was 349 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
gkb.ch performance score
name
value
score
weighting
Value7.8 s
0/100
10%
Value26.9 s
0/100
25%
Value18.1 s
0/100
10%
Value2,640 ms
4/100
30%
Value0.465
19/100
15%
Value32.7 s
0/100
10%
349 ms
115 ms
350 ms
228 ms
573 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 93% of them (51 requests) were addressed to the original Gkb.ch, 5% (3 requests) were made to Yourmoney.ch and 2% (1 request) were made to Stats.gkb.ch. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Gkb.ch.
Page size can be reduced by 386.4 kB (59%)
653.9 kB
267.5 kB
In fact, the total size of Gkb.ch main page is 653.9 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. 20% of websites need less resources to load. Javascripts take 428.3 kB which makes up the majority of the site volume.
Potential reduce by 13.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 13.8 kB or 72% of the original size.
Potential reduce by 895 B
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. Gkb images are well optimized though.
Potential reduce by 310.2 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 310.2 kB or 72% of the original size.
Potential reduce by 61.6 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. Gkb.ch needs all CSS files to be minified and compressed as it can save up to 61.6 kB or 84% of the original size.
Number of requests can be reduced by 35 (67%)
52
17
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gkb. 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 5 to 1 for CSS and as a result speed up the page load time.
www.gkb.ch
349 ms
home
115 ms
home
350 ms
yui-reset-min.css
228 ms
gkb.css
573 ms
socialshareprivacy.css
463 ms
slimbox2.css
468 ms
common.js
371 ms
jquery-1.4.4.min.js
698 ms
jquery-ui.min.js
948 ms
nx.js
649 ms
nx.util.js
710 ms
nx.util.log.dev.js
722 ms
nx.selecttext.js
856 ms
jquery.searchText.js
883 ms
nx.init.js
816 ms
jquery.tabs.js
933 ms
nx.tabs.js
985 ms
jquery.hometabs.js
934 ms
jquery.socialshareprivacy.js
1087 ms
slimbox2.js
1152 ms
jquery.hoverIntent.js
1167 ms
jquery.cookie.min.js
1056 ms
jquery.loop.js
1191 ms
glowbuttonsettings.js
1258 ms
dropnav.js
1289 ms
swfobject22.js
1325 ms
financialparameters.js
1407 ms
fadeSlideShow.js
1399 ms
jquery.banksearchwidget.js
1310 ms
nx.pdash.js
1390 ms
gkb-logo.gif
235 ms
newsroom_smaller.jpg
263 ms
rss_smaller.jpg
146 ms
home_banner_ws_sparen_2015.jpg
282 ms
jobs_guetesiegel_home_2014.jpg
266 ms
gkb-slogan.gif
199 ms
gr-logo.gif
281 ms
twitter.jpg
320 ms
fb.jpg
350 ms
youtube.jpg
379 ms
flickr.jpg
384 ms
chart3.jsp
762 ms
search-bg-blue.png
494 ms
login-bg-blue.png
502 ms
content-bg4.gif
537 ms
sprite-blue.png
564 ms
button-blue.png
587 ms
footer-bg.gif
584 ms
piwik.js
702 ms
aGetRotatingVisual
665 ms
chart3.jsp;jsessionid=AA10DD1A941DB631977B6D0A24A7D82E
188 ms
crameri_fallback.jpg
233 ms
trend_-1.png
191 ms
print.css
232 ms
gkb.ch 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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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.
gkb.ch best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
gkb.ch SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gkb.ch 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 Gkb.ch 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.
gkb.ch
Open Graph description is not detected on the main page of Gkb. 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: