Tools & Wizards About Us
umie.jp screenshot

Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

umie.jp

神戸ハーバーランドｕｍｉｅ

Page Load Speed

9.5 sec in total

First Response

538 ms

Resources Loaded

7.8 sec

Page Rendered

1.1 sec

umie.jp screenshot

About Website

Click here to check amazing Umie content for Japan. Otherwise, check out these important facts you probably never knew about umie.jp

神戸ハーバーランド 大型商業施設「ウミエ」

Visit umie.jp

Key Findings

We analyzed Umie.jp page load time and found that the first response time was 538 ms and then it took 8.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.

Performance Metrics

umie.jp performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value18.7 s

0/100

25%

SI (Speed Index)

Value18.6 s

0/100

10%

TBT (Total Blocking Time)

Value3,560 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.388

26/100

15%

TTI (Time to Interactive)

Value37.5 s

0/100

10%

Network Requests Diagram

umie.jp

538 ms

umie.jp

1160 ms

common.css

380 ms

slick.css

544 ms

slick-theme.css

545 ms

Our browser made a total of 155 requests to load all elements on the main page. We found that 85% of them (131 requests) were addressed to the original Umie.jp, 4% (6 requests) were made to Youtube-nocookie.com and 3% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Umie.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 893.9 kB (7%)

Content Size

12.6 MB

After Optimization

11.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Umie.jp main page is 12.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. Only a small number of websites need less resources to load. Images take 11.8 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 145.3 kB

  • Original 159.1 kB
  • After minification 119.1 kB
  • After compression 13.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 40.0 kB, which is 25% 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 145.3 kB or 91% of the original size.

Image Optimization

-3%

Potential reduce by 409.7 kB

  • Original 11.8 MB
  • After minification 11.4 MB

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.

JavaScript Optimization

-57%

Potential reduce by 287.7 kB

  • Original 508.2 kB
  • After minification 503.4 kB
  • After compression 220.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 287.7 kB or 57% of the original size.

CSS Optimization

-42%

Potential reduce by 51.2 kB

  • Original 121.2 kB
  • After minification 105.4 kB
  • After compression 70.1 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 51.2 kB or 42% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (19%)

Requests Now

148

After Optimization

120

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 148 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 16 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

umie.jp

umie.jp

538 ms

umie.jp

umie.jp

1160 ms

common.css

common.css

380 ms

slick.css

slick.css

544 ms

slick-theme.css

slick-theme.css

545 ms

top.css

top.css

740 ms

custom.css

custom.css

557 ms

original.css

original.css

563 ms

css

css

39 ms

jquery.min.js

jquery.min.js

27 ms

jquery.cookie.js

jquery.cookie.js

569 ms

common.js

common.js

724 ms

custom.js

custom.js

725 ms

slick.min.js

slick.min.js

926 ms

jquery.matchHeight-min.js

jquery.matchHeight-min.js

756 ms

ofi.min.js

ofi.min.js

760 ms

functions.js

functions.js

904 ms

top.js

top.js

905 ms

lt.js

lt.js

259 ms

gtm.js

gtm.js

274 ms

0156parking_status.png

0156parking_status.png

1204 ms

onqRe7fwO6s

onqRe7fwO6s

361 ms

embed

embed

834 ms

0156parking_status.png

0156parking_status.png

1091 ms

0156parking_status.png

0156parking_status.png

1097 ms

scname_image.png

scname_image.png

447 ms

scname_image_sm.png

scname_image_sm.png

831 ms

txt-lang-pc.png

txt-lang-pc.png

446 ms

txt-lang-sp.png

txt-lang-sp.png

445 ms

ico-search.png

ico-search.png

444 ms

ico-search-blue.png

ico-search-blue.png

443 ms

btn-sp-access.png

btn-sp-access.png

832 ms

btn-sp-map.png

btn-sp-map.png

829 ms

btn-sp-shop.png

btn-sp-shop.png

832 ms

btn-sp-news.png

btn-sp-news.png

829 ms

btn-pc-home.png

btn-pc-home.png

830 ms

btn-pc-access.png

btn-pc-access.png

1070 ms

btn-pc-map.png

btn-pc-map.png

1070 ms

btn-pc-shop.png

btn-pc-shop.png

1071 ms

btn-pc-news.png

btn-pc-news.png

1070 ms

topimage.jpg

topimage.jpg

2122 ms

topimage.jpg

topimage.jpg

2462 ms

topimage.jpg

topimage.jpg

2024 ms

banner-01.png

banner-01.png

1612 ms

banner-02.png

banner-02.png

1444 ms

banner-03.png

banner-03.png

1440 ms

banner-04.png

banner-04.png

1625 ms

sidetab-01-pc.png

sidetab-01-pc.png

1632 ms

ext_banner1.png

ext_banner1.png

1793 ms

sidetab-03-pc.png

sidetab-03-pc.png

1811 ms

txt-parking-pc.png

txt-parking-pc.png

1820 ms

txt-parking-sp.png

txt-parking-sp.png

1975 ms

btn-gmap.png

btn-gmap.png

1996 ms

ext_banner4.jpg

ext_banner4.jpg

2381 ms

ext_banner4.jpg

ext_banner4.jpg

2516 ms

ext_banner4.jpg

ext_banner4.jpg

2367 ms

ext_banner4.jpg

ext_banner4.jpg

2214 ms

ext_banner4.jpg

ext_banner4.jpg

2306 ms

txt-today-pc.png

txt-today-pc.png

2405 ms

txt-today-sp.png

txt-today-sp.png

2674 ms

image.jpg

image.jpg

3235 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj35TS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj35TS1g.ttf

566 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk35TS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk35TS1g.ttf

951 ms

err.gif

err.gif

960 ms

www-player.css

www-player.css

17 ms

www-embed-player.js

www-embed-player.js

49 ms

base.js

base.js

98 ms

slick.woff

slick.woff

2130 ms

image.jpg

image.jpg

2346 ms

image.jpg

image.jpg

2200 ms

image.jpg

image.jpg

2434 ms

image.jpg

image.jpg

2497 ms

YjCNJ0mFj9HiCkQt39lQVpZzkP0G8dlYH-ABayRLdFs.js

YjCNJ0mFj9HiCkQt39lQVpZzkP0G8dlYH-ABayRLdFs.js

127 ms

embed.js

embed.js

74 ms

AIdro_nCIreBJTdutW2AxpQVcPZYYJtnT_eiT8F6k2K_Hg=s68-c-k-c0x00ffffff-no-rj

AIdro_nCIreBJTdutW2AxpQVcPZYYJtnT_eiT8F6k2K_Hg=s68-c-k-c0x00ffffff-no-rj

411 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

197 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

195 ms

js

js

362 ms

image.jpg

image.jpg

2003 ms

image.jpg

image.jpg

2218 ms

image.jpg

image.jpg

2151 ms

image.jpg

image.jpg

2179 ms

image.jpg

image.jpg

2231 ms

image.jpg

image.jpg

2490 ms

image.jpg

image.jpg

2104 ms

image.jpg

image.jpg

2122 ms

image.jpg

image.jpg

2165 ms

Create

Create

21 ms

image.png

image.png

2173 ms

GenerateIT

GenerateIT

15 ms

image.jpg

image.jpg

1924 ms

image.jpg

image.jpg

1928 ms

image.jpg

image.jpg

1804 ms

image.jpg

image.jpg

1800 ms

image.jpg

image.jpg

1849 ms

image.jpg

image.jpg

1717 ms

image.jpg

image.jpg

1744 ms

txt-read-more-black-pc.png

txt-read-more-black-pc.png

1734 ms

txt-read-more-black-sp.png

txt-read-more-black-sp.png

1629 ms

ico-access.png

ico-access.png

1607 ms

ico-map.png

ico-map.png

1644 ms

ico-shop.png

ico-shop.png

1575 ms

ico-news.png

ico-news.png

1520 ms

txt-topics-pc.png

txt-topics-pc.png

1440 ms

txt-topics-sp.png

txt-topics-sp.png

1418 ms

image.jpg

image.jpg

1405 ms

image.png

image.png

1446 ms

image.jpg

image.jpg

1423 ms

image.jpg

image.jpg

1400 ms

image.gif

image.gif

1362 ms

image.jpg

image.jpg

1327 ms

txt-read-more-white-pc.png

txt-read-more-white-pc.png

1292 ms

txt-read-more-white-sp.png

txt-read-more-white-sp.png

1249 ms

log_event

log_event

19 ms

txt-search-pc.png

txt-search-pc.png

1243 ms

txt-search-sp.png

txt-search-sp.png

1220 ms

bg-red.png

bg-red.png

1184 ms

ext_banner3.jpg

ext_banner3.jpg

1170 ms

ext_banner3.jpg

ext_banner3.jpg

1148 ms

ext_banner3.jpg

ext_banner3.jpg

1178 ms

ext_banner3.jpg

ext_banner3.jpg

1201 ms

ext_banner3.jpg

ext_banner3.jpg

1109 ms

ext_banner3.jpg

ext_banner3.jpg

1131 ms

ext_banner3.jpg

ext_banner3.jpg

1098 ms

ext_banner3.jpg

ext_banner3.jpg

1099 ms

dashed-black.png

dashed-black.png

1110 ms

txt-info-pc.png

txt-info-pc.png

1129 ms

txt-info-sp.png

txt-info-sp.png

1098 ms

arrow-right-black.png

arrow-right-black.png

1140 ms

txt-more-black-pc.png

txt-more-black-pc.png

1097 ms

txt-more-black-sp.png

txt-more-black-sp.png

1100 ms

sub_banner.jpg

sub_banner.jpg

1114 ms

sub_banner.gif

sub_banner.gif

1128 ms

sub_banner.jpg

sub_banner.jpg

1090 ms

sub_banner.jpg

sub_banner.jpg

1136 ms

sub_banner.jpg

sub_banner.jpg

1091 ms

sub_banner.gif

sub_banner.gif

1105 ms

sub_banner.jpg

sub_banner.jpg

1111 ms

sub_banner.gif

sub_banner.gif

1128 ms

sub_banner.gif

sub_banner.gif

1091 ms

sub_banner.jpg

sub_banner.jpg

1127 ms

sub_banner.jpg

sub_banner.jpg

1108 ms

sub_banner.gif

sub_banner.gif

1108 ms

fotter-eigyojikan-text.png

fotter-eigyojikan-text.png

1114 ms

pagetop_btn_blue.png

pagetop_btn_blue.png

1128 ms

map.png

map.png

1090 ms

arrow-right-black-2.png

arrow-right-black-2.png

1118 ms

icon_app.png

icon_app.png

1116 ms

icon_Instagram.png

icon_Instagram.png

1109 ms

fotter-eigyojikan-illust.png

fotter-eigyojikan-illust.png

1114 ms

ajax-loader.gif

ajax-loader.gif

1114 ms

arrow-left-round-black.png

arrow-left-round-black.png

1102 ms

arrow-right-round-black.png

arrow-right-round-black.png

1107 ms

arrow-left-round-white.png

arrow-left-round-white.png

1115 ms

arrow-right-round-white.png

arrow-right-round-white.png

1120 ms

Accessibility Review

umie.jp accessibility score

75

Accessibility Issues

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

High

[aria-hidden="true"] elements contain focusable descendents

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

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

umie.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

umie.jp SEO score

84

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    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 neither this language nor any other was claimed in <html> or <meta> tags. 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.

Social Sharing Optimization

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: