8.5 sec in total
598 ms
6.5 sec
1.4 sec
Welcome to e-ninniku.com homepage info - get ready to check E Ninniku best content for Japan right away, or after learning these important things about e-ninniku.com
にんにく、熟成黒にんにく、青森県産にんにくの通販販売なら青森県田子町から産地直送の岡崎屋!モンドセレクション12年連続受賞! 10,800円以上で【全国送料無料】
Visit e-ninniku.comWe analyzed E-ninniku.com page load time and found that the first response time was 598 ms and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
e-ninniku.com performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value13.0 s
0/100
25%
Value17.1 s
0/100
10%
Value1,800 ms
9/100
30%
Value0.546
13/100
15%
Value23.1 s
1/100
10%
598 ms
1300 ms
1277 ms
54 ms
441 ms
Our browser made a total of 131 requests to load all elements on the main page. We found that 54% of them (71 requests) were addressed to the original E-ninniku.com, 5% (7 requests) were made to Apis.google.com and 5% (7 requests) were made to I.yimg.jp. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain E-ninniku.com.
Page size can be reduced by 331.8 kB (21%)
1.6 MB
1.2 MB
In fact, the total size of E-ninniku.com main page is 1.6 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. 50% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 77.7 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 14.5 kB, which is 14% 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 77.7 kB or 77% of the original size.
Potential reduce by 90.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 Ninniku images are well optimized though.
Potential reduce by 157.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 157.5 kB or 58% of the original size.
Potential reduce by 5.9 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-ninniku.com needs all CSS files to be minified and compressed as it can save up to 5.9 kB or 77% of the original size.
Number of requests can be reduced by 58 (46%)
125
67
The browser has sent 125 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E Ninniku. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and as a result speed up the page load time.
e-ninniku.com
598 ms
www.e-ninniku.com
1300 ms
CSScriptLib.js
1277 ms
plusone.js
54 ms
l.j
441 ms
widgets.js
4 ms
bookmark_button.js
351 ms
conversion.js
17 ms
index.js
369 ms
cb=gapi.loaded_0
112 ms
addmy_btn.gif
697 ms
button-only.gif
333 ms
006c75a92ba244c6b4cbe2709aa17d7b.gif
1066 ms
Logo_40wht.gif
64 ms
tl.php
413 ms
tfg.gif
618 ms
top2012.jpg
653 ms
cart2012_016.jpg
327 ms
topja.gif
760 ms
menu_1.jpg
597 ms
menu_pro1.jpg
578 ms
menu_hiba1.jpg
592 ms
menu_ca1.jpg
454 ms
menu_history1.jpg
650 ms
menu_seibun1.jpg
743 ms
menu_junkuro2.jpg
763 ms
menu_saibai1.jpg
766 ms
menu_recipe1.jpg
837 ms
menu_sagase.jpg
813 ms
menu_qa1.jpg
903 ms
menu_kita.jpg
929 ms
menu_blog1.jpg
931 ms
space5_40.gif
938 ms
thanks.jpg
979 ms
40banner_top.jpg
1207 ms
top_home_kochira.jpg
1217 ms
top_gyomu.jpg
1262 ms
top_hiba.jpg
1260 ms
sanks.jpg
1595 ms
hatake0610.gif
1468 ms
brix.jpg
2096 ms
top_takko_map.jpg
1384 ms
wakansanzai.jpg
1749 ms
point.gif
1438 ms
topranking0703.gif
1550 ms
top_rank1.gif
1607 ms
40sninki2.jpg
1645 ms
top_rank2.gif
1711 ms
yoyaku0704.gif
1767 ms
6tokusen_l.jpeg
1777 ms
top_rank3.gif
1795 ms
yjapan_logo_110_29.gif
691 ms
s_btn_web.gif
711 ms
s_b.gif
716 ms
s_i.gif
724 ms
s_d.gif
730 ms
2s_nama.jpg
1866 ms
ga.js
73 ms
x.gif
299 ms
l7.f
592 ms
ts.gif
371 ms
like.php
237 ms
82 ms
__utm.gif
47 ms
top_rank4.gif
1603 ms
386 ms
vpc6VNjRPXV.js
78 ms
LVx-xkvaJ0b.png
81 ms
uh.js
519 ms
7b6eab0f.js
1077 ms
30 ms
44 ms
34 ms
07s_jyo_tokudai.jpg
1495 ms
top_rank5.gif
1388 ms
13s_muki.jpg
1381 ms
top_rank6.gif
1458 ms
10s_nami.jpg
1452 ms
top_rank7.gif
1472 ms
reset.css
11 ms
entry-button.css
12 ms
bbtn-s_v3.png
8 ms
5tokusen2l.jpeg
1394 ms
top_rank8.gif
1383 ms
41jas.jpg
1460 ms
top_rank9.gif
1506 ms
17s_curry.jpg
1482 ms
top_rank10.gif
1456 ms
14s_otameshi2_2.jpg
1405 ms
toiawase.jpg
1787 ms
kesai.gif
1456 ms
card_s2_all.gif
1504 ms
convini_ok_s.jpg
1485 ms
jnb_jfuri_logo88x31.gif
1285 ms
tag.js
193 ms
analytics.js
21 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
46 ms
cb=gapi.loaded_1
27 ms
fastbutton
100 ms
collect
19 ms
postmessageRelay
67 ms
collect
82 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
16 ms
cb=gapi.loaded_0
31 ms
cb=gapi.loaded_1
25 ms
api.js
44 ms
core:rpc:shindig.random:shindig.sha1.js
95 ms
2536007149-postmessagerelay.js
93 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
116 ms
tag
24 ms
jot
95 ms
trackfeedbargreen.gif
406 ms
oct.js
7 ms
ya.js
341 ms
menu_2.jpg
175 ms
menu_pro2.jpg
194 ms
menu_hiba2.jpg
176 ms
menu_kitatu2.jpg
175 ms
menu_ca2.jpg
173 ms
menu_history2.jpg
176 ms
menu_seibun2.jpg
336 ms
menu_junkuro1.jpg
343 ms
menu_saibai2.jpg
345 ms
menu_recipe2.jpg
345 ms
menu_sagase2.jpg
350 ms
menu_qa2.jpg
384 ms
menu_blog2.jpg
499 ms
adsct
92 ms
adsct
124 ms
pb.js
189 ms
321 ms
e-ninniku.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
e-ninniku.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
e-ninniku.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
X-SJIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-ninniku.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-ninniku.com main page’s claimed encoding is x-sjis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
e-ninniku.com
Open Graph description is not detected on the main page of E Ninniku. 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: