9.8 sec in total
1.2 sec
8.3 sec
305 ms
Welcome to nihondokan.co.jp homepage info - get ready to check Nihondokan best content right away, or after learning these important things about nihondokan.co.jp
日本道観では、長年に渡りタオイズムの研究を行い、各国の道教・タオイストの皆様との交流を深めながら、研究成果を世界に伝える活動をしています。
Visit nihondokan.co.jpWe analyzed Nihondokan.co.jp page load time and found that the first response time was 1.2 sec and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
nihondokan.co.jp performance score
name
value
score
weighting
Value8.9 s
0/100
10%
Value15.0 s
0/100
25%
Value17.8 s
0/100
10%
Value860 ms
33/100
30%
Value0.211
59/100
15%
Value26.4 s
0/100
10%
1211 ms
490 ms
901 ms
369 ms
370 ms
Our browser made a total of 145 requests to load all elements on the main page. We found that 65% of them (94 requests) were addressed to the original Nihondokan.co.jp, 6% (8 requests) were made to Apis.google.com and 6% (8 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Nihondokan.co.jp.
Page size can be reduced by 546.8 kB (62%)
882.7 kB
335.8 kB
In fact, the total size of Nihondokan.co.jp main page is 882.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. 60% of websites need less resources to load. Javascripts take 349.7 kB which makes up the majority of the site volume.
Potential reduce by 116.1 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 116.1 kB or 81% of the original size.
Potential reduce by 29.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. Obviously, Nihondokan needs image optimization as it can save up to 29.5 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 277.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 277.9 kB or 79% of the original size.
Potential reduce by 123.4 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. Nihondokan.co.jp needs all CSS files to be minified and compressed as it can save up to 123.4 kB or 85% of the original size.
Number of requests can be reduced by 55 (39%)
141
86
The browser has sent 141 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nihondokan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
nihondokan.co.jp
1211 ms
base.css
490 ms
design.css
901 ms
nav.js
369 ms
mm_css_menu.js
370 ms
AC_RunActiveContent.js
391 ms
jquery.js
1597 ms
g_analytics.js
735 ms
line-button.js
472 ms
line-button.js
507 ms
analytics.js
23 ms
bn_books_top.gif
662 ms
logo02.gif
200 ms
h_tel02.gif
328 ms
ic_faq.gif
328 ms
ic_sitemap.gif
389 ms
ic_mobile.gif
384 ms
ic_cir_bro01.gif
406 ms
bn_appo2_resize.gif
660 ms
bn_contact2_resize.gif
688 ms
bn_login2_resize.gif
759 ms
g_home_ov.gif
777 ms
g_about.gif
774 ms
g_taoism.gif
814 ms
g_kitoha.gif
966 ms
g_training.gif
1046 ms
g_special.gif
1099 ms
g_relationship.gif
1112 ms
menu_top.gif
1119 ms
menu_01.gif
1165 ms
menu_02.gif
1323 ms
menu_03.gif
1361 ms
menu_04.gif
1404 ms
menu_05.gif
1478 ms
menu_06.gif
1502 ms
menu__btm.gif
1556 ms
key_01.gif
2170 ms
key_105th.gif
2145 ms
key_03.gif
2195 ms
key_04.gif
2324 ms
key_05.gif
2268 ms
contact2.gif
1912 ms
contact3.gif
2302 ms
l_training.gif
2503 ms
l_first.gif
2528 ms
l_course.gif
2501 ms
l_session.gif
2607 ms
cse.js
96 ms
l_flow.gif
2630 ms
widgets.js
86 ms
collect
15 ms
jsapi
32 ms
sdk.js
201 ms
plusone.js
84 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
34 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
35 ms
default+ja.css
10 ms
default.css
24 ms
default+ja.I.js
52 ms
default.css
79 ms
syndication
192 ms
307349080915460096
242 ms
l_narrative.gif
2517 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
53 ms
cb=gapi.loaded_0
68 ms
cb=gapi.loaded_1
87 ms
fastbutton
139 ms
async-ads.js
118 ms
google_custom_search_watermark.gif
55 ms
small-logo.png
33 ms
search_box_icon.png
33 ms
clear.png
110 ms
l_faq_02.gif
2497 ms
mailmag.gif
2540 ms
postmessageRelay
93 ms
86 ms
xd_arbiter.php
284 ms
xd_arbiter.php
420 ms
cb=gapi.loaded_0
30 ms
cb=gapi.loaded_1
27 ms
pamphlet.gif
2520 ms
facebook.jpg
2722 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
35 ms
bn_international.gif
2597 ms
proxy.jpg
211 ms
3193398744-postmessagerelay.js
224 ms
rpc:shindig_random.js
32 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
20 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
18 ms
DokanMark_normal.jpg
237 ms
_________normal.jpg
211 ms
Sl987l1T_normal
214 ms
Mv4fgDci_normal.jpg
209 ms
1c2697e458f0a79feb2bd54b886965ce_normal.jpeg
213 ms
1NeNooOp_normal.jpeg
276 ms
885a13f53136f80090eedc15fea84cf0_normal.png
214 ms
Tadanori_Yokoo_normal.jpg
214 ms
cn_sim.gif
2421 ms
cb=gapi.loaded_0
7 ms
mobile.gif
2526 ms
mission01.gif
2476 ms
mission02.gif
2456 ms
t_world.gif
2534 ms
bn_tpcs_150724.gif
2651 ms
jot.html
2 ms
bn_tpcs_151107.jpg
2450 ms
earth_4.jpg
2813 ms
t_books_pickup_1603.gif
2438 ms
book_ikinuku.gif
2914 ms
t_tit_1603.png
2549 ms
btn_order.png
2615 ms
t_topics.gif
2501 ms
ic_rss.gif
2536 ms
ic_topics_all.gif
2573 ms
ic_new.gif
2640 ms
sakeburo_2.gif
2698 ms
konronnoyu_s_2.jpg
2812 ms
book_30words.jpg
2466 ms
bn_roushi.gif
2147 ms
t_special02.gif
2246 ms
t_taoism02.gif
2238 ms
t_dokyo02.gif
2289 ms
bn_kodawaranai.gif
2316 ms
bn_dragon.gif
2364 ms
bn_105th.gif
2205 ms
bn_anniversary_34.jpg
2390 ms
shopping_nocam.gif
2246 ms
01.gif
2288 ms
08.gif
2282 ms
06.gif
2287 ms
02.gif
2248 ms
00.gif
2226 ms
key_back.png
2319 ms
topics_bkg.gif
2255 ms
tri_gold_new.gif
2176 ms
topics_box_bkg.gif
2295 ms
r_nav_bkg.gif
2230 ms
ic_cir_ora01.gif
2192 ms
r_nav_btm.gif
2386 ms
ic_sq_bro01.gif
2308 ms
contact2_ov.gif
165 ms
menu_02_ov.gif
212 ms
like.php
78 ms
wy1X4hBW7e7.js
295 ms
LVx-xkvaJ0b.png
332 ms
nihondokan.co.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
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
<html> element does not have a [lang] attribute
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.
nihondokan.co.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
nihondokan.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nihondokan.co.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 Nihondokan.co.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.
nihondokan.co.jp
Open Graph description is not detected on the main page of Nihondokan. 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: