Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

miyajima.or.jp

一般社団法人宮島観光協会 嚴島神社等の観光施設や歴史・自然をご紹介

Page Load Speed

11.3 sec in total

First Response

555 ms

Resources Loaded

10.1 sec

Page Rendered

675 ms

About Website

Welcome to miyajima.or.jp homepage info - get ready to check Miyajima best content for Japan right away, or after learning these important things about miyajima.or.jp

世界遺産・日本三景の島宮島。嚴島神社等の観光施設や自然・歴史を詳しくご紹介します。

Visit miyajima.or.jp

Key Findings

We analyzed Miyajima.or.jp page load time and found that the first response time was 555 ms and then it took 10.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

miyajima.or.jp performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value29.5 s

0/100

25%

SI (Speed Index)

Value26.4 s

0/100

10%

TBT (Total Blocking Time)

Value3,450 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.453

20/100

15%

TTI (Time to Interactive)

Value44.8 s

0/100

10%

Network Requests Diagram

miyajima.or.jp

555 ms

miyajima.or.jp

720 ms

index.php

1504 ms

gtm.js

69 ms

gtm.js

109 ms

Our browser made a total of 231 requests to load all elements on the main page. We found that 71% of them (164 requests) were addressed to the original Miyajima.or.jp, 9% (21 requests) were made to Static.xx.fbcdn.net and 8% (18 requests) were made to Platinumaps.jp. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Miyajima.or.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 857.4 kB (11%)

Content Size

7.5 MB

After Optimization

6.6 MB

In fact, the total size of Miyajima.or.jp main page is 7.5 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 5.5 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 29.1 kB

  • Original 37.7 kB
  • After minification 33.0 kB
  • After compression 8.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 4.7 kB, which is 13% 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 29.1 kB or 77% of the original size.

Image Optimization

-4%

Potential reduce by 227.2 kB

  • Original 5.5 MB
  • After minification 5.3 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. Miyajima images are well optimized though.

JavaScript Optimization

-28%

Potential reduce by 499.2 kB

  • Original 1.8 MB
  • After minification 1.8 MB
  • After compression 1.3 MB

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 499.2 kB or 28% of the original size.

CSS Optimization

-60%

Potential reduce by 101.8 kB

  • Original 170.0 kB
  • After minification 145.8 kB
  • After compression 68.2 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. Miyajima.or.jp needs all CSS files to be minified and compressed as it can save up to 101.8 kB or 60% of the original size.

Requests Breakdown

Number of requests can be reduced by 95 (42%)

Requests Now

226

After Optimization

131

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

Accessibility Review

miyajima.or.jp accessibility score

63

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

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

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

miyajima.or.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

miyajima.or.jp SEO score

83

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

High

Tap targets are not sized appropriately

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 Miyajima.or.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 Miyajima.or.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

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