7.1 sec in total
1.1 sec
5.5 sec
446 ms
Visit kinpusen.or.jp now to see the best up-to-date Kinpusen content for Japan and also check out these interesting facts you probably never knew about kinpusen.or.jp
奈良県 金峯山修験本宗 総本山 金峯山寺ウェブサイト。国宝・世界遺産の仁王門、蔵王堂の他、日本最大秘仏である金剛蔵王大権現。全国の修験者・山伏が集う修験道の中心寺院となっています。
Visit kinpusen.or.jpWe analyzed Kinpusen.or.jp page load time and found that the first response time was 1.1 sec and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
kinpusen.or.jp performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value26.4 s
0/100
25%
Value15.3 s
1/100
10%
Value1,570 ms
13/100
30%
Value0.549
13/100
15%
Value33.8 s
0/100
10%
1095 ms
335 ms
510 ms
343 ms
541 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 92% of them (100 requests) were addressed to the original Kinpusen.or.jp, 4% (4 requests) were made to Sync5-res.digitalstage.jp and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Kinpusen.or.jp.
Page size can be reduced by 797.5 kB (24%)
3.3 MB
2.5 MB
In fact, the total size of Kinpusen.or.jp main page is 3.3 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. 60% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 31.2 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 7.5 kB, which is 20% 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 31.2 kB or 83% of the original size.
Potential reduce by 122.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. Kinpusen images are well optimized though.
Potential reduce by 298.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 298.6 kB or 72% of the original size.
Potential reduce by 345.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. Kinpusen.or.jp needs all CSS files to be minified and compressed as it can save up to 345.4 kB or 87% of the original size.
Number of requests can be reduced by 43 (40%)
107
64
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kinpusen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 31 to 1 for CSS and as a result speed up the page load time.
kinpusen.or.jp
1095 ms
style.css
335 ms
_else.css
510 ms
style.css
343 ms
index.css
541 ms
script.js
1544 ms
common.css
167 ms
pagelayout.css
689 ms
printlayout.css
332 ms
blockskin.css
1188 ms
wp_style.css
727 ms
overwrite.css
387 ms
style.css
291 ms
theme.css
186 ms
_else.css
186 ms
style.css
354 ms
_else.css
172 ms
jquery-1.8.3.min.js
706 ms
jquery.easing.1.3.js
168 ms
head.load.min.js
172 ms
movie.js
332 ms
parts.js
342 ms
fx.js
512 ms
override.js
367 ms
load.js
498 ms
analytics.js
48 ms
_area_side_a.css
186 ms
_area_billboard.css
178 ms
_area_main.css
172 ms
_area_header.css
178 ms
_area_side_b.css
170 ms
_area_footer.css
172 ms
_block_footer.css
333 ms
_block_header.css
340 ms
_block_main_food.css
341 ms
_block_side_a.css
353 ms
_block_side_b.css
353 ms
_block_main.css
368 ms
_block_main_topics.css
496 ms
side_yellow.css
510 ms
_block_main_news.css
511 ms
header.css
528 ms
sync.css
544 ms
json.js
559 ms
sync.js
761 ms
home_main-image2.png
1757 ms
footer.png
557 ms
sign.png
653 ms
home.png
672 ms
sign.png
673 ms
8fd089ee.png
697 ms
sign.png
728 ms
8bf82e8.png
817 ms
sign.png
842 ms
8f8497e7.png
841 ms
sign.png
873 ms
8fc8ds.png
911 ms
sign.png
982 ms
8ds8e96.png
1012 ms
sign.png
1011 ms
82a882dc82e082e8.png
1049 ms
sign.png
1095 ms
mainmenu_06.png
1481 ms
mainmenu_over_06.png
1350 ms
mainmenu_08.png
1182 ms
collect
28 ms
mainmenu_over_08.png
1246 ms
mainmenu_10.png
1138 ms
mainmenu_over_10.png
1195 ms
8fc8ds-1_17.png
1501 ms
8fc8ds-2_17.png
1527 ms
mainmenu_18.png
1354 ms
mainmenu_over_18.png
1261 ms
omamoriofuda_19.png
1483 ms
omamoriofuda_ov_19.png
1367 ms
sign.png
1419 ms
83x83n838a815b839383v838783b83g202014-08-042018.40.42.png
1509 ms
83x83n838a815b839383v838783b83g202014-08-042018.42.47.png
1506 ms
83x83n838a815b839383v838783b83g202014-08-042018.45.28.png
1383 ms
1354692.jpg
1432 ms
83x83n838a815b839383v838783b83g202014-08-042018.51.57.png
1436 ms
8034360.jpg
1458 ms
sign.png
1455 ms
qr_code.jpg
1383 ms
sign.png
1367 ms
sign.png
1439 ms
1_ic_linktop.png
1418 ms
hibutsu_bunner_03.png
1416 ms
jquery.socialbutton.js
374 ms
umashiuruwashi_21.png
1388 ms
gien_bunner_19.png
1379 ms
side_news_26.png
1367 ms
side_news_28.png
1415 ms
side_news_30.png
1379 ms
94fc82b582ab93fa967b_16.png
1328 ms
side_news_32.png
1363 ms
img20160204164413156158.jpg
1367 ms
side_b_20.png
1356 ms
sign.png
1367 ms
result.png
1284 ms
like.php
175 ms
sign.png
1178 ms
result.png
1195 ms
sign.png
1196 ms
result.png
1188 ms
vpc6VNjRPXV.js
40 ms
LVx-xkvaJ0b.png
30 ms
side_c_20.png
1159 ms
sign.png
1117 ms
kinpusen.or.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
kinpusen.or.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
kinpusen.or.jp SEO score
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
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kinpusen.or.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 Kinpusen.or.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.
kinpusen.or.jp
Open Graph data is detected on the main page of Kinpusen. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: