7.9 sec in total
993 ms
6.4 sec
481 ms
Welcome to ninnaji.jp homepage info - get ready to check Ninnaji best content for Japan right away, or after learning these important things about ninnaji.jp
真言宗御室派総本山 仁和寺の公式ウェブサイトです。888年に創建、かつて門跡寺院として栄えた、格式ある寺院・仁和寺。所蔵の国宝・重要文化財や御室桜などの境内のみどころ、仁和寺でできる写経や宿泊など数々の体験についてご案内しています。
Visit ninnaji.jpWe analyzed Ninnaji.jp page load time and found that the first response time was 993 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
ninnaji.jp performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value17.5 s
0/100
25%
Value20.3 s
0/100
10%
Value860 ms
33/100
30%
Value0.258
48/100
15%
Value23.3 s
1/100
10%
993 ms
764 ms
585 ms
2601 ms
407 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 61% of them (43 requests) were addressed to the original Ninnaji.jp, 24% (17 requests) were made to Pbs.twimg.com and 10% (7 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Ninnaji.jp.
Page size can be reduced by 551.1 kB (12%)
4.8 MB
4.2 MB
In fact, the total size of Ninnaji.jp main page is 4.8 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. 60% of websites need less resources to load. Images take 4.2 MB which makes up the majority of the site volume.
Potential reduce by 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 11.6 kB or 66% of the original size.
Potential reduce by 118.0 kB
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.
Potential reduce by 399.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 399.5 kB or 80% of the original size.
Potential reduce by 22.0 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 22.0 kB or 89% of the original size.
Number of requests can be reduced by 10 (14%)
70
60
The browser has sent 70 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 7 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
ninnaji.jp
993 ms
common.css
764 ms
top.css
585 ms
jquery-1.6.2.js
2601 ms
crossFader.css
407 ms
jquery.crossFader.js
414 ms
widgets.js
83 ms
back.jpg
1927 ms
analytics.js
15 ms
logo.png
387 ms
001.jpg
398 ms
002.jpg
1814 ms
003.jpg
1911 ms
004.jpg
1601 ms
005.jpg
2116 ms
006.jpg
818 ms
007.jpg
1406 ms
008.jpg
1996 ms
009.jpg
2399 ms
010.jpg
2820 ms
main_menu1.jpg
2098 ms
main_menu2.jpg
2110 ms
main_menu3.jpg
2193 ms
main_menu4.jpg
2286 ms
main_menu5.jpg
2302 ms
index_h2_houyuou.jpg
2306 ms
arrow_houyou.gif
2389 ms
index_h2_haikan.jpg
2475 ms
index_menu_sub1.jpg
2495 ms
index_menu_sub2.jpg
2496 ms
index_menu_sub3.jpg
2584 ms
index_h2_oshirase.jpg
2596 ms
kawarahounou.png
3038 ms
bnr_MediaTrek_220_ninnaji.gif
2685 ms
footer_ninnaji.jpg
2687 ms
collect
37 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
127 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
155 ms
link_arrow.gif
2680 ms
banner_donate.jpg
2694 ms
banner_blog.jpg
2777 ms
sub_menu2_1.jpg
2778 ms
sub_menu2_2.jpg
2876 ms
sub_menu2_3.jpg
2894 ms
sub_menu2_4.jpg
2915 ms
sub_menu1_1.jpg
2968 ms
sub_menu1_2.jpg
2968 ms
syndication
100 ms
558538096585613312
186 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
60 ms
footer_back.jpg
2799 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
31 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
151 ms
omuroryu_60_1__normal.gif
386 ms
CbssR2eUUAAUOSi.jpg:small
365 ms
CTArGYDUcAEa12r.jpg:small
552 ms
CSnAVLkUAAA0DEC.jpg:small
538 ms
CQI1O0aVEAAv4CG.jpg:small
473 ms
CZIktXKUMAAu-ln.jpg:small
346 ms
CZIktVoU8AArIoc.jpg:small
380 ms
CRlHKidUAAAN4J4.jpg:small
414 ms
CRlHKifUwAAheE6.jpg:small
411 ms
CRlHKikUwAQDgXq.jpg:small
408 ms
CRlHKj1UcAAR6gz.jpg:small
438 ms
CRk-IjtUkAAnzkg.jpg:small
442 ms
CRk-IjvVEAEDhEw.jpg:small
440 ms
CRk8ZxqVAAAd1V9.jpg:small
465 ms
CRk8ZyCUAAQZAz9.jpg:small
491 ms
CRaaST0UEAA69M1.jpg:small
471 ms
CRaaST-UEAAhDgS.jpg:small
519 ms
jot.html
28 ms
ninnaji.jp accessibility score
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
ninnaji.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
ninnaji.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
JA
JA
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.
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: