8.1 sec in total
312 ms
7.5 sec
286 ms
Visit housefoods.jp now to see the best up-to-date Housefoods content for Japan and also check out these interesting facts you probably never knew about housefoods.jp
ハウス食品のホームページへようこそ。ハウス食品は、お客様の食生活と健康に貢献し、食を通じて、家庭の幸せに役立つ企業として「おいしさとやすらぎを」お届けいたします。
Visit housefoods.jpWe analyzed Housefoods.jp page load time and found that the first response time was 312 ms and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
housefoods.jp performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value35.1 s
0/100
25%
Value18.1 s
0/100
10%
Value3,190 ms
2/100
30%
Value0.048
99/100
15%
Value22.0 s
1/100
10%
312 ms
446 ms
299 ms
306 ms
305 ms
Our browser made a total of 216 requests to load all elements on the main page. We found that 98% of them (211 requests) were addressed to the original Housefoods.jp, 2% (4 requests) were made to Assets.adobedtm.com and 0% (1 request) were made to Housefoods.d1.sc.omtrdc.net. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Housefoods.jp.
Page size can be reduced by 1.3 MB (37%)
3.7 MB
2.3 MB
In fact, the total size of Housefoods.jp main page is 3.7 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. 55% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 49.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. 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 49.7 kB or 82% of the original size.
Potential reduce by 51.6 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. Housefoods images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 83% of the original size.
Potential reduce by 187.7 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. Housefoods.jp needs all CSS files to be minified and compressed as it can save up to 187.7 kB or 84% of the original size.
Number of requests can be reduced by 103 (48%)
214
111
The browser has sent 214 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Housefoods. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
housefoods.jp
312 ms
index.html
446 ms
import.css
299 ms
guard.css
306 ms
tvcm_guard.css
305 ms
top_noscript.css
304 ms
jquery.js
447 ms
jqcookie.js
442 ms
interface.js
449 ms
master.js
744 ms
ajax.js
449 ms
inlenq.js
450 ms
jquery-1.3.2.min.js
739 ms
jquery.easing.1.3.js
597 ms
jquery.galleryview-1.1.js
744 ms
jquery.timers-1.1.2.js
599 ms
jquery.tipsy.js
601 ms
top_inc.js
748 ms
smartphone.js
748 ms
satelliteLib-7eef1bdecd23d6503ab20f7ef2f4393cf7cbf755.js
112 ms
default.css
454 ms
layout.css
593 ms
header.css
597 ms
globalnavi.css
599 ms
footer.css
602 ms
localnavi.css
604 ms
container.css
750 ms
ecology.css
741 ms
recipetop.css
745 ms
commonquestion.css
745 ms
csr.css
748 ms
form.css
152 ms
topkv.css
151 ms
body_bg.gif
173 ms
spacer.gif
171 ms
house_logo_l.gif
173 ms
btn_house_group_ovoff.gif
173 ms
head_search_2_ovoff.gif
174 ms
head_search_w_ovoff.gif
173 ms
pc_top_kv.jpg
743 ms
pc_top_kv.jpg
744 ms
pc_top_kv.jpg
1040 ms
pc_top_kv.jpg
896 ms
pc_top_kv.jpg
1040 ms
pc_top_kv.jpg
1044 ms
pc_top_kv_space.gif
893 ms
pc_top_kv.jpg
1045 ms
pc_top_kv.jpg
1193 ms
pc_top_kv_s.jpg
1047 ms
pc_top_kv_s.jpg
1191 ms
pc_top_kv_s.jpg
1191 ms
pc_top_kv_s.jpg
1195 ms
pc_top_kv_s.jpg
1195 ms
pc_top_kv_s.jpg
1198 ms
pc_top_kv_s_space.gif
1341 ms
pc_top_kv_s.jpg
1341 ms
pc_top_kv_s.jpg
1342 ms
bnr_top_main_line.jpg
1346 ms
bnr_top_main02.jpg
1345 ms
bnr_top_main03.jpg
1345 ms
recipe_tit.gif
1491 ms
recipe_tit_btn_ovoff.gif
1492 ms
0.138-103.jpeg
1496 ms
recipe_osusume22.gif
1504 ms
recipe_search_tit.gif
1503 ms
btn-localnavi-search_ovoff.gif
1502 ms
recipe_search_img.gif
1640 ms
icon_rss_ovoff.gif
1643 ms
pc_top_pic_100.jpg
1620 ms
s-code-contents-3184d2156c242153e13d3335a4ac635d007a34c6.js
104 ms
satellite-549d40da3335350015480000.js
111 ms
pc_top_pic_099.jpg
1485 ms
pc_top_pic_020.jpg
1486 ms
pc_top_pic_010.jpg
1483 ms
pc_top_pic.ssi.005.jpg
1627 ms
icon_rcp.gif
1624 ms
maker-win.gif
1603 ms
s43313849093392
10 ms
icon_pro.gif
1062 ms
icon_cm.gif
1061 ms
icon_know.gif
913 ms
icon_rss.gif
1051 ms
ln_tit_products_ovoff.gif
907 ms
ln_products_new_ovoff.gif
907 ms
0.28-22.jpeg
909 ms
0.28-22.jpeg
909 ms
0.28-22.jpeg
907 ms
0.28-22.jpeg
906 ms
0.28-22.jpeg
909 ms
0.28-22.jpeg
909 ms
0.28-22.jpeg
909 ms
0.28-22.jpeg
911 ms
0.28-22.jpeg
908 ms
0.28-22.jpeg
904 ms
0.28-22.jpeg
905 ms
0.28-22.jpeg
904 ms
0.28-22.jpeg
905 ms
0.28-22.jpeg
905 ms
0.28-22.jpeg
908 ms
0.28-22.jpeg
901 ms
0.28-22.jpeg
902 ms
0.28-22.jpeg
899 ms
0.28-22.jpeg
897 ms
0.28-24.jpeg
899 ms
0.28-24.jpeg
900 ms
0.28-24.jpeg
902 ms
0.28-22.jpeg
900 ms
0.28-22.jpeg
899 ms
item_hwf.jpg
903 ms
t_ln_btn_brandsite_ovoff.gif
898 ms
btn_alg_ovoff.gif
899 ms
tvcm_tit.gif
904 ms
tvcm_txt.gif
901 ms
tvcm_btn.gif
900 ms
sinsai_oshirase.jpg
900 ms
bnr_csr_ovoff.jpg
902 ms
group_banner_ovoff.jpg
899 ms
bnr_saiyou_ovoff.jpg
904 ms
bnr_mailmagazine_ovoff.gif
906 ms
bnr_factory_ovoff.gif
905 ms
footnav_products_ovoff.gif
904 ms
footnav_company_ovoff.gif
902 ms
marker-win_foot.gif
904 ms
footnav_group_ovoff.gif
903 ms
footnav_recipe_ovoff.gif
903 ms
footnav_data_ovoff.gif
900 ms
footnav_activity_ovoff.gif
899 ms
footnav_shopping_ovoff.gif
901 ms
footnav_inquiry_ovoff.gif
902 ms
footnav_social_ovoff.gif
905 ms
footnav_line.gif
907 ms
footnav_twitter.gif
907 ms
footnav_facebook.gif
904 ms
footnav_youtube.gif
905 ms
footnav_mobilesite.gif
903 ms
footnav_smartphone.gif
905 ms
footnav_apli.gif
904 ms
img-text-change.gif
902 ms
btn-text-small_ovoff.gif
900 ms
btn-text-medium_ovon.gif
900 ms
btn-text-large_ovoff.gif
899 ms
marker-separate.gif
905 ms
header_icon_text.gif
907 ms
header_icon_sitemap.gif
907 ms
header_icon_home.gif
902 ms
header_form_bg_btm.gif
902 ms
header_form_bg_top.gif
902 ms
header_form_bg_mdl.gif
904 ms
header_input_bg.gif
903 ms
gnavi_bg.gif
904 ms
gnavi_bg_btm.gif
903 ms
gnavi_bg_01.gif
903 ms
gnavi_bg_02.gif
904 ms
gnavi_bg_03.gif
904 ms
gnavi_bg_04.gif
903 ms
gnavi_bg_05.gif
904 ms
gnavi_bg_06.gif
902 ms
gnavi_bg_07.gif
902 ms
promo_bg_btm.gif
902 ms
promo_bg.gif
904 ms
promo_main_bg.gif
903 ms
pc_top_kv.jpg
1197 ms
pc_top_kv_s.jpg
903 ms
recipe_tit_bar.gif
900 ms
recipe_bg_center.gif
900 ms
recipe_photo_btm.gif
904 ms
recipe_photo_top.gif
904 ms
marker-arrow.gif
906 ms
heading2_bg_l.gif
906 ms
heading2_mark.gif
906 ms
bg-localnavi_btm.gif
1046 ms
ln_navi_bg.gif
906 ms
ln_navi_bg_btm.gif
908 ms
ln_navi_bg_top.gif
908 ms
ln_navi_bg_mdl.gif
910 ms
tvcm_bg_btm.gif
1044 ms
tvcm_mdl.gif
1049 ms
tvcm_01.jpg
905 ms
heading3_mark.gif
905 ms
marker-pagetop.gif
907 ms
footer_bg_btm.gif
907 ms
footer_bg.gif
1044 ms
footer_navi_dd.gif
1048 ms
footnav_group_bg_btm.gif
905 ms
marker-separate_footer.gif
906 ms
btn_house_group_ovon.gif
907 ms
btn-text-small_ovon.gif
905 ms
btn-text-large_ovon.gif
1044 ms
head_search_w_ovon.gif
1046 ms
recipe_tit_btn_ovon.gif
904 ms
icon_rss_ovon.gif
910 ms
ln_tit_products_ovon.gif
907 ms
ln_products_new_ovon.gif
906 ms
t_ln_btn_brandsite_ovon.gif
1044 ms
btn_alg_ovon.gif
1046 ms
bnr_csr_ovon.jpg
903 ms
group_banner_ovon.jpg
907 ms
bnr_saiyou_ovon.jpg
904 ms
bnr_mailmagazine_ovon.gif
903 ms
bnr_factory_ovon.gif
1044 ms
footnav_products_ovon.gif
900 ms
footnav_company_ovon.gif
900 ms
footnav_group_ovon.gif
902 ms
footnav_recipe_ovon.gif
899 ms
footnav_data_ovon.gif
898 ms
footnav_activity_ovon.gif
904 ms
footnav_shopping_ovon.gif
899 ms
footnav_inquiry_ovon.gif
899 ms
footnav_social_ovon.gif
900 ms
head_search_2_ovon.gif
900 ms
btn-localnavi-search_ovon.gif
899 ms
next.gif
905 ms
prev.gif
902 ms
guard_print.css
152 ms
print.css
152 ms
satellite-549d410364623200186d0000.js
104 ms
housefoods.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
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
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>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
housefoods.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
Browser errors were logged to the console
housefoods.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Housefoods.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 Housefoods.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.
housefoods.jp
Open Graph description is not detected on the main page of Housefoods. 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: