7.4 sec in total
1.2 sec
6 sec
170 ms
Visit koenigsbanner.de now to see the best up-to-date Koenigsbanner content for Germany and also check out these interesting facts you probably never knew about koenigsbanner.de
Shop powered by PrestaShop
Visit koenigsbanner.deWe analyzed Koenigsbanner.de page load time and found that the first response time was 1.2 sec and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
koenigsbanner.de performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value5.4 s
20/100
25%
Value6.1 s
45/100
10%
Value80 ms
99/100
30%
Value0.148
76/100
15%
Value6.5 s
59/100
10%
1217 ms
195 ms
475 ms
283 ms
284 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 61% of them (25 requests) were addressed to the original Koenigsbanner.de, 24% (10 requests) were made to Sw-assets.ekomiapps.de and 7% (3 requests) were made to Smart-widget-assets.ekomiapps.de. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Koenigsbanner.de.
Page size can be reduced by 33.1 kB (10%)
322.5 kB
289.4 kB
In fact, the total size of Koenigsbanner.de main page is 322.5 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. 35% of websites need less resources to load. Javascripts take 119.1 kB which makes up the majority of the site volume.
Potential reduce by 31.0 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 31.0 kB or 74% of the original size.
Potential reduce by 840 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. Koenigsbanner images are well optimized though.
Potential reduce by 654 B
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.
Potential reduce by 647 B
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. Koenigsbanner.de has all CSS files already compressed.
Number of requests can be reduced by 8 (33%)
24
16
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Koenigsbanner. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.koenigsbanner.de
1217 ms
v_87_3c1a7aac812a2cb9185d47efa2714b76_all.css
195 ms
v_72_a62acfe61883854e534cbbba62954908.js
475 ms
ptmfix.css
283 ms
custommaker.css
284 ms
customuser.css
286 ms
js
25 ms
koenigsbanner-logo-1449607727.jpg
100 ms
logo.png
400 ms
de_seal_*%7Cseal_type%7C*-105.png
884 ms
Made-in-Germany_web.png
203 ms
f8ef76dbc8448192bec74dc8dbbb6ea37f3be128_premium-qualitaet-deutschland-400x250.jpg
203 ms
c982b87a914f3334f894a45694268edf26fb55c9_flaggewindjpg
205 ms
e40d922cecf227ec571c30c98befdca08e8d23e8_kundenbilder-hier-01png
107 ms
6ad65f76446b3a68bd64258a13eeeba8cff84534_mcp-hawkpng
388 ms
931208ff5688eb901eaf88a2f0076c40840a530f_individuelle-bestellung-02png
275 ms
eKomi-logo1.png
298 ms
qstart.png
109 ms
qend.png
110 ms
%7B%7Bstars-grey-129x24%7D%7D
1511 ms
%7B%7Bstars-yellow-129x24%7D%7D
1442 ms
%7B%7Bqbg%7D%7D
1455 ms
fontawesome-webfont.woff
476 ms
widget.js
82 ms
%7B%7BLato-Light-woff%7D%7D
1473 ms
%7B%7BLato-Bold-woff%7D%7D
1627 ms
X9E9A8A19B531B0D8640EB3BE7DDA43DF.js
388 ms
x-widget.js
17 ms
jquery.min.js
2 ms
sf1408575f50fe2fccca0.json
390 ms
widget.css
3 ms
140857_seller_summary.json
385 ms
stars-grey-129x24.png
13 ms
stars-yellow-129x24.png
16 ms
qbg.png
15 ms
de_seal_gold-105.png
3 ms
%7B%7BLato-Light-ttf%7D%7D
905 ms
%7B%7BLato-Bold-ttf%7D%7D
907 ms
%7B%7BLato-Light-svg%7D%7D
901 ms
%7B%7BLato-Bold-svg%7D%7D
898 ms
bx_loader.gif
316 ms
koenigsbanner.de 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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
koenigsbanner.de 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
koenigsbanner.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Koenigsbanner.de 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 Koenigsbanner.de 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.
koenigsbanner.de
Open Graph description is not detected on the main page of Koenigsbanner. 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: