Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 74

    SEO

    Google-friendlier than
    31% of websites

aquatotto.com

世界淡水魚園水族館 アクア・トト ぎふ - 岐阜県各務原市の水族館

Page Load Speed

12.4 sec in total

First Response

546 ms

Resources Loaded

9.4 sec

Page Rendered

2.4 sec

aquatotto.com screenshot

About Website

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

岐阜県各務原市の世界淡水魚園水族館、アクア・トト ぎふは、世界最大級の淡水魚水族館。岐阜県を観光される際にはぜひお立ち寄り下さい

Visit aquatotto.com

Key Findings

We analyzed Aquatotto.com page load time and found that the first response time was 546 ms and then it took 11.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

aquatotto.com performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value21.2 s

0/100

25%

SI (Speed Index)

Value19.2 s

0/100

10%

TBT (Total Blocking Time)

Value1,060 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.652

9/100

15%

TTI (Time to Interactive)

Value29.1 s

0/100

10%

Network Requests Diagram

aquatotto.com

546 ms

aquatotto.com

2781 ms

slick.css

523 ms

slick-theme.css

522 ms

insta.css

529 ms

Our browser made a total of 188 requests to load all elements on the main page. We found that 72% of them (136 requests) were addressed to the original Aquatotto.com, 6% (12 requests) were made to Snapwidget.com and 5% (9 requests) were made to Scontent.cdninstagram.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Aquatotto.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (5%)

Content Size

19.1 MB

After Optimization

18.1 MB

In fact, the total size of Aquatotto.com main page is 19.1 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 18.6 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 101.9 kB

  • Original 113.5 kB
  • After minification 55.3 kB
  • After compression 11.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 58.2 kB, which is 51% 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 101.9 kB or 90% of the original size.

Image Optimization

-4%

Potential reduce by 663.9 kB

  • Original 18.6 MB
  • After minification 18.0 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. Aquatotto images are well optimized though.

JavaScript Optimization

-39%

Potential reduce by 43.7 kB

  • Original 111.9 kB
  • After minification 109.8 kB
  • After compression 68.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 43.7 kB or 39% of the original size.

CSS Optimization

-87%

Potential reduce by 197.1 kB

  • Original 227.6 kB
  • After minification 175.0 kB
  • After compression 30.5 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. Aquatotto.com needs all CSS files to be minified and compressed as it can save up to 197.1 kB or 87% of the original size.

Requests Breakdown

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

Requests Now

180

After Optimization

127

The browser has sent 180 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aquatotto. 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 from 12 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

aquatotto.com accessibility score

80

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 input fields do not have accessible names

High

ARIA toggle fields do not have accessible names

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.

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

<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

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

aquatotto.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

aquatotto.com SEO score

74

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses 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 Aquatotto.com 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 Aquatotto.com 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

Open Graph description is not detected on the main page of Aquatotto. 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: