Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

inari.jp

伏見稲荷大社

Page Load Speed

11.6 sec in total

First Response

1.2 sec

Resources Loaded

10.2 sec

Page Rendered

158 ms

inari.jp screenshot

About Website

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.jp

Key Findings

We 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.

Performance Metrics

inari.jp performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.066

97/100

15%

TTI (Time to Interactive)

Value5.8 s

67/100

10%

Network Requests Diagram

inari.jp

1244 ms

import.css

345 ms

index.css

512 ms

nivo-slider.css

347 ms

import.js

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 Optimization Overview & Recommendations

Page size can be reduced by 321.9 kB (14%)

Content Size

2.2 MB

After Optimization

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.

HTML Optimization

-82%

Potential reduce by 15.4 kB

  • Original 18.9 kB
  • After minification 15.8 kB
  • After compression 3.5 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.

Image Optimization

-2%

Potential reduce by 31.1 kB

  • Original 1.8 MB
  • After minification 1.8 MB

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.

JavaScript Optimization

-70%

Potential reduce by 262.4 kB

  • Original 373.2 kB
  • After minification 347.2 kB
  • After compression 110.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 262.4 kB or 70% of the original size.

CSS Optimization

-79%

Potential reduce by 12.9 kB

  • Original 16.3 kB
  • After minification 10.8 kB
  • After compression 3.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. 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.

Requests Breakdown

Number of requests can be reduced by 18 (23%)

Requests Now

79

After Optimization

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.

Accessibility Review

inari.jp accessibility score

67

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<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

High

Image elements do not have [alt] attributes

Best Practices

inari.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

inari.jp SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    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.

Social Sharing Optimization

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: