6.6 sec in total
1.4 sec
4.7 sec
515 ms
Welcome to izumi.jp homepage info - get ready to check Izumi best content for Japan right away, or after learning these important things about izumi.jp
『ゆめタウン』『ゆめマート』『ゆめモール』のお買物とお店の情報を掲載しています。店舗・チラシ・お料理レシピ・イベント・キャンペーンの情報が満載。知って得する旬の生活情報をご覧いただけます。
Visit izumi.jpWe analyzed Izumi.jp page load time and found that the first response time was 1.4 sec and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
izumi.jp performance score
1379 ms
529 ms
694 ms
549 ms
501 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 96% of them (85 requests) were addressed to the original Izumi.jp, 1% (1 request) were made to Googleadservices.com and 1% (1 request) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Izumi.jp.
Page size can be reduced by 326.8 kB (16%)
2.0 MB
1.7 MB
In fact, the total size of Izumi.jp main page is 2.0 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. 45% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 47.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 47.7 kB or 82% of the original size.
Potential reduce by 64.4 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. Izumi images are well optimized though.
Potential reduce by 155.1 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 155.1 kB or 67% of the original size.
Potential reduce by 59.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. Izumi.jp needs all CSS files to be minified and compressed as it can save up to 59.7 kB or 83% of the original size.
Number of requests can be reduced by 29 (34%)
86
57
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Izumi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
izumi.jp
1379 ms
normalize.css
529 ms
style.css
694 ms
common.css
549 ms
index.css
501 ms
owl.carousel.css
347 ms
owl.theme.css
348 ms
jquery.flipster.css
352 ms
colorbox.css
355 ms
jquery-1.8.3.min.js
1095 ms
jquery.cookie.js
559 ms
swfobject.js
559 ms
common.js
694 ms
jquery.cookie.js
507 ms
common.js
517 ms
index.js
517 ms
vote.js
525 ms
flexslider.css
528 ms
jquery.flexslider.js
996 ms
jquery.colorbox.js
679 ms
important.js
720 ms
jquery.flipster.js
524 ms
conversion.js
17 ms
logo.gif
174 ms
bn_yumeshop_01.jpg
353 ms
bn_ushi.jpg
176 ms
btn_recipe.gif
175 ms
info_cm.png
169 ms
info_music.png
354 ms
info_cafe.png
671 ms
btn_vote.gif
338 ms
page_top.png
344 ms
link_blank.gif
186 ms
arrow_pink.png
168 ms
btn_search.png
169 ms
0222_henkel_bannertei2.jpg
544 ms
2016newlifebn.jpg
725 ms
appbn.jpg
546 ms
credit.jpg
1163 ms
yumeca.jpg
833 ms
yuko_yasukayo.jpg
896 ms
0222_henkel_bannertei290.jpg
726 ms
2016newlifebn290.jpg
726 ms
okaidoku_randoseru.jpg
907 ms
okaidoku_yumeca.jpg
909 ms
okaidoku_youmetopics.jpg
910 ms
bn_youmeshop.jpg
1000 ms
appservice.jpg
1067 ms
service_youmetopics.jpg
1086 ms
service_card.jpg
1089 ms
service_youmeca.jpg
1087 ms
fc_sarvice.jpg
1165 ms
service_xsell.gif
1244 ms
20160301_sattoni.jpg
1267 ms
20160301_hanazushi.jpg
1268 ms
20160301_peperonsalad.jpg
1270 ms
20160301_takiawase.jpg
1325 ms
20160301_openomletsu.jpg
1333 ms
20160301_potajyu.jpg
1418 ms
20160301_cyukatororian.jpg
1448 ms
20160301_katsuopokidon.jpg
1448 ms
20160301_katsuonanban.jpg
1450 ms
info_shunsai.png
1491 ms
tenpo_tab.png
484 ms
chirashi_tab.png
472 ms
map.png
825 ms
arrow_pink.png
496 ms
pref_bg_right.png
497 ms
arrow_right_off.png
637 ms
pref_bg_left.png
654 ms
arrow_left_off.png
670 ms
map2.png
1379 ms
info_circle.gif
803 ms
header_noflash.gif
1475 ms
gnavi.png
1570 ms
h2_bkg.jpg
1603 ms
footer_bg.gif
1569 ms
logo.gif
1572 ms
89 ms
gtm.js
131 ms
vote.cgi
786 ms
42 ms
0222_henkel_bannertei2thumb.jpg
178 ms
2016newlifebn_thumb.jpg
168 ms
appbn_thumb.jpg
169 ms
credit_thumb.jpg
184 ms
webyumeca_thumb.jpg
184 ms
slider_menu_bg.jpg
184 ms
flexslider-icon.svg
890 ms
izumi.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Izumi.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 Izumi.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.
izumi.jp
Open Graph description is not detected on the main page of Izumi. 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: