Tools & Wizards About Us
uminomori.jp screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

uminomori.jp

仙台うみの杜水族館｜仙台うみの杜水族館

Page Load Speed

13 sec in total

First Response

158 ms

Resources Loaded

11.8 sec

Page Rendered

979 ms

uminomori.jp screenshot

About Website

Visit uminomori.jp now to see the best up-to-date Uminomori content for Japan and also check out these interesting facts you probably never knew about uminomori.jp

仙台うみの杜水族館の仙台うみの杜水族館について。いのちきらめく、うみの杜。仙台うみの杜水族館は、豊かな東北の海の魅力を、見て・さわって・感じることができる水族館です。

Visit uminomori.jp

Key Findings

We analyzed Uminomori.jp page load time and found that the first response time was 158 ms and then it took 12.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

uminomori.jp performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.0 s

0/100

25%

SI (Speed Index)

Value21.4 s

0/100

10%

TBT (Total Blocking Time)

Value4,260 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value53.1 s

0/100

10%

Network Requests Diagram

www.uminomori.jp

158 ms

2193 ms

gtm.js

82 ms

css2

54 ms

style.css

919 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 67% of them (51 requests) were addressed to the original Uminomori.jp, 24% (18 requests) were made to Platform.twitter.com and 3% (2 requests) were made to J.wovn.io. The less responsive or slowest element that took the longest time to load (8.8 sec) belongs to the original domain Uminomori.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 71.4 kB (1%)

Content Size

5.0 MB

After Optimization

4.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Uminomori.jp main page is 5.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. 70% of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 71.3 kB

  • Original 81.9 kB
  • After minification 58.2 kB
  • After compression 10.6 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 23.7 kB, which is 29% 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 71.3 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 40 B

  • Original 4.5 MB
  • After minification 4.5 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. Uminomori images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 313.2 kB
  • After minification 313.2 kB
  • After compression 313.2 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 98 B

  • Original 45.8 kB
  • After minification 45.8 kB
  • After compression 45.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. Uminomori.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 29 (39%)

Requests Now

74

After Optimization

45

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Uminomori. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

www.uminomori.jp

www.uminomori.jp

158 ms

2193 ms

gtm.js

gtm.js

82 ms

css2

css2

54 ms

style.css

style.css

919 ms

1

1

79 ms

widgets.js

widgets.js

25 ms

uminomori-logo.svg

uminomori-logo.svg

893 ms

seibu-logo.svg

seibu-logo.svg

409 ms

atumori_PC.png

atumori_PC.png

1941 ms

2024_seatopia_banner_4type_1900_992.jpg

2024_seatopia_banner_4type_1900_992.jpg

2227 ms

maeuri_PC.png

maeuri_PC.png

1198 ms

natsu2024_1900_992.png

natsu2024_1900_992.png

2110 ms

banner_daisuiso_PC.jpg

banner_daisuiso_PC.jpg

3295 ms

00_africa_1.jpg

00_africa_1.jpg

2141 ms

00_africa_2.jpg

00_africa_2.jpg

2687 ms

umino_34241_001.jpg

umino_34241_001.jpg

3089 ms

natsu2024_750_500.png

natsu2024_750_500.png

3570 ms

penguin_zukan.jpg

penguin_zukan.jpg

2984 ms

event_stadiumlive.html_list.jpg

event_stadiumlive.html_list.jpg

3727 ms

event_sol.html_list.jpg

event_sol.html_list.jpg

3819 ms

umino_diving_list.jpg

umino_diving_list.jpg

4165 ms

umino_photowedding_list.jpg

umino_photowedding_list.jpg

4059 ms

umino_top_about.jpg

umino_top_about.jpg

4481 ms

topic_reserve.jpg

topic_reserve.jpg

4705 ms

topic_blog.jpg

topic_blog.jpg

4774 ms

topic_online.jpg

topic_online.jpg

4890 ms

umino_topic_passport.jpg

umino_topic_passport.jpg

5106 ms

topic_gift.jpg

topic_gift.jpg

5547 ms

umino_apuri.png

umino_apuri.png

5626 ms

animals_irowakeiruka.html_list.jpg

animals_irowakeiruka.html_list.jpg

6110 ms

animals_kepu.html_list.jpg

animals_kepu.html_list.jpg

5919 ms

animals_bandouiruka.html_list_2.jpg

animals_bandouiruka.html_list_2.jpg

5979 ms

animals_hoshiei.html_list.jpg

animals_hoshiei.html_list.jpg

6369 ms

animals_yellowheadjofish.html_list.jpg

animals_yellowheadjofish.html_list.jpg

6514 ms

animals_kayanezumi.html_list.jpg

animals_kayanezumi.html_list.jpg

6744 ms

animals_takaashigani.html_list.jpg

animals_takaashigani.html_list.jpg

7085 ms

animals_hunborutopenguin.html_list.jpg

animals_hunborutopenguin.html_list.jpg

7206 ms

animals_maboya.html_list.jpg

animals_maboya.html_list.jpg

8824 ms

animals_mizukurage.html_list_1.jpg

animals_mizukurage.html_list_1.jpg

7613 ms

icon-twitter.png

icon-twitter.png

7069 ms

bundle.js

bundle.js

7124 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

27 ms

settings

settings

141 ms

widget

widget

31 ms

Cgy4_c

Cgy4_c

40 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

4 ms

sendaiuminomori

sendaiuminomori

1129 ms

icon-instagram.png

icon-instagram.png

7251 ms

icon-line.png

icon-line.png

6687 ms

icon-youtube.png

icon-youtube.png

6574 ms

umino_banner_001.png

umino_banner_001.png

6516 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

7 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

15 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

27 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

20 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

80 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

79 ms

_buildManifest.js

_buildManifest.js

97 ms

_ssgManifest.js

_ssgManifest.js

98 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

17 ms

7651.a95a6a76dc7859214377.js

7651.a95a6a76dc7859214377.js

17 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

7 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

14 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

12 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

35 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

11 ms

umino_banner_002.jpg

umino_banner_002.jpg

6234 ms

umino_banner_003.jpg

umino_banner_003.jpg

6285 ms

umino_banner_004.png

umino_banner_004.png

6324 ms

umino_banner_005.jpg

umino_banner_005.jpg

5985 ms

umino_banner_006.jpg

umino_banner_006.jpg

5574 ms

umino_banner_007.jpg

umino_banner_007.jpg

6290 ms

umino_banner_008.png

umino_banner_008.png

6029 ms

umino_banner_009.png

umino_banner_009.png

5612 ms

umino_banner_010.jpg

umino_banner_010.jpg

5554 ms

Accessibility Review

uminomori.jp accessibility score

73

Accessibility Issues

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

uminomori.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

Missing source maps for large first-party JavaScript

SEO Factors

uminomori.jp SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 uses legible font sizes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Uminomori.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 Uminomori.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

uminomori.jp

Open Graph data is detected on the main page of Uminomori. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: