Report Summary

  • 48

    Performance

    Renders faster than
    67% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 94

    SEO

    Google-friendlier than
    90% of websites

tanzan.or.jp

【公式】談山神社|大和多武峰鎮座

Page Load Speed

6.2 sec in total

First Response

2.4 sec

Resources Loaded

3.7 sec

Page Rendered

177 ms

tanzan.or.jp screenshot

About Website

Click here to check amazing Tanzan content for Japan. Otherwise, check out these important facts you probably never knew about tanzan.or.jp

奈良県桜井市にある談山神社の公式ホームページです。当神社は桜と紅葉の名所です。

Visit tanzan.or.jp

Key Findings

We analyzed Tanzan.or.jp page load time and found that the first response time was 2.4 sec and then it took 3.9 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

tanzan.or.jp performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value12.5 s

0/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value300 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value10.0 s

26/100

10%

Network Requests Diagram

tanzan.or.jp

2356 ms

style.css

492 ms

bg01.jpg

1030 ms

head.jpg

328 ms

Our browser made a total of 4 requests to load all elements on the main page. We found that all of those requests were addressed to Tanzan.or.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Tanzan.or.jp.

Page Optimization Overview & Recommendations

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

Content Size

84.5 kB

After Optimization

77.3 kB

In fact, the total size of Tanzan.or.jp main page is 84.5 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 74.1 kB which makes up the majority of the site volume.

HTML Optimization

-53%

Potential reduce by 1.8 kB

  • Original 3.5 kB
  • After minification 3.4 kB
  • After compression 1.6 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 1.8 kB or 53% of the original size.

Image Optimization

-0%

Potential reduce by 45 B

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

CSS Optimization

-78%

Potential reduce by 5.4 kB

  • Original 6.9 kB
  • After minification 5.5 kB
  • After compression 1.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. Tanzan.or.jp needs all CSS files to be minified and compressed as it can save up to 5.4 kB or 78% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

3

After Optimization

3

The browser has sent 3 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tanzan. According to our analytics all requests are already optimized.

Accessibility Review

tanzan.or.jp accessibility score

89

Accessibility Issues

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

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

Best Practices

tanzan.or.jp best practices score

83

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

High

Browser errors were logged to the console

SEO Factors

tanzan.or.jp SEO score

94

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

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tanzan.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 Tanzan.or.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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