Tools & Wizards About Us
yaokami.jp screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

yaokami.jp

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

Page Load Speed

4.6 sec in total

First Response

513 ms

Resources Loaded

3.8 sec

Page Rendered

280 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 513 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

yaokami.jp performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

65/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value5.2 s

60/100

10%

TBT (Total Blocking Time)

Value430 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.079

94/100

15%

TTI (Time to Interactive)

Value7.8 s

44/100

10%

Network Requests Diagram

yaokami.jp

513 ms

yaokami.jp

765 ms

common_pc.css

168 ms

top_pc.css

335 ms

gcs.js

489 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 91% of them (62 requests) were addressed to the original Yaokami.jp, 4% (3 requests) were made to Google.com and 3% (2 requests) were made to Cse.google.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Yaokami.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 34.1 kB (3%)

Content Size

1.0 MB

After Optimization

997.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 28.0 kB

  • Original 37.3 kB
  • After minification 37.2 kB
  • After compression 9.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. 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 28.0 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 1.8 kB

  • Original 816.7 kB
  • After minification 814.9 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

-1%

Potential reduce by 981 B

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

CSS Optimization

-14%

Potential reduce by 3.4 kB

  • Original 24.1 kB
  • After minification 24.1 kB
  • After compression 20.7 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 3.4 kB or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (26%)

Requests Now

65

After Optimization

48

  • Images
  • JavaScript
  • CSS

The browser has sent 65 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 7 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

513 ms

yaokami.jp

yaokami.jp

765 ms

common_pc.css

common_pc.css

168 ms

top_pc.css

top_pc.css

335 ms

gcs.js

gcs.js

489 ms

vendor.js

vendor.js

652 ms

common.js

common.js

652 ms

gtm.js

gtm.js

138 ms

bg_border.png

bg_border.png

246 ms

bg_page_top.png

bg_page_top.png

351 ms

common_header.png

common_header.png

782 ms

top_logo.png

top_logo.png

414 ms

illust_top.png

illust_top.png

944 ms

top_map_00.png

top_map_00.png

458 ms

top_map_01.png

top_map_01.png

519 ms

icon_arrow.png

icon_arrow.png

580 ms

top_map_02.png

top_map_02.png

772 ms

top_map_03.png

top_map_03.png

620 ms

top_map_04.png

top_map_04.png

685 ms

top_map_05.png

top_map_05.png

747 ms

top_map_06.png

top_map_06.png

782 ms

top_map_07.png

top_map_07.png

853 ms

top_map_08.png

top_map_08.png

914 ms

icon_arrow_on.png

icon_arrow_on.png

945 ms

bg_border_photo.png

bg_border_photo.png

944 ms

bg_photo.png

bg_photo.png

945 ms

icon_hanko.png

icon_hanko.png

1021 ms

bOtUH3sv_t.jpg

bOtUH3sv_t.jpg

1082 ms

icon_type1.png

icon_type1.png

1105 ms

XeLM6cSE_s.gif

XeLM6cSE_s.gif

1106 ms

06uzxd4o_t.jpg

06uzxd4o_t.jpg

1107 ms

18hIdx2C_t.jpg

18hIdx2C_t.jpg

1117 ms

vtkpehKw_s.gif

vtkpehKw_s.gif

1188 ms

yCpRS4F8_t.jpg

yCpRS4F8_t.jpg

1248 ms

yKwrLs3e_t.jpg

yKwrLs3e_t.jpg

1270 ms

zxcvu9Ul_t.jpg

zxcvu9Ul_t.jpg

1268 ms

q9GK4bx5_t.jpg

q9GK4bx5_t.jpg

1270 ms

uyiKBRYG_s.gif

uyiKBRYG_s.gif

1292 ms

FiGlfxHp_t.jpg

FiGlfxHp_t.jpg

1355 ms

aQLlZOfH_t.jpg

aQLlZOfH_t.jpg

1414 ms

icon_type2.png

icon_type2.png

1357 ms

cse.js

cse.js

41 ms

yaokamiTopFont.woff

yaokamiTopFont.woff

1304 ms

cse_element__ja.js

cse_element__ja.js

24 ms

default+ja.css

default+ja.css

45 ms

default.css

default.css

48 ms

BF5wEPql_s.gif

BF5wEPql_s.gif

1190 ms

C7aco3IG_t.jpg

C7aco3IG_t.jpg

1174 ms

async-ads.js

async-ads.js

14 ms

default_s.gif

default_s.gif

1205 ms

fHBMS2oV_t.jpg

fHBMS2oV_t.jpg

1234 ms

9ZIhptWO_t.jpg

9ZIhptWO_t.jpg

1182 ms

icon_blank.png

icon_blank.png

1139 ms

yVsdMrnW_s.gif

yVsdMrnW_s.gif

1079 ms

1Y2zMRl9_s.gif

1Y2zMRl9_s.gif

1062 ms

Pzg6H4Ci_s.gif

Pzg6H4Ci_s.gif

1071 ms

CKJbpTBR_s.gif

CKJbpTBR_s.gif

1066 ms

cJaDUdwE_s.gif

cJaDUdwE_s.gif

1011 ms

nyANdDkO_s.gif

nyANdDkO_s.gif

990 ms

top_mark.png

top_mark.png

979 ms

illust_footer_left.png

illust_footer_left.png

1204 ms

illust_footer_right.png

illust_footer_right.png

1341 ms

icon_arrow_top.png

icon_arrow_top.png

1004 ms

icon_sns_mail.svg

icon_sns_mail.svg

976 ms

icon_sns_line.svg

icon_sns_line.svg

977 ms

icon_sns_facebook.svg

icon_sns_facebook.svg

976 ms

icon_sns_x.svg

icon_sns_x.svg

1139 ms

common_logo_footer.png

common_logo_footer.png

1062 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

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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: