7.8 sec in total
759 ms
6.7 sec
353 ms
Click here to check amazing Umie content for Japan. Otherwise, check out these important facts you probably never knew about umie.jp
神戸ハーバーランド 大型商業施設「ウミエ」
Visit umie.jpWe analyzed Umie.jp page load time and found that the first response time was 759 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
umie.jp performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value30.0 s
0/100
25%
Value28.5 s
0/100
10%
Value890 ms
32/100
30%
Value0.657
8/100
15%
Value47.7 s
0/100
10%
759 ms
515 ms
905 ms
366 ms
378 ms
Our browser made a total of 149 requests to load all elements on the main page. We found that 83% of them (124 requests) were addressed to the original Umie.jp, 3% (4 requests) were made to Google-analytics.com and 2% (3 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Umie.jp.
Page size can be reduced by 459.2 kB (8%)
5.7 MB
5.2 MB
In fact, the total size of Umie.jp main page is 5.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 5.1 MB which makes up the majority of the site volume.
Potential reduce by 53.8 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 10.0 kB, which is 15% 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 53.8 kB or 82% of the original size.
Potential reduce by 42.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. Umie images are well optimized though.
Potential reduce by 257.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 257.8 kB or 62% of the original size.
Potential reduce by 104.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. Umie.jp needs all CSS files to be minified and compressed as it can save up to 104.9 kB or 84% of the original size.
Number of requests can be reduced by 45 (31%)
145
100
The browser has sent 145 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Umie. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
umie.jp
759 ms
fotorama.css
515 ms
style.css
905 ms
custom.css
366 ms
sec.css
378 ms
original.css
587 ms
colorbox.css
500 ms
jquery.min.js
1094 ms
fotorama.js
1320 ms
swfobject.js
666 ms
jquery.cookie.js
685 ms
jquery.colorbox-min.js
782 ms
common.js
835 ms
underscore-min.js
857 ms
jquery.tmpldeck.min.js
977 ms
jquery.infinitescroll.min.js
1001 ms
jquery.rwdImageMaps.min.js
1027 ms
imagesloaded.pkgd.min.js
1082 ms
malls.api.js
1173 ms
am_aeonmall.js
839 ms
conversion.js
16 ms
templates.html
176 ms
ga.js
50 ms
sclogo.gif
223 ms
photo1.gif
588 ms
photo_sm.jpg
393 ms
ico_menu.png
356 ms
btn_close_01.png
398 ms
nav_home.png
493 ms
nav_event.png
512 ms
nav_shop.png
496 ms
nav_guide.png
578 ms
nav_access.png
586 ms
nav_info.png
679 ms
nav_lang.png
661 ms
photo1.jpg
2271 ms
photo1.jpg
1671 ms
photo1.jpg
1720 ms
photo1.jpg
2155 ms
photo1.jpg
1498 ms
photo1.jpg
2167 ms
photo1.jpg
2169 ms
photo1.jpg
2217 ms
photo1.jpg
2286 ms
photo1.gif
2353 ms
photo1.jpg
2546 ms
thumbW640_photo1.jpg
2340 ms
thumbW640_photo1.jpg
2402 ms
thumbW640_photo1.jpg
2468 ms
thumbW640_photo1.jpg
2476 ms
thumbW640_photo1.jpg
2508 ms
thumbW640_photo1.jpg
2547 ms
thumbW640_photo1.jpg
2587 ms
photo1.gif
2664 ms
pic.png
2665 ms
sdk.js
296 ms
am_gtpc.js
347 ms
btn_search_01.png
2647 ms
gtm.js
104 ms
photo1.jpg
2619 ms
photo1.jpg
2631 ms
__utm.gif
24 ms
39 ms
conversion_async.js
26 ms
analytics.js
11 ms
s_retargeting.js
578 ms
parking2.html
2616 ms
collect
8 ms
collect
75 ms
63 ms
44 ms
55 ms
parking.html
2661 ms
21 ms
21 ms
115 ms
getEventNews
2499 ms
xd_arbiter.php
214 ms
xd_arbiter.php
420 ms
plog
526 ms
photo1.jpg
2455 ms
photo1.jpg
2527 ms
photo1.gif
2452 ms
photo1.gif
2461 ms
photo1.jpg
2505 ms
photo1.gif
2468 ms
photo1.gif
2475 ms
photo1.jpg
2523 ms
photo1.gif
2479 ms
photo1.gif
2459 ms
am_stpc.js
154 ms
photo1.jpg
1685 ms
photo1.gif
1564 ms
photo1.jpg
1535 ms
photo1.gif
1142 ms
photo1.jpg
1151 ms
photo1.gif
1166 ms
photo1.gif
1133 ms
photo1.gif
1152 ms
photo1.gif
1165 ms
photo1.png
1142 ms
photo1.png
1149 ms
photo1.gif
1127 ms
photo1.gif
1049 ms
photo1.gif
1134 ms
photo1.gif
1138 ms
photo1.gif
1122 ms
photo1.gif
1137 ms
photo1.gif
1097 ms
photo1.gif
1061 ms
photo1.gif
1136 ms
photo1.gif
1165 ms
photo1.gif
1123 ms
photo1.gif
1123 ms
0156parking_status.png
730 ms
0156parking_status.png
738 ms
0156parking_status.png
776 ms
photo1.gif
1077 ms
photo1.gif
1077 ms
photo1.gif
1112 ms
photo1.gif
1158 ms
photo1.png
1099 ms
btn_pagetop.png
1100 ms
ico_loding.gif
1095 ms
btn_prev_01.png
1103 ms
btn_next_01.png
1134 ms
spacer.gif
1129 ms
amano-pc01-2.png
1125 ms
amano-pc02-2.png
1093 ms
amano-pc03-2.png
1094 ms
amano-pc04-2.png
1132 ms
amano-pc05-2.png
1133 ms
amano-pc06-2.png
1100 ms
thumb_photo1.jpg
1121 ms
thumb_photo1.jpg
1096 ms
thumb_photo1.jpg
1097 ms
thumb_photo1.jpg
1162 ms
thumb_photo1.jpg
1102 ms
thumb_photo1.jpg
1106 ms
thumb_photo1.jpg
1117 ms
thumb_photo1.gif
1105 ms
thumb_photo1.jpg
1109 ms
thumb_photo1.jpg
1180 ms
amano-pc01.png
1082 ms
amano-pc02.png
1100 ms
amano-pc06.png
1114 ms
amano-pc03.png
1106 ms
amano-pc04.png
1138 ms
amano-pc05.png
1134 ms
umie.jp 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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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>).
umie.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
umie.jp SEO score
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 doesn't use 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 Umie.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 Umie.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.
umie.jp
Open Graph description is not detected on the main page of Umie. 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: