11.6 sec in total
1.2 sec
10.2 sec
158 ms
Visit inari.jp now to see the best up-to-date Inari content for Japan and also check out these interesting facts you probably never knew about inari.jp
1300年にわたって、人々の信仰を集め続ける「お稲荷さん」の総本宮 伏見稲荷大社の公式ホームページ
Visit inari.jpWe analyzed Inari.jp page load time and found that the first response time was 1.2 sec and then it took 10.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
inari.jp performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value10.7 s
0/100
25%
Value8.2 s
20/100
10%
Value40 ms
100/100
30%
Value0.066
97/100
15%
Value5.8 s
67/100
10%
1244 ms
345 ms
512 ms
347 ms
360 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 98% of them (79 requests) were addressed to the original Inari.jp, 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.9 sec) belongs to the original domain Inari.jp.
Page size can be reduced by 321.9 kB (14%)
2.2 MB
1.9 MB
In fact, the total size of Inari.jp main page is 2.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. 20% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 15.4 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 3.2 kB, which is 17% 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 15.4 kB or 82% of the original size.
Potential reduce by 31.1 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. Inari images are well optimized though.
Potential reduce by 262.4 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 262.4 kB or 70% of the original size.
Potential reduce by 12.9 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. Inari.jp needs all CSS files to be minified and compressed as it can save up to 12.9 kB or 79% of the original size.
Number of requests can be reduced by 18 (23%)
79
61
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Inari. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
inari.jp
1244 ms
import.css
345 ms
index.css
512 ms
nivo-slider.css
347 ms
import.js
360 ms
jquery.nivo.slider.js
956 ms
reset.css
337 ms
font.css
398 ms
format.css
450 ms
layout.css
447 ms
site.init.js
543 ms
index.init.js
700 ms
jquery-1.7.2.min.js
1233 ms
jquery.easing.js
547 ms
jquery-ui-1.8.21.custom.min.js
1828 ms
jquery.cookie.js
531 ms
jquery.rollover.js
520 ms
font.util.js
701 ms
jquery.scrollTo-1.4.2-min.js
882 ms
smoothscroll.js
891 ms
ga.js
56 ms
bg_visual_area.gif
197 ms
logo.gif
209 ms
font_small.gif
398 ms
font_medium.gif
409 ms
font_large.gif
421 ms
icon_arrow.gif
463 ms
btn_access.gif
609 ms
btn_inarikai.gif
647 ms
gnav1.gif
766 ms
gnav2.gif
793 ms
gnav3.gif
808 ms
gnav4.gif
851 ms
gnav5.gif
965 ms
gnav6.gif
1016 ms
main_img5.jpg
2413 ms
main_img0.jpg
2716 ms
main_img1.jpg
2434 ms
main_img2.jpg
2407 ms
main_img3.jpg
2622 ms
img013.jpg
2573 ms
inarisyoka.jpg
3760 ms
h2_01.gif
2757 ms
month_01.png
2831 ms
month_02.png
2921 ms
month_03.png
2984 ms
month_04.png
3064 ms
month_05.png
3118 ms
month_06.png
3181 ms
month_07.png
3281 ms
month_08.png
3347 ms
month_09.png
3477 ms
month_10.png
3462 ms
month_11.png
3583 ms
month_12.png
3700 ms
month_pos_01.png
3746 ms
IMG_0364.jpg
4886 ms
__utm.gif
11 ms
kencyasai-April_01.jpg
4584 ms
sangyousai_01.jpg
4773 ms
IMG_3466.jpg
4820 ms
inarisai_shinkousai_01.jpg
4720 ms
ajax-loader.gif
3751 ms
h2_02.gif
4107 ms
bg_news_cat03.gif
4354 ms
bg_news_cat01.gif
4505 ms
bnr_kitou.gif
4702 ms
bnr_map.gif
4782 ms
bnr_omamori.gif
4741 ms
bnr_honcho.gif
4844 ms
bnr_monogatari.gif
4728 ms
bnr_torii.gif
4750 ms
inari.jp
4050 ms
gnav1_on.gif
3562 ms
gnav2_on.gif
3521 ms
gnav3_on.gif
3465 ms
gnav4_on.gif
3425 ms
gnav5_on.gif
3472 ms
gnav6_on.gif
3559 ms
font_medium_on.gif
3528 ms
font_medium_on_on.gif
3751 ms
inari.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.
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
inari.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
inari.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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inari.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 Inari.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.
inari.jp
Open Graph description is not detected on the main page of Inari. 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: