5.1 sec in total
549 ms
4.4 sec
163 ms
Click here to check amazing Eingedi content. Otherwise, check out these important facts you probably never knew about eingedi.jp
Visit eingedi.jpWe analyzed Eingedi.jp page load time and found that the first response time was 549 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
eingedi.jp performance score
549 ms
1302 ms
339 ms
346 ms
349 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 97% of them (63 requests) were addressed to the original Eingedi.jp, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Eingedi.jp.
Page size can be reduced by 126.7 kB (21%)
603.4 kB
476.7 kB
In fact, the total size of Eingedi.jp main page is 603.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. 25% of websites need less resources to load. Images take 417.4 kB which makes up the majority of the site volume.
Potential reduce by 7.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. This page needs HTML code to be minified as it can gain 1.6 kB, which is 15% 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 7.9 kB or 73% of the original size.
Potential reduce by 1.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. Eingedi images are well optimized though.
Potential reduce by 71.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 71.5 kB or 60% of the original size.
Potential reduce by 46.2 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. Eingedi.jp needs all CSS files to be minified and compressed as it can save up to 46.2 kB or 83% of the original size.
Number of requests can be reduced by 28 (44%)
63
35
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eingedi. 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 13 to 1 for CSS and as a result speed up the page load time.
eingedi.jp
549 ms
www.eingedi.jp
1302 ms
import.css
339 ms
default.css
346 ms
module.css
349 ms
style.css
521 ms
css.js
520 ms
navi.js
370 ms
win_op.js
505 ms
site.js
517 ms
minmax.js
521 ms
rollover.js
553 ms
scrollsmoothly.js
674 ms
jquery-1.4.2.min.js
1034 ms
set.css
357 ms
common.css
358 ms
contents.css
530 ms
table.css
403 ms
bloc.css
506 ms
bloc_alpha.css
534 ms
popup_import.css
531 ms
print.css
588 ms
popup.css
183 ms
ga.js
56 ms
bg_header.png
188 ms
bg_logo.png
288 ms
img_logo.gif
282 ms
hnav_login.jpg
284 ms
hnav_account.jpg
285 ms
hnav_cart.jpg
284 ms
hnav_home.jpg
366 ms
hnav_sitemap.jpg
449 ms
nav_deadsea.gif
469 ms
nav_israel.gif
458 ms
nav_eingedi.gif
458 ms
nav_lineup.gif
458 ms
bg_topside.jpg
538 ms
bnr_deadsea.jpg
625 ms
bnr_israel.jpg
630 ms
bnr_eingedi.jpg
632 ms
img_mainimage_01.jpg
987 ms
img_mainimage_02.jpg
1019 ms
img_mainimage_03.jpg
1055 ms
bg_contents.png
799 ms
bg_contents_inner.png
804 ms
sttl_news.gif
804 ms
btn_more.gif
967 ms
icon_cat_news.gif
976 ms
bg_toplineup.jpg
977 ms
sttl_lineup.gif
1155 ms
img_lineup_01.jpg
1168 ms
btn_detail.gif
1157 ms
img_top_product.jpg
1184 ms
img_copyright.gif
1198 ms
__utm.gif
13 ms
hnav_login_o.jpg
178 ms
hnav_account_o.jpg
176 ms
hnav_cart_o.jpg
171 ms
hnav_home_o.jpg
187 ms
hnav_sitemap_o.jpg
175 ms
nav_deadsea_o.gif
177 ms
nav_israel_o.gif
339 ms
nav_eingedi_o.gif
350 ms
nav_lineup_o.gif
349 ms
btn_more_o.gif
350 ms
eingedi.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eingedi.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 Eingedi.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.
eingedi.jp
Open Graph description is not detected on the main page of Eingedi. 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: