Tools & Wizards About Us
kenninji.jp screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

kenninji.jp

建仁寺 The Oldest Zen Temple Kenninji

Page Load Speed

4.7 sec in total

First Response

530 ms

Resources Loaded

3.9 sec

Page Rendered

263 ms

kenninji.jp screenshot

About Website

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

建仁寺は臨済宗建仁寺派の大本山で、建仁2年に開創しました。開山は栄西禅師、開基は源頼家です。坐禅体験、写経体験受け付けております。

Visit kenninji.jp

Key Findings

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

Performance Metrics

kenninji.jp performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value220 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

kenninji.jp

530 ms

jquery-1.11.3.min.js

185 ms

jquery-1.11.3.min.map

331 ms

jsapi

41 ms

rssfeed2.js

336 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 88% of them (78 requests) were addressed to the original Kenninji.jp, 4% (4 requests) were made to Google.com and 4% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Kenninji.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 173.3 kB (9%)

Content Size

1.8 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-71%

Potential reduce by 9.6 kB

  • Original 13.5 kB
  • After minification 11.7 kB
  • After compression 3.9 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 1.8 kB, which is 14% 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 9.6 kB or 71% of the original size.

Image Optimization

-3%

Potential reduce by 51.0 kB

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

JavaScript Optimization

-59%

Potential reduce by 95.4 kB

  • Original 162.0 kB
  • After minification 154.9 kB
  • After compression 66.6 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 95.4 kB or 59% of the original size.

CSS Optimization

-83%

Potential reduce by 17.2 kB

  • Original 20.8 kB
  • After minification 16.3 kB
  • After compression 3.6 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. Kenninji.jp needs all CSS files to be minified and compressed as it can save up to 17.2 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (28%)

Requests Now

86

After Optimization

62

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kenninji.jp

kenninji.jp

530 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

185 ms

jquery-1.11.3.min.map

jquery-1.11.3.min.map

331 ms

jsapi

jsapi

41 ms

rssfeed2.js

rssfeed2.js

336 ms

useragent.js

useragent.js

342 ms

common.css

common.css

350 ms

default.css

default.css

333 ms

animation.css

animation.css

367 ms

rssfeed.css

rssfeed.css

479 ms

ajax.1.4.2jquery.min.js

ajax.1.4.2jquery.min.js

984 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

482 ms

jquery.easing.compatibility.js

jquery.easing.compatibility.js

498 ms

timelineanimation.js

timelineanimation.js

509 ms

13 ms

default+en.css

default+en.css

3 ms

default+en.I.js

default+en.I.js

5 ms

index_pc.css

index_pc.css

207 ms

btn_panorama.jpg

btn_panorama.jpg

317 ms

btn_archive.jpg

btn_archive.jpg

317 ms

btn_ebook.jpg

btn_ebook.jpg

333 ms

cut01bg.jpg

cut01bg.jpg

840 ms

cut01text.png

cut01text.png

574 ms

cut02.png

cut02.png

602 ms

cut03bg.jpg

cut03bg.jpg

909 ms

cut03text1.png

cut03text1.png

670 ms

cut03text2.png

cut03text2.png

766 ms

cut03text3.png

cut03text3.png

765 ms

cut04bg.jpg

cut04bg.jpg

1137 ms

cut04text.png

cut04text.png

1014 ms

cut05raijin.jpg

cut05raijin.jpg

1401 ms

cut05fujin.jpg

cut05fujin.jpg

1506 ms

cut05text1.png

cut05text1.png

1012 ms

cut05text2.png

cut05text2.png

1066 ms

cut06bg.jpg

cut06bg.jpg

1518 ms

cut06text.png

cut06text.png

1184 ms

cut07bg.jpg

cut07bg.jpg

1524 ms

cut07text.png

cut07text.png

1313 ms

cut08bg.jpg

cut08bg.jpg

1695 ms

cut08text.png

cut08text.png

1489 ms

cut09bg.jpg

cut09bg.jpg

1869 ms

cut09subTitle.png

cut09subTitle.png

1663 ms

cut09title.png

cut09title.png

1713 ms

frame.png

frame.png

1688 ms

rssmikle.js

rssmikle.js

19 ms

logo.gif

logo.gif

1480 ms

h_navi_bookmark.gif

h_navi_bookmark.gif

1633 ms

h_navi_privacy.gif

h_navi_privacy.gif

1635 ms

h_navi_sitemap.gif

h_navi_sitemap.gif

1659 ms

h_navi_toiawase.gif

h_navi_toiawase.gif

1664 ms

h_navi_english.gif

h_navi_english.gif

1700 ms

h_navi_top.gif

h_navi_top.gif

1802 ms

bg_con_middle.gif

bg_con_middle.gif

1788 ms

menu_01_o.jpg

menu_01_o.jpg

1816 ms

40 ms

ga.js

ga.js

5 ms

__utm.gif

__utm.gif

12 ms

jquery.min.js

jquery.min.js

8 ms

analytics.js

analytics.js

18 ms

news_bg.png

news_bg.png

733 ms

menu_01.jpg

menu_01.jpg

1728 ms

menu_02_o.jpg

menu_02_o.jpg

1722 ms

collect

collect

12 ms

menu_02.jpg

menu_02.jpg

1765 ms

menu_03_o.jpg

menu_03_o.jpg

1578 ms

menu_03.jpg

menu_03.jpg

1580 ms

menu_04_o.jpg

menu_04_o.jpg

1550 ms

menu_04.jpg

menu_04.jpg

1542 ms

menu_05_o.jpg

menu_05_o.jpg

1450 ms

menu_05.jpg

menu_05.jpg

1523 ms

menu_06_o.jpg

menu_06_o.jpg

1470 ms

menu_06.jpg

menu_06.jpg

1444 ms

menu_07_o.jpg

menu_07_o.jpg

1347 ms

menu_07.jpg

menu_07.jpg

1369 ms

news_bg.png

news_bg.png

1331 ms

ttl_news.gif

ttl_news.gif

1338 ms

bnr_ebook_off.jpg

bnr_ebook_off.jpg

1298 ms

bnr_movie01_off.jpg

bnr_movie01_off.jpg

1220 ms

contents_bg.png

contents_bg.png

1134 ms

bnr_event2016_kyofuyu50_on.jpg

bnr_event2016_kyofuyu50_on.jpg

1245 ms

bnr_event2016_kyofuyu50_off.jpg

bnr_event2016_kyofuyu50_off.jpg

1248 ms

bnr_category01gallery_off.jpg

bnr_category01gallery_off.jpg

1532 ms

bnr_category02history_off.jpg

bnr_category02history_off.jpg

1124 ms

bnr_category03precincts_off.jpg

bnr_category03precincts_off.jpg

1048 ms

bnr_category04access_off.jpg

bnr_category04access_off.jpg

1041 ms

bnr_category05zenmaster_off.jpg

bnr_category05zenmaster_off.jpg

1128 ms

bnr_category06experience_off.jpg

bnr_category06experience_off.jpg

1194 ms

bnr_category08zen_off.jpg

bnr_category08zen_off.jpg

1204 ms

f_copyright.gif

f_copyright.gif

1071 ms

Accessibility Review

kenninji.jp accessibility score

77

Accessibility Issues

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.

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

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

High

List items (<li>) are not contained within <ul> or <ol> parent 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

High

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

High

Links do not have a discernible name

Best Practices

kenninji.jp 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

kenninji.jp SEO score

92

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

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

kenninji.jp

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