Tools & Wizards About Us
rengein.jp screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

rengein.jp

蓮華院誕生寺

Page Load Speed

8.8 sec in total

First Response

515 ms

Resources Loaded

8.1 sec

Page Rendered

173 ms

rengein.jp screenshot

About Website

Click here to check amazing Rengein content. Otherwise, check out these important facts you probably never knew about rengein.jp

蓮華院誕生寺は本尊皇円大菩薩様をお祀りする真言律宗の九州別格本山です。南大門、四天王像、五重塔、多宝塔、五輪塔が有名です。悩み事相談や祈願・供養、国内外の援助、文化活動、内観研修等も活発に行っています。

Visit rengein.jp

Key Findings

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

Performance Metrics

rengein.jp performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value17.5 s

0/100

25%

SI (Speed Index)

Value15.4 s

1/100

10%

TBT (Total Blocking Time)

Value620 ms

48/100

30%

CLS (Cumulative Layout Shift)

Value0.082

94/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

rengein.jp

515 ms

rengein.jp

681 ms

www.rengein.jp

1022 ms

style.css

501 ms

ddsmoothmenu.css

502 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 69% of them (49 requests) were addressed to the original Rengein.jp, 25% (18 requests) were made to Platform.twitter.com and 3% (2 requests) were made to Syndication.twitter.com. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Rengein.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 156.1 kB (13%)

Content Size

1.2 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-68%

Potential reduce by 11.8 kB

  • Original 17.4 kB
  • After minification 17.1 kB
  • After compression 5.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.8 kB or 68% of the original size.

Image Optimization

-2%

Potential reduce by 15.9 kB

  • Original 983.5 kB
  • After minification 967.5 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. Rengein images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 119.5 kB

  • Original 174.8 kB
  • After minification 162.1 kB
  • After compression 55.3 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 119.5 kB or 68% of the original size.

CSS Optimization

-80%

Potential reduce by 8.9 kB

  • Original 11.2 kB
  • After minification 7.5 kB
  • After compression 2.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. Rengein.jp needs all CSS files to be minified and compressed as it can save up to 8.9 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (40%)

Requests Now

67

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rengein.jp

rengein.jp

515 ms

rengein.jp

rengein.jp

681 ms

www.rengein.jp

www.rengein.jp

1022 ms

style.css

style.css

501 ms

ddsmoothmenu.css

ddsmoothmenu.css

502 ms

jScrollPane.css

jScrollPane.css

518 ms

js

js

74 ms

jquery.js

jquery.js

863 ms

jquery.mousewheel.js

jquery.mousewheel.js

520 ms

jScrollPane-1.2.3.min.js

jScrollPane-1.2.3.min.js

520 ms

ddsmoothmenu.js

ddsmoothmenu.js

1003 ms

jquery.cookie.js

jquery.cookie.js

1004 ms

jqueryfontsizechange.js

jqueryfontsizechange.js

1017 ms

rollover.js

rollover.js

1019 ms

script.js

script.js

1041 ms

if_oshirase2.php

if_oshirase2.php

319 ms

index-back.jpg

index-back.jpg

2234 ms

logo.png

logo.png

693 ms

index-serback.png

index-serback.png

521 ms

ser_01.gif

ser_01.gif

564 ms

size01.gif

size01.gif

543 ms

size02.gif

size02.gif

819 ms

size03.gif

size03.gif

1020 ms

ser_02.gif

ser_02.gif

1038 ms

ser_box01.gif

ser_box01.gif

1048 ms

ser_box02.gif

ser_box02.gif

1195 ms

ser_facebook.gif

ser_facebook.gif

1338 ms

ser_twitter.gif

ser_twitter.gif

1537 ms

index_menuback-bg.png

index_menuback-bg.png

1555 ms

index-menuback.png

index-menuback.png

1909 ms

menu_top1301.png

menu_top1301.png

2055 ms

index-back2.jpg

index-back2.jpg

2004 ms

index-koushin.gif

index-koushin.gif

2038 ms

index-txt01.gif

index-txt01.gif

2073 ms

index-gyoji.gif

index-gyoji.gif

2409 ms

index-txt02.gif

index-txt02.gif

2521 ms

bnr_top04.jpg

bnr_top04.jpg

2899 ms

bnr_top02.jpg

bnr_top02.jpg

2886 ms

bnr_top03.jpg

bnr_top03.jpg

2938 ms

bnr_top01.jpg

bnr_top01.jpg

3258 ms

bnr_top05.jpg

bnr_top05.jpg

3271 ms

bnr_top06.jpg

bnr_top06.jpg

3209 ms

bnr_blog4.jpg

bnr_blog4.jpg

3750 ms

widgets.js

widgets.js

91 ms

search.json

search.json

67 ms

size01_ov.gif

size01_ov.gif

3384 ms

size02_ov.gif

size02_ov.gif

3406 ms

size03_ov.gif

size03_ov.gif

3695 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

56 ms

settings

settings

68 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

22 ms

rengeinhon

rengeinhon

55 ms

jquery144.js

jquery144.js

3945 ms

ticker.js

ticker.js

3476 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

25 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

64 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

87 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

84 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

112 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

115 ms

_buildManifest.js

_buildManifest.js

124 ms

_ssgManifest.js

_ssgManifest.js

124 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

22 ms

1755.07a49c40b12af4f75780.js

1755.07a49c40b12af4f75780.js

22 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

24 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

48 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

41 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

57 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

19 ms

not_bg1_2.gif

not_bg1_2.gif

174 ms

not_bg2.gif

not_bg2.gif

521 ms

Accessibility Review

rengein.jp accessibility score

64

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

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

rengein.jp best practices score

58

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

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

SEO Factors

rengein.jp SEO score

69

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rengein.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Rengein.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

rengein.jp

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