Tools & Wizards About Us
oomiwa.or.jp screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

oomiwa.or.jp

【公式】三輪明神 大神神社 (おおみわじんじゃ)

Page Load Speed

6.3 sec in total

First Response

1.3 sec

Resources Loaded

4.6 sec

Page Rendered

412 ms

oomiwa.or.jp screenshot

About Website

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

奈良県桜井市、大神神社の公式ホームページです。大和国一之宮 三輪明神 大神神社（おおみわじんじゃ）は、本殿は設けずに三ツ鳥居を通し三輪山を拝するという原初の神祀りの様を伝える我が国最古の神社のひとつです。

Visit oomiwa.or.jp

Key Findings

We analyzed Oomiwa.or.jp page load time and found that the first response time was 1.3 sec and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

oomiwa.or.jp performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value26.7 s

0/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value450 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0.282

43/100

15%

TTI (Time to Interactive)

Value13.8 s

10/100

10%

Network Requests Diagram

oomiwa.or.jp

1338 ms

base.css

511 ms

index.css

707 ms

header_footer.css

544 ms

jquery.js

1083 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 85% of them (69 requests) were addressed to the original Oomiwa.or.jp, 9% (7 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Oomiwa.or.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 237.3 kB (17%)

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oomiwa.or.jp main page is 1.4 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. Only a small number of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 23.0 kB

  • Original 29.7 kB
  • After minification 27.8 kB
  • After compression 6.7 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 23.0 kB or 77% of the original size.

Image Optimization

-2%

Potential reduce by 15.5 kB

  • Original 1.0 MB
  • After minification 997.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. Oomiwa images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 168.7 kB

  • Original 305.8 kB
  • After minification 301.9 kB
  • After compression 137.2 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 168.7 kB or 55% of the original size.

CSS Optimization

-79%

Potential reduce by 30.1 kB

  • Original 38.2 kB
  • After minification 28.2 kB
  • After compression 8.1 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. Oomiwa.or.jp needs all CSS files to be minified and compressed as it can save up to 30.1 kB or 79% of the original size.

Requests Breakdown

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

Requests Now

73

After Optimization

56

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

oomiwa.or.jp

oomiwa.or.jp

1338 ms

base.css

base.css

511 ms

index.css

index.css

707 ms

header_footer.css

header_footer.css

544 ms

jquery.js

jquery.js

1083 ms

rollover.js

rollover.js

372 ms

jquery.min.js

jquery.min.js

79 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

504 ms

se-styles.css

se-styles.css

557 ms

styles.css

styles.css

674 ms

thickbox.min.css

thickbox.min.css

676 ms

jquery.js

jquery.js

1265 ms

jquery-migrate.min.js

jquery-migrate.min.js

927 ms

stt.js

stt.js

844 ms

debounce.js

debounce.js

845 ms

strx-magic-floating-sidebar-maker.js

strx-magic-floating-sidebar-maker.js

878 ms

thickbox.min.js

thickbox.min.js

857 ms

sasa2.gif

sasa2.gif

232 ms

analytics.js

analytics.js

57 ms

notosansjapanese.css

notosansjapanese.css

56 ms

loadingAnimation.gif

loadingAnimation.gif

717 ms

sitemap_link_off.png

sitemap_link_off.png

212 ms

logo2.gif

logo2.gif

402 ms

logo2_2.gif

logo2_2.gif

214 ms

navi1_off.png

navi1_off.png

399 ms

navi2_off.png

navi2_off.png

215 ms

navi3_off.png

navi3_off.png

397 ms

navi4_off.png

navi4_off.png

398 ms

menu5_off.png

menu5_off.png

400 ms

menu1_off.png

menu1_off.png

398 ms

cover1.png

cover1.png

509 ms

page1.jpg

page1.jpg

852 ms

sub1_1_off.gif

sub1_1_off.gif

530 ms

sub1_2_off.gif

sub1_2_off.gif

546 ms

sub1_3_off.gif

sub1_3_off.gif

548 ms

sub1_4_off.gif

sub1_4_off.gif

557 ms

sub1_5_off.gif

sub1_5_off.gif

678 ms

page2.jpg

page2.jpg

1058 ms

sub2_1_off.gif

sub2_1_off.gif

726 ms

sub2_2_off.gif

sub2_2_off.gif

729 ms

page3.jpg

page3.jpg

1113 ms

sub3_1_off.gif

sub3_1_off.gif

848 ms

sub3_3_off.gif

sub3_3_off.gif

907 ms

sub3_2_off.gif

sub3_2_off.gif

910 ms

sub3_4_off.gif

sub3_4_off.gif

1017 ms

page4.jpg

page4.jpg

1020 ms

sub4_1_off.gif

sub4_1_off.gif

1088 ms

sub4_2_off.gif

sub4_2_off.gif

1091 ms

sub4_3_off.gif

sub4_3_off.gif

1185 ms

page5.jpg

page5.jpg

1193 ms

sub5_1_off.gif

sub5_1_off.gif

1233 ms

sub5_2_off.gif

sub5_2_off.gif

1267 ms

sub5_3_off.gif

sub5_3_off.gif

1272 ms

page6.jpg

page6.jpg

1484 ms

sub6_1_off.gif

sub6_1_off.gif

1354 ms

menu2_off.png

menu2_off.png

1362 ms

menu3_off.png

menu3_off.png

1406 ms

collect

collect

12 ms

NotoSansJP-Regular.woff

NotoSansJP-Regular.woff

123 ms

NotoSansJP-Medium.woff

NotoSansJP-Medium.woff

170 ms

NotoSansJP-DemiLight.woff

NotoSansJP-DemiLight.woff

262 ms

NotoSansJP-Light.woff

NotoSansJP-Light.woff

264 ms

NotoSansJP-Thin.woff

NotoSansJP-Thin.woff

237 ms

NotoSansJP-Bold.woff

NotoSansJP-Bold.woff

262 ms

NotoSansJP-Black.woff

NotoSansJP-Black.woff

262 ms

navi5_off.png

navi5_off.png

1242 ms

menu4_off.png

menu4_off.png

1246 ms

navi6_off.png

navi6_off.png

1314 ms

menu6_off.png

menu6_off.png

1144 ms

subline.gif

subline.gif

1196 ms

btn_list_off.jpg

btn_list_off.jpg

1239 ms

foot_btn1_off.png

foot_btn1_off.png

1244 ms

foot_btn2_off.png

foot_btn2_off.png

1279 ms

foot_btn3_off.png

foot_btn3_off.png

1300 ms

foot_btn4_off.png

foot_btn4_off.png

1202 ms

logobg2.gif

logobg2.gif

1239 ms

top_bg.gif

top_bg.gif

1269 ms

touka_bg.gif

touka_bg.gif

1275 ms

bg_bottom.jpg

bg_bottom.jpg

1306 ms

print_index.css

print_index.css

172 ms

bg_direction_nav.png

bg_direction_nav.png

172 ms

Accessibility Review

oomiwa.or.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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Definition list items are not wrapped in <dl> elements

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

Form elements do not have associated labels

Best Practices

oomiwa.or.jp best practices score

83

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

SEO Factors

oomiwa.or.jp SEO score

86

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

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

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 Oomiwa.or.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 Oomiwa.or.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

oomiwa.or.jp

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