12.2 sec in total
1.5 sec
10.3 sec
448 ms
Welcome to e-dashi.com homepage info - get ready to check E Dashi best content for Japan right away, or after learning these important things about e-dashi.com
Visit e-dashi.comWe analyzed E-dashi.com page load time and found that the first response time was 1.5 sec and then it took 10.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
e-dashi.com performance score
name
value
score
weighting
Value7.8 s
0/100
10%
Value10.0 s
0/100
25%
Value25.6 s
0/100
10%
Value500 ms
58/100
30%
Value0.602
10/100
15%
Value19.3 s
2/100
10%
1489 ms
482 ms
350 ms
927 ms
405 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 86% of them (89 requests) were addressed to the original E-dashi.com, 13% (13 requests) were made to Ajax.googleapis.com and 1% (1 request) were made to Badge.facebook.com. The less responsive or slowest element that took the longest time to load (4.4 sec) belongs to the original domain E-dashi.com.
Page size can be reduced by 260.1 kB (17%)
1.5 MB
1.2 MB
In fact, the total size of E-dashi.com main page is 1.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 1.2 MB which makes up the majority of the site volume.
Potential reduce by 24.6 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 9.0 kB, which is 30% 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 24.6 kB or 80% of the original size.
Potential reduce by 44.7 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. E Dashi images are well optimized though.
Potential reduce by 154.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 154.5 kB or 68% of the original size.
Potential reduce by 36.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. E-dashi.com needs all CSS files to be minified and compressed as it can save up to 36.2 kB or 83% of the original size.
Number of requests can be reduced by 28 (27%)
102
74
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E Dashi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
e-dashi.com
1489 ms
style.css
482 ms
openwin.js
350 ms
CSScriptLib.js
927 ms
default.css
405 ms
light.css
450 ms
dark.css
559 ms
bar.css
670 ms
nivo-slider.css
776 ms
jquery-1.7.1.min.js
1267 ms
jquery.nivo.slider.js
1003 ms
sbc.css
757 ms
jquery.js
1450 ms
jquery-migrate.min.js
911 ms
prototype.js
70 ms
sbc.js
1186 ms
scriptaculous.js
78 ms
builder.js
89 ms
effects.js
98 ms
dragdrop.js
100 ms
slider.js
99 ms
controls.js
97 ms
menu_open.js
1185 ms
popup_selects.js
1240 ms
253510491376878.1929.191358552.png
79 ms
**.jpg
1537 ms
top-banner.jpg
1391 ms
nav-top.gif
1297 ms
nav-ichiran.gif
1306 ms
nav-okaimono.gif
1330 ms
nav-touten.gif
1516 ms
nav-cart.gif
1699 ms
icon-okyaku-koe.jpg
1674 ms
top-tenpo.jpg
2150 ms
kaigai_baner.jpg
1758 ms
katuokezuri_baner.jpg
2046 ms
05.4.25kezurikata4.JPG
2155 ms
karei-baner.jpg
2233 ms
gokuatsukezuri-baner.jpg
2251 ms
matomegai-baner.jpg
2346 ms
top_konbu.gif
2416 ms
top_hidaka.jpg
2704 ms
top_naganekonbu.jpg
2526 ms
top_otoku.jpg
2755 ms
top_saomae.JPG
2805 ms
top_dashi.jpg
2750 ms
t_rausu-mimikonbu.jpg
2928 ms
top_osatube1_top.JPG
3219 ms
05.11.27makonbu_otosibe..JPG
3250 ms
top_makonbu_ishizaki.jpg
3016 ms
top_katuo.gif
2919 ms
honbusi.jpg
3076 ms
top_hanakatuo.jpg
3062 ms
05.6.8souda1.JPG
3203 ms
top_katuko.jpg
2954 ms
top_katuokezuriki1.jpg
2958 ms
top_niboshi.gif
2814 ms
bec.cgi
2816 ms
wariago_nibosi1.gif
3119 ms
top_nibosi.jpg
3126 ms
builder.js
9 ms
effects.js
11 ms
dragdrop.js
10 ms
controls.js
18 ms
slider.js
19 ms
sound.js
20 ms
t_urume.JPG
2981 ms
05.3.29nibosi_aji_top.JPG
2907 ms
nibosi-tai.jpg
2984 ms
top_wariurume.jpg
2742 ms
top_suboshi.gif
2969 ms
top_subosi.jpg
3076 ms
top-subosi1.jpg
2928 ms
top_sasakarei.JPG
3045 ms
top_shiitake.gif
2849 ms
top_juou_kousin.jpg
3118 ms
top_donko.jpg
2798 ms
top_jyoubare.jpg
2793 ms
maitake.jpg
3317 ms
kikurage-.jpg
3039 ms
top_kaisou.gif
2812 ms
okiarame_.jpg
3022 ms
top_itawakame.gif
3155 ms
top_kamojinori.jpg
2939 ms
06.1.23kansounori_HP.JPG
3098 ms
mekabu1.JPG
3207 ms
top_gentei.gif
3009 ms
hosikarei.jpg
3216 ms
ozouni_set.JPG
3097 ms
nita-mochi.jpg
3064 ms
shougatou-naka.JPG
3224 ms
top_kanbutu.gif
2975 ms
top-aokinako.jpg
3184 ms
shougayu2.JPG
3402 ms
shouhin-sobakarin.JPG
3151 ms
credit.gif
3129 ms
toiawase.jpg
3217 ms
kago.gif
3368 ms
space.gif
3510 ms
cal.css
3638 ms
toiawase_adress.jpg
3510 ms
top-main.jpg
4427 ms
style.css
4199 ms
e-dashi.com 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.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
e-dashi.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
e-dashi.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 E-dashi.com 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 E-dashi.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.
e-dashi.com
Open Graph description is not detected on the main page of E Dashi. 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: