TENRIKYO.OR.JP 天理教

tenrikyo.or.jp Website Information

Daily Unique Visits: 1,235

Daily Page Views: 2,470

Income Per Day: $8

Estimated Value: $1,920

This website is located in Japan and is using following IP address 114.160.46.11. See the complete list of popular websites hosted in Japan.

tenrikyo.or.jp is registered under .JP top-level domain. Please check other sites in .JP zone.

Website tenrikyo.or.jp is using the following name servers:

  • ns1.tenrikyo.or.jp
  • ns1.mahoroba.ne.jp
  • ns0.tenrikyo.or.jp

and is probably hosted by VECTANT ARTERIA Networks Corporation, JP. See the full list of other websites hosted by VECTANT ARTERIA Networks Corporation, JP.

The highest website tenrikyo.or.jp position in Alexa rank database was 33216 and the lowest rank position was 993177. Current position of tenrikyo.or.jp in Alexa rank database is 580848.

Desktop speed score of tenrikyo.or.jp (83/100) is better than the results of 76.15% of other sites and shows that the page is performing great on desktop computers.

Mobile usability score of tenrikyo.or.jp (100/100) is better than the results of 100% of other sites and means that the page is mobile-friendly.

Mobile speed score of tenrikyo.or.jp (63/100) is better than the results of 61.76% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

tenrikyo.or.jp Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.


tenrikyo.or.jp whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.


[ JPRS database provides information on network administration. Its use is ]
[ restricted to network administration purposes. For further information, ]
[ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e' ]
[ at the end of command, e.g. 'whois -h whois.jprs.jp xxx/e'. ]
Domain Information: [ドメイン情報]
a. [ドメイン名] TENRIKYO.OR.JP
e. [そしきめい] しゅうきょうほうじん てんりきょう
f. [組織名] 宗教法人 天理教
g. [Organization] Religious Corporation, Tenrikyo Church
Headquarters
k. [組織種別] 宗教法人
l. [Organization Type] Religious Corporation
m. [登録担当者] HM334JP
n. [技術連絡担当者] TG338JP
n. [技術連絡担当者] TK9133JP
n. [技術連絡担当者] TS612JP
p. [ネームサーバ] ns0.tenrikyo.or.jp
p. [ネームサーバ] ns1.mahoroba.ne.jp
p. [ネームサーバ] www.tenrikyo.or.jp
s. [署名鍵]
[状態] Connected (2024/11/30)
[登録年月日] 1996/11/22
[接続年月日] 1997/03/11
[最終更新] 2023/12/01 01:02:44 (JST)

tenrikyo.or.jp server information

Servers Location

tenrikyo.or.jp desktop page speed rank

Last tested: 2019-06-23


Desktop Speed Medium
83/100

tenrikyo.or.jp Desktop Speed Test Quick Summary


priority - 8Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 3 blocking CSS resources. This causes a delay in rendering your page.

Optimize CSS Delivery of the following:

https://www.tenrikyo.or.jp/css/enter.css
https://www.tenrikyo.or.jp/css/html5reset-1.6.1.css
https://www.tenrikyo.or.jp/css/common.css

priority - 7Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://tenrikyo.or.jp/
http://www.tenrikyo.or.jp/
https://www.tenrikyo.or.jp/

priority - 3Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://www.tenrikyo.or.jp/css/common.css (24 hours)
https://www.tenrikyo.or.jp/css/enter.css (24 hours)
https://www.tenrikyo.or.jp/css/html5reset-1.6.1.css (24 hours)
https://www.tenrikyo.or.jp/js/enter.js (24 hours)
https://www.tenrikyo.or.jp/js/prototype.min.js (24 hours)

priority - 0Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 2KiB (39% reduction).

Compressing https://www.tenrikyo.or.jp/images/enter/enter_bg.jpg could save 1.1KiB (74% reduction).
Compressing https://www.tenrikyo.or.jp/bn_doyusha-store_daitop.png could save 952B (25% reduction).

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 1.5KiB (31% reduction).

Minifying https://www.tenrikyo.or.jp/css/common.css could save 1.1KiB (33% reduction) after compression.
Minifying https://www.tenrikyo.or.jp/css/enter.css could save 257B (30% reduction) after compression.
Minifying https://www.tenrikyo.or.jp/css/html5reset-1.6.1.css could save 195B (24% reduction) after compression.

priority - 0Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 316B (35% reduction).

Minifying https://www.tenrikyo.or.jp/js/enter.js could save 316B (35% reduction) after compression.

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 267B (11% reduction).

Minifying https://www.tenrikyo.or.jp/ could save 267B (11% reduction) after compression.

tenrikyo.or.jp Desktop Resource Breakdown

Total Resources19
Number of Hosts5
Static Resources13
JavaScript Resources4
CSS Resources3

tenrikyo.or.jp mobile page speed rank

Last tested: 2019-07-06


Mobile Speed Bad
63/100

tenrikyo.or.jp Mobile Speed Test Quick Summary


priority - 32Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 3 blocking CSS resources. This causes a delay in rendering your page.

Optimize CSS Delivery of the following:

https://www.tenrikyo.or.jp/css/enter.css
https://www.tenrikyo.or.jp/css/html5reset-1.6.1.css
https://www.tenrikyo.or.jp/css/common.css

priority - 26Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://tenrikyo.or.jp/
http://www.tenrikyo.or.jp/
https://www.tenrikyo.or.jp/

priority - 5Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://www.tenrikyo.or.jp/css/common.css (24 hours)
https://www.tenrikyo.or.jp/css/enter.css (24 hours)
https://www.tenrikyo.or.jp/css/html5reset-1.6.1.css (24 hours)
https://www.tenrikyo.or.jp/js/enter.js (24 hours)
https://www.tenrikyo.or.jp/js/prototype.min.js (24 hours)

priority - 0Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 2KiB (39% reduction).

Compressing https://www.tenrikyo.or.jp/images/enter/enter_bg.jpg could save 1.1KiB (74% reduction).
Compressing https://www.tenrikyo.or.jp/bn_doyusha-store_daitop.png could save 952B (25% reduction).

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 1.5KiB (31% reduction).

Minifying https://www.tenrikyo.or.jp/css/common.css could save 1.1KiB (33% reduction) after compression.
Minifying https://www.tenrikyo.or.jp/css/enter.css could save 257B (30% reduction) after compression.
Minifying https://www.tenrikyo.or.jp/css/html5reset-1.6.1.css could save 195B (24% reduction) after compression.

priority - 0Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 316B (35% reduction).

Minifying https://www.tenrikyo.or.jp/js/enter.js could save 316B (35% reduction) after compression.

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 269B (11% reduction).

Minifying https://www.tenrikyo.or.jp/ could save 269B (11% reduction) after compression.

tenrikyo.or.jp Mobile Resource Breakdown

Total Resources19
Number of Hosts5
Static Resources13
JavaScript Resources4
CSS Resources3

tenrikyo.or.jp mobile page usability

Last tested: 2019-07-06


Mobile Usability Good
100/100

tenrikyo.or.jp HTML validation

Errors

Attribute “xmlns:og” not allowed here.

Line: 18 Column: 32 - 48
"...IE)]><!--> <html lang="ja" xmlns:og="http://ogp.me/ns#" xmlns:fb="http://www.facebook.com/2008/fbml" xmlns:mixi="http://mixi-platform.com/ns#"><!--<!..."

Attribute “xmlns:fb” not allowed here.

Line: 18 Column: 32 - 48
"...IE)]><!--> <html lang="ja" xmlns:og="http://ogp.me/ns#" xmlns:fb="http://www.facebook.com/2008/fbml" xmlns:mixi="http://mixi-platform.com/ns#"><!--<!..."

Attribute “xmlns:mixi” not allowed here.

Line: 18 Column: 32 - 48
"...IE)]><!--> <html lang="ja" xmlns:og="http://ogp.me/ns#" xmlns:fb="http://www.facebook.com/2008/fbml" xmlns:mixi="http://mixi-platform.com/ns#"><!--<!..."

A “meta” element with an “http-equiv” attribute whose value is “X-UA-Compatible” must have a “content” attribute with the value “IE=edge”.

Line: 21 Column: 1 - 59
"...UTF-8" /> <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE9"> <!--[..."

Bad value “Content-Style-Type” for attribute “http-equiv” on element “meta”.

Line: 31 Column: 1 - 59
"...のきしん隊" /> <meta http-equiv="Content-Style-Type" content="text/css" /> <meta..."

Bad value “Content-Script-Type” for attribute “http-equiv” on element “meta”.

Line: 32 Column: 1 - 67
"...t/css" /> <meta http-equiv="Content-Script-Type" content="text/javascript" /> <!-- ..."

Warnings

Attribute with the local name “xmlns:og” is not serializable as XML 1.0.

Line: 18 Column: 32 - 48
"...IE)]><!--> <html lang="ja" xmlns:og="http://ogp.me/ns#" xmlns:fb="http://www.facebook.com/2008/fbml" xmlns:mixi="http://mixi-platform.com/ns#"><!--<!..."

Attribute with the local name “xmlns:fb” is not serializable as XML 1.0.

Line: 18 Column: 32 - 48
"...IE)]><!--> <html lang="ja" xmlns:og="http://ogp.me/ns#" xmlns:fb="http://www.facebook.com/2008/fbml" xmlns:mixi="http://mixi-platform.com/ns#"><!--<!..."

Attribute with the local name “xmlns:mixi” is not serializable as XML 1.0.

Line: 18 Column: 32 - 48
"...IE)]><!--> <html lang="ja" xmlns:og="http://ogp.me/ns#" xmlns:fb="http://www.facebook.com/2008/fbml" xmlns:mixi="http://mixi-platform.com/ns#"><!--<!..."

tenrikyo.or.jp similar domains

Similar domains:
www.tenrikyo.com
www.tenrikyo.net
www.tenrikyo.org
www.tenrikyo.info
www.tenrikyo.biz
www.tenrikyo.us
www.tenrikyo.mobi
www.enrikyo.or.jp
www.tenrikyo.or.jp
www.renrikyo.or.jp
www.trenrikyo.or.jp
www.rtenrikyo.or.jp
www.fenrikyo.or.jp
www.tfenrikyo.or.jp
www.ftenrikyo.or.jp
www.genrikyo.or.jp
www.tgenrikyo.or.jp
www.gtenrikyo.or.jp
www.yenrikyo.or.jp
www.tyenrikyo.or.jp
www.ytenrikyo.or.jp
www.tnrikyo.or.jp
www.twnrikyo.or.jp
www.tewnrikyo.or.jp
www.twenrikyo.or.jp
www.tsnrikyo.or.jp
www.tesnrikyo.or.jp
www.tsenrikyo.or.jp
www.tdnrikyo.or.jp
www.tednrikyo.or.jp
www.tdenrikyo.or.jp
www.trnrikyo.or.jp
www.ternrikyo.or.jp
www.terikyo.or.jp
www.tebrikyo.or.jp
www.tenbrikyo.or.jp
www.tebnrikyo.or.jp
www.tehrikyo.or.jp
www.tenhrikyo.or.jp
www.tehnrikyo.or.jp
www.tejrikyo.or.jp
www.tenjrikyo.or.jp
www.tejnrikyo.or.jp
www.temrikyo.or.jp
www.tenmrikyo.or.jp
www.temnrikyo.or.jp
www.tenikyo.or.jp
www.teneikyo.or.jp
www.tenreikyo.or.jp
www.tenerikyo.or.jp
www.tendikyo.or.jp
www.tenrdikyo.or.jp
www.tendrikyo.or.jp
www.tenfikyo.or.jp
www.tenrfikyo.or.jp
www.tenfrikyo.or.jp
www.tentikyo.or.jp
www.tenrtikyo.or.jp
www.tentrikyo.or.jp
www.tenrkyo.or.jp
www.tenrukyo.or.jp
www.tenriukyo.or.jp
www.tenruikyo.or.jp
www.tenrjkyo.or.jp
www.tenrijkyo.or.jp
www.tenrjikyo.or.jp
www.tenrkkyo.or.jp
www.tenrikkyo.or.jp
www.tenrkikyo.or.jp
www.tenrokyo.or.jp
www.tenriokyo.or.jp
www.tenroikyo.or.jp
www.tenriyo.or.jp
www.tenrijyo.or.jp
www.tenrikjyo.or.jp
www.tenriiyo.or.jp
www.tenrikiyo.or.jp
www.tenriikyo.or.jp
www.tenrimyo.or.jp
www.tenrikmyo.or.jp
www.tenrimkyo.or.jp
www.tenrilyo.or.jp
www.tenriklyo.or.jp
www.tenrilkyo.or.jp
www.tenrioyo.or.jp
www.tenrikoyo.or.jp
www.tenriko.or.jp
www.tenrikto.or.jp
www.tenrikyto.or.jp
www.tenriktyo.or.jp
www.tenrikgo.or.jp
www.tenrikygo.or.jp
www.tenrikgyo.or.jp
www.tenrikho.or.jp
www.tenrikyho.or.jp
www.tenrikhyo.or.jp
www.tenrikuo.or.jp
www.tenrikyuo.or.jp
www.tenrikuyo.or.jp
www.tenriky.or.jp
www.tenrikyi.or.jp
www.tenrikyoi.or.jp
www.tenrikyio.or.jp
www.tenrikyk.or.jp
www.tenrikyok.or.jp
www.tenrikyko.or.jp
www.tenrikyl.or.jp
www.tenrikyol.or.jp
www.tenrikylo.or.jp
www.tenrikyp.or.jp
www.tenrikyop.or.jp
www.tenrikypo.or.jp

tenrikyo.or.jp Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.


tenrikyo.or.jp TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.