8 sec in total
272 ms
7.4 sec
289 ms
Visit eheim.com now to see the best up-to-date EHEIM content for Jordan and also check out these interesting facts you probably never knew about eheim.com
EHEIM is a leading manufacturer of aquariums and aquaristics equipment. Filters, pumps, lighting, fish food and so on. Best quality for more than 55 years.
Visit eheim.comWe analyzed Eheim.com page load time and found that the first response time was 272 ms and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
eheim.com performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value30.4 s
0/100
25%
Value22.4 s
0/100
10%
Value17,370 ms
0/100
30%
Value1.48
0/100
15%
Value27.6 s
0/100
10%
272 ms
312 ms
550 ms
773 ms
102 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 96% of them (68 requests) were addressed to the original Eheim.com, 3% (2 requests) were made to Stats.g.doubleclick.net and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (4.7 sec) belongs to the original domain Eheim.com.
Page size can be reduced by 327.9 kB (13%)
2.5 MB
2.1 MB
In fact, the total size of Eheim.com main page is 2.5 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 62.2 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 62.2 kB or 85% of the original size.
Potential reduce by 153.1 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. EHEIM images are well optimized though.
Potential reduce by 27 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 112.6 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. Eheim.com needs all CSS files to be minified and compressed as it can save up to 112.6 kB or 83% of the original size.
Number of requests can be reduced by 11 (20%)
55
44
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EHEIM. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for CSS and as a result speed up the page load time.
eheim.com
272 ms
www.eheim.com
312 ms
www.eheim.com
550 ms
home
773 ms
en.css
102 ms
reset.css
201 ms
style.css
607 ms
quickfinder.css
303 ms
fish-and-plants.css
301 ms
jquery-ui-1.8.12.custom.css
313 ms
jquery.fancybox.css
316 ms
jquery-1.6.2.min.js
639 ms
jquery-ui-1.8.12.custom.min.js
808 ms
overlay.min.js
399 ms
toolbox.expose.min.js
414 ms
easySlider1.7.js
418 ms
jquery.jcarousel.min.js
608 ms
jquery.ba-hashchange.min.js
515 ms
carousel.js
827 ms
jquery.fancybox.js
626 ms
jquery.validate.min.js
1206 ms
main.js
1047 ms
retailer_map.js
727 ms
body_bg.jpg
332 ms
gtm.js
117 ms
container-border.png
146 ms
logo.png
367 ms
land_small.png
341 ms
dere_grey.png
246 ms
search_bt_grey.png
346 ms
sub_nav_bg-top.png
406 ms
content_bg.gif
443 ms
line3.gif
445 ms
aquastar_54_led.jpg
3470 ms
neu_zubehore_terrastyle.jpg
4408 ms
prof_4_gb_0.jpg
1219 ms
plusx_award_incpiria_en.jpg
2082 ms
nano_terrarien_gb_0.jpg
3370 ms
futter_gb_0815_0.jpg
2375 ms
new_led_gb_1114.jpg
3593 ms
aquarium-app.png
2288 ms
aquarium_guide_new.jpg
2704 ms
guide_marine_aquarium.jpg
2879 ms
guide_light.jpg
3119 ms
link_bg.png
2981 ms
carousel_bg.gif
3082 ms
click.gif
3182 ms
power_cleaner.jpg
3331 ms
thumb-video-futter_1.jpg
3489 ms
interview_mr_eheim.jpg
3637 ms
filter_range.jpg
3587 ms
professionel_3e.jpg
3769 ms
ecco_pro.jpg
3812 ms
substratpro.jpg
4089 ms
autofeeder_automatic_gravel_cleaner.jpg
3905 ms
dc.js
64 ms
helvetica-light-webfont.woff
4010 ms
__utm.gif
12 ms
dere_bg.png
4674 ms
futter_neu_0.jpg
3977 ms
water-plant-care_0.jpg
4475 ms
incpiria_1.jpg
4323 ms
sm_facebook.png
3891 ms
sm_twitter.png
3878 ms
sm_youtube.png
3949 ms
google-play-badge.png
3960 ms
appstore-badge.png
4030 ms
3992 ms
circle.png
3939 ms
dere3.png
3951 ms
username.gif
101 ms
eheim.com 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.com 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.com 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eheim.com 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 Eheim.com 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.com
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: