Tools & Wizards About Us
shorenin.com screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

shorenin.com

天台宗 青蓮院門跡

Page Load Speed

828 ms in total

First Response

198 ms

Resources Loaded

497 ms

Page Rendered

133 ms

shorenin.com screenshot

About Website

Click here to check amazing Shorenin content for Japan. Otherwise, check out these important facts you probably never knew about shorenin.com

京都市東山区粟田口に位置する天台宗の門跡寺院、青蓮院門跡。拝観案内、夜間拝観の他、飛地境内「将軍塚」、国宝「青不動尊」の紹介等。

Visit shorenin.com

Key Findings

We analyzed Shorenin.com page load time and found that the first response time was 198 ms and then it took 630 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

shorenin.com performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value75.6 s

0/100

25%

SI (Speed Index)

Value5.7 s

52/100

10%

TBT (Total Blocking Time)

Value840 ms

34/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value5.0 s

76/100

10%

Network Requests Diagram

shorenin.com

198 ms

www.shorenin.com

171 ms

common.css

5 ms

top.css

6 ms

rollover2.js

8 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 96% of them (45 requests) were addressed to the original Shorenin.com, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (198 ms) belongs to the original domain Shorenin.com.

Page Optimization Overview & Recommendations

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

Content Size

263.7 kB

After Optimization

234.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Shorenin.com main page is 263.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 218.3 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 7.8 kB

  • Original 11.1 kB
  • After minification 10.4 kB
  • After compression 3.3 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 7.8 kB or 70% of the original size.

Image Optimization

-5%

Potential reduce by 10.0 kB

  • Original 218.3 kB
  • After minification 208.2 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. Shorenin images are well optimized though.

JavaScript Optimization

-26%

Potential reduce by 7.5 kB

  • Original 29.4 kB
  • After minification 29.0 kB
  • After compression 21.9 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 7.5 kB or 26% of the original size.

CSS Optimization

-76%

Potential reduce by 3.8 kB

  • Original 4.9 kB
  • After minification 3.5 kB
  • After compression 1.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. Shorenin.com needs all CSS files to be minified and compressed as it can save up to 3.8 kB or 76% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

45

After Optimization

45

  • Images
  • JavaScript
  • CSS

The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shorenin. According to our analytics all requests are already optimized.

Network Requests Diagram

shorenin.com

shorenin.com

198 ms

www.shorenin.com

www.shorenin.com

171 ms

common.css

common.css

5 ms

top.css

top.css

6 ms

rollover2.js

rollover2.js

8 ms

swfobject-2.3.js

swfobject-2.3.js

9 ms

ga.js

ga.js

35 ms

bg.jpg

bg.jpg

11 ms

logo.jpg

logo.jpg

12 ms

head_blog.jpg

head_blog.jpg

13 ms

navi_gokaicho01.png

navi_gokaicho01.png

15 ms

navi_shogunzuka.png

navi_shogunzuka.png

12 ms

navi_monsu.png

navi_monsu.png

14 ms

navi_info.png

navi_info.png

16 ms

navi_haikan.jpg

navi_haikan.jpg

15 ms

navi_temple.jpg

navi_temple.jpg

15 ms

navi_shogun.jpg

navi_shogun.jpg

16 ms

navi_kokuhou.jpg

navi_kokuhou.jpg

17 ms

navi_tukigoma.jpg

navi_tukigoma.jpg

18 ms

navi_gyoji.jpg

navi_gyoji.jpg

18 ms

navi_kobuntei.jpg

navi_kobuntei.jpg

20 ms

navi_ganzan.jpg

navi_ganzan.jpg

18 ms

navi_shuyokai.jpg

navi_shuyokai.jpg

19 ms

navi_reijo.jpg

navi_reijo.jpg

21 ms

blog.jpg

blog.jpg

22 ms

night.jpg

night.jpg

22 ms

gohonzon.jpg

gohonzon.jpg

19 ms

toptopic_bg.jpg

toptopic_bg.jpg

20 ms

topropic_shoren_h2.jpg

topropic_shoren_h2.jpg

22 ms

topicli.jpg

topicli.jpg

22 ms

top_shogun_h2.jpg

top_shogun_h2.jpg

22 ms

top_tukigoma.jpg

top_tukigoma.jpg

24 ms

top_gomadou_h2.gif

top_gomadou_h2.gif

22 ms

butuzen_bn.jpg

butuzen_bn.jpg

22 ms

nokotsubn.jpg

nokotsubn.jpg

23 ms

englishbn.jpg

englishbn.jpg

24 ms

pagetop.jpg

pagetop.jpg

23 ms

footer_bg.jpg

footer_bg.jpg

23 ms

__utm.gif

__utm.gif

25 ms

head_blog_on.jpg

head_blog_on.jpg

3 ms

blog_on.jpg

blog_on.jpg

6 ms

night_on.jpg

night_on.jpg

6 ms

gohonzon_on.jpg

gohonzon_on.jpg

5 ms

butuzen_bn_on.jpg

butuzen_bn_on.jpg

7 ms

nokotsubn_on.jpg

nokotsubn_on.jpg

6 ms

englishbn_on.jpg

englishbn_on.jpg

7 ms

pagetop_on.jpg

pagetop_on.jpg

8 ms

Accessibility Review

shorenin.com accessibility score

80

Accessibility Issues

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

Image elements do not have [alt] attributes

Best Practices

shorenin.com 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

SEO Factors

shorenin.com SEO score

67

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shorenin.com 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 Shorenin.com main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

shorenin.com

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