6.2 sec in total
1.3 sec
4.6 sec
279 ms
Click here to check amazing EHEIM content for Japan. Otherwise, check out these important facts you probably never knew about eheim.jp
エーハイムはドイツの観賞魚用器具メーカーです。観賞魚の水槽システムのフィルターの製造・販売を行っており、各種水槽サイズに対応した多くのラインナップをご用意しています。
Visit eheim.jpWe analyzed Eheim.jp page load time and found that the first response time was 1.3 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
eheim.jp performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value6.9 s
6/100
25%
Value11.4 s
5/100
10%
Value170 ms
93/100
30%
Value0.168
71/100
15%
Value6.0 s
64/100
10%
1300 ms
523 ms
523 ms
722 ms
375 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 94% of them (50 requests) were addressed to the original Eheim.jp, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Eheim.jp.
Page size can be reduced by 279.1 kB (12%)
2.3 MB
2.0 MB
In fact, the total size of Eheim.jp main page is 2.3 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. 35% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 22.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. This page needs HTML code to be minified as it can gain 6.7 kB, which is 25% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 22.3 kB or 82% of the original size.
Potential reduce by 5.2 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 207.5 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 207.5 kB or 72% of the original size.
Potential reduce by 44.0 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.jp needs all CSS files to be minified and compressed as it can save up to 44.0 kB or 82% of the original size.
Number of requests can be reduced by 12 (24%)
51
39
The browser has sent 51 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 JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.eheim.jp
1300 ms
common.css
523 ms
style.css
523 ms
original.css
722 ms
nivo-slider.css
375 ms
light.css
377 ms
jquery.fancybox.css
563 ms
flexslider.css
566 ms
jquery.js
975 ms
jquery-migrate.min.js
692 ms
jquery.nivo.slider.pack.js
692 ms
jquery.fancybox.js
1121 ms
jquery.flexslider.js
1132 ms
script.js
1037 ms
analytics.js
46 ms
body_bg.jpg
330 ms
logo.jpg
191 ms
headnavi_home_off.jpg
182 ms
headnavi_products_off.jpg
189 ms
icon_headnavi.jpg
174 ms
headnavi_shopinfo_off.jpg
176 ms
headnavi_faq_off.jpg
348 ms
headnavi_company_off.jpg
349 ms
headnavi_contact_off.jpg
361 ms
visual01.jpg
1313 ms
visual02.jpg
1136 ms
visual03.jpg
1154 ms
visual04.jpg
1213 ms
bg_main.jpg
522 ms
title_top_guide.png
543 ms
main_2213-90x90.jpg
695 ms
icon_more.jpg
723 ms
main_2234-90x100.jpg
868 ms
main_2073-90x90.jpg
905 ms
main_1048-90x90.jpg
1041 ms
img_filterpad-90x90.jpg
1085 ms
title_top_news.png
1214 ms
bg_top_new.png
1266 ms
bg_top_campaign.png
1326 ms
bg_top_other.png
1318 ms
originator_filter_05.jpg
1385 ms
bnr_search.jpg
1389 ms
bnr_campaign.jpg
1446 ms
bnr_filter_instraction.jpg
1499 ms
bnr_interview.jpg
1482 ms
bnr_caution.jpg
1513 ms
bnr_originator_filter.jpg
1558 ms
bnr_users_voice_top.jpg
1559 ms
bnr_my_aqua_pride.jpg
1627 ms
bnr_parts.jpg
1646 ms
icon_totop.png
1685 ms
collect
11 ms
collect
65 ms
eheim.jp 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
Links do not have a discernible name
eheim.jp 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
eheim.jp SEO score
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eheim.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Eheim.jp 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.jp
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: