7.5 sec in total
892 ms
6.3 sec
333 ms
Click here to check amazing E Food content for Japan. Otherwise, check out these important facts you probably never knew about e-food.jp
郷土料理の魅力を満載。食を通じた日本と世界の相互理解・地域活性化・健康的な食事の啓蒙等を目指す「世界の料理 総合情報サイト」。食文化を学ぶために役立つ情報をお届けします。
Visit e-food.jpWe analyzed E-food.jp page load time and found that the first response time was 892 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
e-food.jp performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value6.4 s
9/100
25%
Value12.0 s
4/100
10%
Value7,770 ms
0/100
30%
Value0.037
100/100
15%
Value23.6 s
1/100
10%
892 ms
718 ms
541 ms
31 ms
32 ms
Our browser made a total of 176 requests to load all elements on the main page. We found that 30% of them (52 requests) were addressed to the original E-food.jp, 13% (22 requests) were made to Scontent-iad3-1.xx.fbcdn.net and 11% (20 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain E-food.jp.
Page size can be reduced by 399.8 kB (19%)
2.1 MB
1.7 MB
In fact, the total size of E-food.jp main page is 2.1 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 32.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. 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 32.3 kB or 74% of the original size.
Potential reduce by 29.9 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 Food images are well optimized though.
Potential reduce by 315.8 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 315.8 kB or 61% of the original size.
Potential reduce by 21.8 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-food.jp needs all CSS files to be minified and compressed as it can save up to 21.8 kB or 70% of the original size.
Number of requests can be reduced by 89 (52%)
170
81
The browser has sent 170 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E Food. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 57 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
e-food.jp
892 ms
styletop.css
718 ms
gfdynamicfeedcontrol.css
541 ms
31 ms
gfdynamicfeedcontrol.js
32 ms
jquery-1.7.1.js
1617 ms
whatsnew.js
371 ms
whatsnewtop.js
572 ms
respond.js
530 ms
count.js
554 ms
gfdynamicfeedcontrol.js
25 ms
show_ads.js
5 ms
element.js
49 ms
bodyback.jpg
178 ms
12 ms
default+en.css
2 ms
default+en.I.js
4 ms
ga.js
41 ms
logo_e-foodjp.jpg
354 ms
195 ms
banner_renew.jpg
193 ms
banner_nydocumentary.jpg
394 ms
banner_milanoexpo.jpg
365 ms
logo_whatsnew.jpg
195 ms
p_lis018.gif
192 ms
image_trs.gif
395 ms
image_map.gif
364 ms
rss.png
394 ms
facebook.png
622 ms
twitter.png
583 ms
banner_mailmagazine.jpg
590 ms
banner_flagbento.jpg
639 ms
banner_japanesefood.jpg
638 ms
banner_ethnic.jpg
639 ms
banner_silkroad.jpg
772 ms
yahoo.gif
759 ms
ippin_logo_tagline_small.jpg
751 ms
poweredby_FFFFFF.gif
26 ms
ca-pub-0709369671751755.js
93 ms
zrt_lookup.html
52 ms
show_ads_impl.js
51 ms
efoodjpslider.html
825 ms
__utm.gif
49 ms
branding.css
56 ms
ads
382 ms
osd.js
4 ms
ads
301 ms
ads
286 ms
icon_button.gif
829 ms
ads
266 ms
translateelement.css
51 ms
main.js
77 ms
ads
216 ms
plusone.js
129 ms
widgets.js
95 ms
element_main.js
40 ms
ads
163 ms
footer_back.jpg
563 ms
sdk.js
343 ms
translate_24dp.png
133 ms
l
56 ms
cleardot.gif
108 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
254 ms
te_ctrl3.gif
54 ms
cb=gapi.loaded_0
56 ms
cb=gapi.loaded_1
127 ms
fastbutton
159 ms
googlelogo_color_68x28dp.png
84 ms
loading.gif
83 ms
abg.js
160 ms
css
284 ms
m_js_controller.js
170 ms
googlelogo_color_112x36dp.png
146 ms
3784097529959671136
254 ms
te_bk.gif
89 ms
postmessageRelay
216 ms
cb=gapi.loaded_0
154 ms
cb=gapi.loaded_1
154 ms
s
116 ms
x_button_blue2.png
112 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
250 ms
syndication
202 ms
334249230749270016
317 ms
217 ms
xd_arbiter.php
232 ms
xd_arbiter.php
460 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
33 ms
favicon
1426 ms
nessie_icon_tiamat_white.png
17 ms
api.js
96 ms
core:rpc:shindig.random:shindig.sha1.js
142 ms
2536007149-postmessagerelay.js
134 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
125 ms
default.css
181 ms
pascal.css
184 ms
orman.css
185 ms
nivo-slider.css
197 ms
style.css
195 ms
jquery-1.7.1.min.js
696 ms
jquery.nivo.slider.pack.js
362 ms
imagetop.jpg
543 ms
image1.jpg
541 ms
image2.jpg
374 ms
image3.jpg
778 ms
image4.jpg
716 ms
image5.jpg
555 ms
image6.jpg
721 ms
image7.jpg
1259 ms
image8.jpg
923 ms
image9.jpg
880 ms
image10.jpg
1241 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
32 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
101 ms
loading.gif
707 ms
1bedge8r_normal.jpg
103 ms
jot
22 ms
activeview
13 ms
arrows.png
180 ms
bullets.png
181 ms
Gfeeds
388 ms
Gfeeds
45 ms
Gfeeds
622 ms
Gfeeds
236 ms
Gfeeds
197 ms
Gfeeds
394 ms
Gfeeds
477 ms
Gfeeds
386 ms
Gfeeds
478 ms
Gfeeds
475 ms
page.php
290 ms
0195_heart.png
269 ms
8iic-uk7e48.css
292 ms
wh6BEp31KPV.css
360 ms
PcbHa7iOOh9.css
431 ms
LLJ7pJgsgEx.css
502 ms
2SXpl0N3InK.css
501 ms
_rx8naC75Dy.js
628 ms
t-KLv3gqZy0.js
503 ms
uLtKx7ldlvR.js
668 ms
xoyOB9tkUFt.js
502 ms
wFYNJ9lyaMJ.js
696 ms
Xs81m_2832G.js
705 ms
wyIfBc7KBcg.js
704 ms
319800_374298862620270_1328452965_n.jpg
163 ms
safe_image.php
689 ms
12647060_1102213573162125_7339393850918005804_n.jpg
160 ms
12141712_426358304217965_1368079071057343663_n.jpg
168 ms
12143129_439535022915163_5637100293605366074_n.jpg
167 ms
11230968_798972826884702_8218104013046247445_n.jpg
166 ms
10665817_1472965846296768_2338177791759533570_n.jpg
169 ms
12742597_1534591916838271_3026702014427972458_n.jpg
163 ms
10363379_257587661092475_1510761408368216278_n.jpg
169 ms
12524016_1697347310477328_9181895691077407496_n.jpg
170 ms
298238_10200380983779480_705329306_n.jpg
174 ms
12241787_1658013467788524_8953974777960856365_n.jpg
173 ms
1240044_435531163231607_1314338150_n.jpg
173 ms
10354686_10150004552801856_220367501106153455_n.jpg
170 ms
11071945_10207109052113119_7152716533523826723_n.jpg
173 ms
424336_126394117506414_926046554_n.jpg
174 ms
1935077_1111722488877900_675607121547125794_n.jpg
388 ms
12141658_1111722575544558_5947560940639556672_n.jpg
194 ms
12803040_1111722645544551_4417013741726108033_n.jpg
278 ms
12801203_1111722778877871_5707274217752067541_n.jpg
228 ms
10334369_1109687942414688_2798337037605562482_n.jpg
498 ms
10258719_971355976233350_1232806785511920050_o.jpg
173 ms
12733402_1108482839201865_2600071285365633187_n.jpg
429 ms
wL6VQj7Ab77.png
147 ms
CSXXCvknpgK.png
147 ms
7NEHk19WerA.png
147 ms
lRyN50VcaFW.js
84 ms
activeview
23 ms
R9a_DtVRZgv.js
69 ms
cUDgRFxaoIk.js
69 ms
0JBr1QHp8Gi.js
69 ms
kDOzhTr2W91.js
70 ms
ui
14 ms
e-food.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
e-food.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
e-food.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
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-food.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 E-food.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.
e-food.jp
Open Graph description is not detected on the main page of E Food. 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: