3.5 sec in total
304 ms
3 sec
238 ms
Visit kruegerrand.de now to see the best up-to-date Kruegerrand content for Germany and also check out these interesting facts you probably never knew about kruegerrand.de
Im ESG Krügerrand-Shop finden Sie aktuelle Preise für Ankauf / Verkauf sowie wissenswertes über die Anlagegoldmünze Krügerrand / Krugerrand
Visit kruegerrand.deWe analyzed Kruegerrand.de page load time and found that the first response time was 304 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
kruegerrand.de performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value6.6 s
8/100
25%
Value7.0 s
32/100
10%
Value120 ms
97/100
30%
Value0.002
100/100
15%
Value6.3 s
60/100
10%
304 ms
885 ms
288 ms
297 ms
199 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 87% of them (34 requests) were addressed to the original Kruegerrand.de, 5% (2 requests) were made to Google-analytics.com and 5% (2 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (885 ms) belongs to the original domain Kruegerrand.de.
Page size can be reduced by 166.1 kB (32%)
524.4 kB
358.3 kB
In fact, the total size of Kruegerrand.de main page is 524.4 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. Images take 290.3 kB which makes up the majority of the site volume.
Potential reduce by 12.3 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 12.3 kB or 72% of the original size.
Potential reduce by 3.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. Kruegerrand images are well optimized though.
Potential reduce by 109.8 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 109.8 kB or 65% of the original size.
Potential reduce by 40.4 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. Kruegerrand.de needs all CSS files to be minified and compressed as it can save up to 40.4 kB or 82% of the original size.
Number of requests can be reduced by 14 (38%)
37
23
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kruegerrand. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
kruegerrand.de
304 ms
www.kruegerrand.de
885 ms
stylesheet_3ed979fd76.css
288 ms
slightbox.css
297 ms
columns.css
199 ms
prototype.1.7.0.yui.js
691 ms
scriptaculous.js
297 ms
lightbox.2.0.5.yui.js
299 ms
default.js
298 ms
javascript_0b12553063.js
383 ms
original.css
592 ms
additional.css
436 ms
header.css
316 ms
builder.js
107 ms
effects.js
300 ms
ipad.css
102 ms
ga.js
38 ms
header-bg.gif
379 ms
Kruegerrand.png
116 ms
sprite.png
672 ms
f3cef74214.jpg
398 ms
b59aba28da.jpg
371 ms
df10b15f12.jpg
549 ms
d81964a2ed.jpg
294 ms
9a7cbe5c48.jpg
455 ms
Kruegerrand_01.jpg
812 ms
detail10_small.jpg
517 ms
detail11_small.jpg
518 ms
detail12_small.jpg
557 ms
detail13_small.jpg
630 ms
87609f66de.jpg
821 ms
68e75c5b31.jpg
786 ms
bb3c9c2c70.jpg
658 ms
footer-building.jpg
735 ms
listBullet.gif
761 ms
__utm.gif
12 ms
like.php
144 ms
qeKvIRsJabD.js
41 ms
LVx-xkvaJ0b.png
27 ms
kruegerrand.de 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
kruegerrand.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
kruegerrand.de SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
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 Kruegerrand.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 Kruegerrand.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.
kruegerrand.de
Open Graph description is not detected on the main page of Kruegerrand. 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: