8.5 sec in total
295 ms
8.1 sec
141 ms
Click here to check amazing KPT content for Switzerland. Otherwise, check out these important facts you probably never knew about kpt.ch
Als Krankenkasse mit dem Plus bieten wir Ihnen innovative Krankenversicherungen für Ihre Bedürfnisse und persönlichen Service.<br/>
Visit kpt.chWe analyzed Kpt.ch page load time and found that the first response time was 295 ms and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
kpt.ch performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value10.5 s
0/100
25%
Value8.6 s
17/100
10%
Value3,580 ms
1/100
30%
Value0.152
75/100
15%
Value13.6 s
11/100
10%
295 ms
304 ms
247 ms
108 ms
5861 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 80% of them (37 requests) were addressed to the original Kpt.ch, 7% (3 requests) were made to Track.adform.net and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.9 sec) belongs to the original domain Kpt.ch.
Page size can be reduced by 867.6 kB (60%)
1.5 MB
587.8 kB
In fact, the total size of Kpt.ch 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. 25% of websites need less resources to load. Javascripts take 997.7 kB which makes up the majority of the site volume.
Potential reduce by 95.7 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 22.6 kB, which is 18% 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 95.7 kB or 76% of the original size.
Potential reduce by 4.6 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. KPT images are well optimized though.
Potential reduce by 706.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 706.2 kB or 71% of the original size.
Potential reduce by 61.1 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. Kpt.ch needs all CSS files to be minified and compressed as it can save up to 61.1 kB or 83% of the original size.
Number of requests can be reduced by 16 (41%)
39
23
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of KPT. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.
kpt.ch
295 ms
www.kpt.ch
304 ms
VariationRoot.aspx
247 ms
de
108 ms
default.aspx
5861 ms
init.js
523 ms
kptnet.ui.ribbonactioncommands.js
319 ms
ScriptResource.axd
511 ms
blank.js
223 ms
ScriptResource.axd
412 ms
controls15.css
327 ms
main.css
392 ms
main.garaio.css
432 ms
WebResource.axd
254 ms
jquery-1.11.0.min.js
229 ms
functions.js
234 ms
functions.garaio.js
306 ms
conversion.js
14 ms
ga.js
101 ms
455 ms
favicon.ico
131 ms
spcommon.png
130 ms
top_kpt_80x67.jpg
130 ms
top_news_80x67.jpg
131 ms
top_service_80x67.jpg
129 ms
top_produkte_80x67.jpg
130 ms
top_jobs_80x67.jpg
231 ms
top_kontakt_80x67.jpg
236 ms
teaser_inform_0115_200x130.jpg
328 ms
teaser_sicuranta_200x130_bild.jpg
239 ms
home_winter_540x250_0216.jpg
421 ms
Steuerbescheinigung_0116_240x170.jpg
325 ms
teaser_rf_200x130_bild_0813.jpg
330 ms
kpt-logo-de.gif
319 ms
square-white.gif
316 ms
square-red.gif
410 ms
78 ms
__utm.gif
14 ms
collect
59 ms
49 ms
initstrings.js
296 ms
strings.js
134 ms
214 ms
core.js
233 ms
108 ms
ScriptResx.ashx
112 ms
kpt.ch accessibility score
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
Links do not have a discernible name
kpt.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
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
kpt.ch 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
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 Kpt.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 Kpt.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.
kpt.ch
Open Graph description is not detected on the main page of KPT. 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: