Tools & Wizards About Us
jinja.in screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

jinja.in

神社検索なら神社ポータルサイトの日本神社

Page Load Speed

4.1 sec in total

First Response

537 ms

Resources Loaded

3.4 sec

Page Rendered

172 ms

jinja.in screenshot

About Website

Welcome to jinja.in homepage info - get ready to check Jinja best content for Japan right away, or after learning these important things about jinja.in

日本神社は日本全国の神社を検索出来る神社ポータルサイトです。 お近くの神社の住所・由緒・祭神・地図などの情報を検索することが出来ます。

Visit jinja.in

Key Findings

We analyzed Jinja.in page load time and found that the first response time was 537 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

jinja.in performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value9.1 s

13/100

10%

TBT (Total Blocking Time)

Value1,190 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.0 s

6/100

10%

Network Requests Diagram

jinja.in

537 ms

www.jinja.in

527 ms

www.jinja.in

709 ms

css_4a69663d503909eaeb87ee20c8c48e2e.css

175 ms

js_e40ae87fd30138cfe1d95c3e316ea03a.js

522 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 31% of them (9 requests) were addressed to the original Jinja.in, 21% (6 requests) were made to Apis.google.com and 7% (2 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Xml.affiliate.rakuten.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 50.9 kB (9%)

Content Size

586.4 kB

After Optimization

535.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jinja.in main page is 586.4 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. 30% of websites need less resources to load. Javascripts take 406.8 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 20.5 kB

  • Original 28.6 kB
  • After minification 25.9 kB
  • After compression 8.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 20.5 kB or 72% of the original size.

Image Optimization

-0%

Potential reduce by 49 B

  • Original 137.6 kB
  • After minification 137.6 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. Jinja images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 27.5 kB

  • Original 406.8 kB
  • After minification 406.8 kB
  • After compression 379.3 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. This website has mostly compressed JavaScripts.

CSS Optimization

-21%

Potential reduce by 2.9 kB

  • Original 13.4 kB
  • After minification 13.4 kB
  • After compression 10.5 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. Jinja.in needs all CSS files to be minified and compressed as it can save up to 2.9 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (54%)

Requests Now

24

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jinja. 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 as a result speed up the page load time.

Network Requests Diagram

jinja.in

jinja.in

537 ms

www.jinja.in

www.jinja.in

527 ms

www.jinja.in

www.jinja.in

709 ms

css_4a69663d503909eaeb87ee20c8c48e2e.css

css_4a69663d503909eaeb87ee20c8c48e2e.css

175 ms

js_e40ae87fd30138cfe1d95c3e316ea03a.js

js_e40ae87fd30138cfe1d95c3e316ea03a.js

522 ms

js

js

48 ms

adsbygoogle.js

adsbygoogle.js

119 ms

rakuten_widget.js

rakuten_widget.js

1181 ms

jquery.min.js

jquery.min.js

29 ms

logo.jpg

logo.jpg

208 ms

head_r2_c2.jpg

head_r2_c2.jpg

725 ms

head_r6_c1.jpg

head_r6_c1.jpg

358 ms

widgets.js

widgets.js

32 ms

like.php

like.php

320 ms

plusone.js

plusone.js

45 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

11 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

39 ms

fastbutton

fastbutton

55 ms

postmessageRelay

postmessageRelay

73 ms

developers.google.com

developers.google.com

315 ms

3604799710-postmessagerelay.js

3604799710-postmessagerelay.js

21 ms

rpc:shindig_random.js

rpc:shindig_random.js

16 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

5 ms

TttXWwYVW0v.js

TttXWwYVW0v.js

25 ms

FEppCFCt76d.png

FEppCFCt76d.png

14 ms

mw_dynamic_view.html

mw_dynamic_view.html

416 ms

menu-leaf.png

menu-leaf.png

172 ms

ga.js

ga.js

27 ms

__utm.gif

__utm.gif

11 ms

Accessibility Review

jinja.in accessibility score

86

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.

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

<frame> or <iframe> elements do not have a title

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

jinja.in 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

jinja.in SEO score

98

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Jinja.in 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 Jinja.in 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

jinja.in

Open Graph description is not detected on the main page of Jinja. 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: