1.2 sec in total
396 ms
651 ms
174 ms
Click here to check amazing Kapferer content. Otherwise, check out these important facts you probably never knew about kapferer.ch
Stefan Kapferer - Software Engineer
Visit kapferer.chWe analyzed Kapferer.ch page load time and found that the first response time was 396 ms and then it took 825 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
kapferer.ch performance score
name
value
score
weighting
Value2.6 s
65/100
10%
Value3.6 s
60/100
25%
Value2.6 s
97/100
10%
Value0 ms
100/100
30%
Value0.063
97/100
15%
Value3.6 s
91/100
10%
396 ms
148 ms
24 ms
38 ms
50 ms
Our browser made a total of 9 requests to load all elements on the main page. We found that 11% of them (1 request) were addressed to the original Kapferer.ch, 22% (2 requests) were made to Fonts.googleapis.com and 22% (2 requests) were made to Stefan.kapferer.ch. The less responsive or slowest element that took the longest time to load (396 ms) belongs to the original domain Kapferer.ch.
Page size can be reduced by 4.6 kB (74%)
6.3 kB
1.7 kB
In fact, the total size of Kapferer.ch main page is 6.3 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 10% of websites need less resources to load. HTML takes 6.3 kB which makes up the majority of the site volume.
Potential reduce by 4.6 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.3 kB, which is 21% 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 4.6 kB or 74% of the original size.
Number of requests can be reduced by 3 (50%)
6
3
The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kapferer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for CSS and as a result speed up the page load time.
kapferer.ch
396 ms
stefan.kapferer.ch
148 ms
pixyll.css
24 ms
css
38 ms
css
50 ms
font-awesome.min.css
33 ms
font
19 ms
fontawesome-webfont.woff
14 ms
font
23 ms
kapferer.ch 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
kapferer.ch best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
kapferer.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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kapferer.ch can be misinterpreted by Google and other search engines. Our service has detected that English 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 Kapferer.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.
kapferer.ch
Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: