Tools & Wizards About Us
yaokami.jp screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

yaokami.jp

八百万の神 - 日本の神社・寺院検索サイト

Page Load Speed

4 sec in total

First Response

676 ms

Resources Loaded

3 sec

Page Rendered

391 ms

yaokami.jp screenshot

About Website

Welcome to yaokami.jp homepage info - get ready to check Yaokami best content for Japan right away, or after learning these important things about yaokami.jp

神道と仏教の信仰に基づき作られた約15万件の⛩神社・卍寺院を掲載。名所・巡拝地、地域、電車路線・駅、バス路線、系列・宗派、祭神・仏尊から探すことができます。登録会員の投稿写真・口伝情報や、独自の電子御朱印機能もあります。

Visit yaokami.jp

Key Findings

We analyzed Yaokami.jp page load time and found that the first response time was 676 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

yaokami.jp performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

65/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

21/100

25%

SI (Speed Index)

Value5.1 s

61/100

10%

TBT (Total Blocking Time)

Value250 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0.079

94/100

15%

TTI (Time to Interactive)

Value6.7 s

56/100

10%

Network Requests Diagram

yaokami.jp

676 ms

default.css

175 ms

top.css

347 ms

jquery.js

536 ms

jquery_default.js

382 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 67% of them (39 requests) were addressed to the original Yaokami.jp, 19% (11 requests) were made to Google.com and 5% (3 requests) were made to Cse.google.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Yaokami.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 167.2 kB (35%)

Content Size

471.9 kB

After Optimization

304.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yaokami.jp main page is 471.9 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. 40% of websites need less resources to load. Javascripts take 198.9 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 26.8 kB

  • Original 36.9 kB
  • After minification 35.5 kB
  • After compression 10.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 26.8 kB or 73% of the original size.

Image Optimization

-4%

Potential reduce by 7.0 kB

  • Original 187.8 kB
  • After minification 180.8 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. Yaokami images are well optimized though.

JavaScript Optimization

-47%

Potential reduce by 94.1 kB

  • Original 198.9 kB
  • After minification 196.6 kB
  • After compression 104.8 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 94.1 kB or 47% of the original size.

CSS Optimization

-81%

Potential reduce by 39.3 kB

  • Original 48.2 kB
  • After minification 37.3 kB
  • After compression 8.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. Yaokami.jp needs all CSS files to be minified and compressed as it can save up to 39.3 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (38%)

Requests Now

53

After Optimization

33

  • Images
  • JavaScript
  • CSS

The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yaokami. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

yaokami.jp

yaokami.jp

676 ms

default.css

default.css

175 ms

top.css

top.css

347 ms

jquery.js

jquery.js

536 ms

jquery_default.js

jquery_default.js

382 ms

jquery_map.js

jquery_map.js

384 ms

cse.js

cse.js

23 ms

top_illust.jpg

top_illust.jpg

517 ms

g2sormvi_t.jpg

g2sormvi_t.jpg

195 ms

default_s.gif

default_s.gif

193 ms

ZpMIfgHk_t.jpg

ZpMIfgHk_t.jpg

195 ms

dIxWmCvr_s.gif

dIxWmCvr_s.gif

179 ms

QxKyvMAI_t.jpg

QxKyvMAI_t.jpg

356 ms

FpSjgQ98_t.jpg

FpSjgQ98_t.jpg

373 ms

0J8XHSBm_t.jpg

0J8XHSBm_t.jpg

394 ms

I1BKGpoZ_t.jpg

I1BKGpoZ_t.jpg

395 ms

UlaGAnCJ_t.jpg

UlaGAnCJ_t.jpg

395 ms

zNm32CVf_t.jpg

zNm32CVf_t.jpg

533 ms

wSdJ1XCR_t.jpg

wSdJ1XCR_t.jpg

559 ms

UrwY8ie5_t.jpg

UrwY8ie5_t.jpg

569 ms

2GC8Zc1O_t.jpg

2GC8Zc1O_t.jpg

576 ms

jNkYEHih_s.gif

jNkYEHih_s.gif

583 ms

Ae0zuwvc_t.jpg

Ae0zuwvc_t.jpg

687 ms

gtm.js

gtm.js

94 ms

bg_bl.gif

bg_bl.gif

869 ms

bg_br.gif

bg_br.gif

730 ms

top_bg.gif

top_bg.gif

744 ms

icon_mb.gif

icon_mb.gif

752 ms

top_logo.gif

top_logo.gif

954 ms

map_japan.gif

map_japan.gif

1187 ms

icon_link_arrow.gif

icon_link_arrow.gif

915 ms

photo_bg_border.gif

photo_bg_border.gif

932 ms

photo_bg.gif

photo_bg.gif

944 ms

icon_hanko.gif

icon_hanko.gif

1046 ms

icon_next_on.gif

icon_next_on.gif

1100 ms

icon_blank.gif

icon_blank.gif

1121 ms

top_mark.gif

top_mark.gif

1135 ms

btn_top.gif

btn_top.gif

1148 ms

btn_sns.gif

btn_sns.gif

1221 ms

bg_footer.gif

bg_footer.gif

1286 ms

cse.js

cse.js

185 ms

topFont.woff

topFont.woff

1614 ms

analytics.js

analytics.js

18 ms

linkid.js

linkid.js

9 ms

collect

collect

9 ms

collect

collect

57 ms

ga-audiences

ga-audiences

51 ms

jsapi

jsapi

63 ms

default+ja.css

default+ja.css

3 ms

default.css

default.css

35 ms

default+ja.I.js

default+ja.I.js

9 ms

default.css

default.css

38 ms

async-ads.js

async-ads.js

60 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

34 ms

small-logo.png

small-logo.png

14 ms

search_box_icon.png

search_box_icon.png

13 ms

clear.gif

clear.gif

15 ms

nav_logo114.png

nav_logo114.png

8 ms

Accessibility Review

yaokami.jp accessibility score

79

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

yaokami.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

yaokami.jp SEO score

90

Search Engine Optimization Advices

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

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

yaokami.jp

Open Graph data is detected on the main page of Yaokami. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: