4.2 sec in total
309 ms
3.8 sec
89 ms
Welcome to eheim.de homepage info - get ready to check EHEIM best content right away, or after learning these important things about eheim.de
Visit eheim.deWe analyzed Eheim.de page load time and found that the first response time was 309 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
eheim.de performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value9.9 s
0/100
25%
Value13.7 s
2/100
10%
Value380 ms
70/100
30%
Value0.283
43/100
15%
Value11.0 s
21/100
10%
309 ms
267 ms
475 ms
326 ms
329 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Eheim.de, 96% (46 requests) were made to Eheim.com and 2% (1 request) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Eheim.com.
Page size can be reduced by 234.1 kB (29%)
812.7 kB
578.6 kB
In fact, the total size of Eheim.de main page is 812.7 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. 50% of websites need less resources to load. Javascripts take 306.8 kB which makes up the majority of the site volume.
Potential reduce by 214.4 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 214.4 kB or 91% of the original size.
Potential reduce by 18.9 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. Obviously, EHEIM needs image optimization as it can save up to 18.9 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 12 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 768 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. Eheim.de has all CSS files already compressed.
We found no issues to fix!
30
30
The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EHEIM. According to our analytics all requests are already optimized.
eheim.de
309 ms
267 ms
1714031729_be5d2d2b44ea56134566bfd767cddb8e.css
475 ms
wishlist.svg
326 ms
basket.svg
329 ms
1.jpg
432 ms
2.jpg
435 ms
Wifi_242x228.png
435 ms
icon9.png
434 ms
3.jpg
632 ms
teaser_gartenteich.png
632 ms
icon11.png
633 ms
icon7.png
633 ms
Icons_Ratgeber_Licht.jpg
634 ms
icon16.png
634 ms
icon29.png
653 ms
icon30.png
652 ms
Media-Center_110x100_0620.svg
980 ms
Servicestellen_0620.svg
882 ms
icon19.png
552 ms
Icon_barcode_0813.jpg
587 ms
icon35.png
659 ms
js
70 ms
1714031729_be5d2d2b44ea56134566bfd767cddb8e.js
994 ms
10_years.svg
657 ms
service_hotline.svg
690 ms
adv-3.svg
1088 ms
adv-4.svg
1100 ms
eheim_logo.png
799 ms
gb.png
473 ms
montserrat-medium.woff
469 ms
montserrat-regular.woff
458 ms
montserrat-light.woff
517 ms
montserrat-extralight.woff
570 ms
montserrat-thin.woff
576 ms
montserrat-semibold.woff
581 ms
montserrat-extrabold.woff
608 ms
montserrat-bold.woff
676 ms
montserrat-black.woff
683 ms
OpenSans-Regular.woff
697 ms
OpenSans-Light.woff
698 ms
OpenSans-Semibold.woff
717 ms
OpenSans-Bold.woff
784 ms
OpenSans-ExtraBold.woff
790 ms
fontawesome-webfont.woff
802 ms
shopware.woff
802 ms
123 ms
130 ms
eheim.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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
eheim.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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
eheim.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eheim.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Eheim.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.
eheim.de
Open Graph description is not detected on the main page of EHEIM. 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: