Access ninnaji.jp. 世界遺産真言宗御室派総本山仁和寺

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

5/100

10%

LCP (Largest Contentful Paint)

Value22.1 s

0/100

25%

SI (Speed Index)

Value21.1 s

0/100

10%

TBT (Total Blocking Time)

Value2,040 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.284

43/100

15%

TTI (Time to Interactive)

Value31.5 s

0/100

10%

ninnaji.jp

516 ms

ninnaji.jp

1567 ms

reset.css

507 ms

animate.css

1008 ms

module.css

502 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 79% of them (66 requests) were addressed to the original Ninnaji.jp, 7% (6 requests) were made to Youtube-nocookie.com and 2% (2 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Ninnaji.jp.

Content Size

6.2 MB

After Optimization

5.7 MB

In fact, the total size of Ninnaji.jp main page is 6.2 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.2 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 42.2 kB

Original 52.7 kB
After minification 43.8 kB
After compression 10.5 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 8.9 kB, which is 17% 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 42.2 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 68.4 kB

Original 5.2 MB
After minification 5.1 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. Ninnaji images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 80.4 kB

Original 607.6 kB
After minification 596.8 kB
After compression 527.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 80.4 kB or 13% of the original size.

CSS Optimization

-73%

Potential reduce by 260.5 kB

Original 354.8 kB
After minification 300.1 kB
After compression 94.3 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. Ninnaji.jp needs all CSS files to be minified and compressed as it can save up to 260.5 kB or 73% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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.

High

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

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

High

Links are not crawlable

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/).

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

ninnaji.jp

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

Report Summary

Performance

Accessibility

Best Practices

SEO

世界遺産 真言宗御室派総本山 仁和寺

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

ninnaji.jp

ninnaji.jp

reset.css

animate.css

module.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

ninnaji.jp

ninnaji.jp

reset.css

animate.css

module.css

module_sp.css

global.css

global_sp.css

top.css

top_sp.css

top_cta.css

style.min.css

styles.css

styles.css

pagenavi-css.css

jquery.fancybox.min.css

jquery-1.10.2.min.js

jquery.easing.min.js

ticketing.umd.min.js

js

index.js

index.js

jquery.form.min.js

scripts.js

jquery.fancybox.min.js

jquery.easing.min.js

jquery.mousewheel.min.js

global.js

heightLine.js

iscroll.min.js

drawer.min.css

drawer.min.js

jquery.bxslider.min.js

jquery.bxslider.css

mainPanel_copy.png

banner_omurobyou.png

banner_amidado.png

bnr_shop.png

informationArea_thumb.png

bnr_goten3d.png

banner_art48p_l.png

bnr_omurokaikan.png

bnr_sankoubou.png

世界遺産真言宗御室派総本山仁和寺