3.4 sec in total
299 ms
2.8 sec
289 ms
Visit ekalog.de now to see the best up-to-date Ekalog content for Germany and also check out these interesting facts you probably never knew about ekalog.de
This website is for sale! ekalog.de is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, ekalog.de has it all...
Visit ekalog.deWe analyzed Ekalog.de page load time and found that the first response time was 299 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
ekalog.de performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value7.5 s
4/100
25%
Value7.3 s
29/100
10%
Value720 ms
41/100
30%
Value0.001
100/100
15%
Value8.6 s
37/100
10%
299 ms
325 ms
103 ms
104 ms
32 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 49% of them (26 requests) were addressed to the original Ekalog.de, 6% (3 requests) were made to Googleadservices.com and 6% (3 requests) were made to 104.cdn.ekalog.de. The less responsive or slowest element that took the longest time to load (806 ms) belongs to the original domain Ekalog.de.
Page size can be reduced by 144.1 kB (24%)
610.8 kB
466.7 kB
In fact, the total size of Ekalog.de main page is 610.8 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. 30% of websites need less resources to load. Images take 413.1 kB which makes up the majority of the site volume.
Potential reduce by 41.9 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 41.9 kB or 78% of the original size.
Potential reduce by 22.4 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. Ekalog images are well optimized though.
Potential reduce by 67.9 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 67.9 kB or 52% of the original size.
Potential reduce by 11.9 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. Ekalog.de needs all CSS files to be minified and compressed as it can save up to 11.9 kB or 81% of the original size.
Number of requests can be reduced by 19 (41%)
46
27
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ekalog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
ekalog.de
299 ms
www.ekalog.de
325 ms
main-div.css
103 ms
plusone.js
104 ms
conversion.js
32 ms
print-beitrag.css
104 ms
cb=gapi.loaded_0
36 ms
ga.js
54 ms
logo_grey.png
411 ms
facebook24x24.gif
346 ms
twitter24x24.gif
302 ms
nl_archiv_orange.png
346 ms
sosnowski_klein.jpg
302 ms
button_meinungen.png
296 ms
71 ms
piwik.js
478 ms
pxl.php
294 ms
twitter2.gif
284 ms
header-right-newsletter.png
286 ms
79 ms
rss.gif
330 ms
thullmann_klein.jpg
294 ms
siegel-einkauf.png
326 ms
ico_arrow.gif
326 ms
navi3.gif
167 ms
navi1.png
210 ms
navi2.png
212 ms
background-sidebar.gif
214 ms
einkauf-normal.png
214 ms
energie-normal.png
216 ms
rohstoff-normal.png
267 ms
globaler-normal.png
309 ms
logistik-normal.png
312 ms
fuhrpark-normal.png
316 ms
search-button-blue.gif
316 ms
line.gif
322 ms
rss.gif
366 ms
start.jpg
607 ms
einkauf.jpg
613 ms
energie.jpg
620 ms
rohstoff.jpg
621 ms
stahl.jpg
627 ms
globaler.jpg
565 ms
logistik.jpg
769 ms
fuhrpark.jpg
806 ms
hg_footer.png
714 ms
__utm.gif
14 ms
29 ms
25 ms
32 ms
25 ms
count.js
410 ms
count.js
378 ms
ekalog.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.
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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
ekalog.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
Missing source maps for large first-party JavaScript
ekalog.de 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 Ekalog.de 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 Ekalog.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.
ekalog.de
Open Graph description is not detected on the main page of Ekalog. 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: