Tools & Wizards About Us
nanzen.net screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

nanzen.net

臨済宗大本山 南禅寺 公式サイト :: 南禅寺

Page Load Speed

5.7 sec in total

First Response

571 ms

Resources Loaded

4.5 sec

Page Rendered

630 ms

nanzen.net screenshot

About Website

Visit nanzen.net now to see the best up-to-date Nanzen content for Japan and also check out these interesting facts you probably never knew about nanzen.net

臨済宗大本山 南禅寺 公式サイト

Visit nanzen.net

Key Findings

We analyzed Nanzen.net page load time and found that the first response time was 571 ms and then it took 5.1 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

nanzen.net performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.1 s

1/100

10%

LCP (Largest Contentful Paint)

Value18.7 s

0/100

25%

SI (Speed Index)

Value9.5 s

11/100

10%

TBT (Total Blocking Time)

Value200 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

nanzen.net

571 ms

nanzenji.or.jp

1477 ms

js

72 ms

css

45 ms

css

64 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Nanzen.net, 66% (41 requests) were made to Nanzenji.or.jp and 10% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Nanzenji.or.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 242.1 kB (11%)

Content Size

2.1 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nanzen.net main page is 2.1 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 35.4 kB

  • Original 41.1 kB
  • After minification 29.9 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 11.2 kB, which is 27% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 35.4 kB or 86% of the original size.

Image Optimization

-4%

Potential reduce by 70.5 kB

  • Original 1.8 MB
  • After minification 1.7 MB

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. Nanzen images are well optimized though.

JavaScript Optimization

-34%

Potential reduce by 76.3 kB

  • Original 224.5 kB
  • After minification 217.9 kB
  • After compression 148.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 76.3 kB or 34% of the original size.

CSS Optimization

-83%

Potential reduce by 59.8 kB

  • Original 72.3 kB
  • After minification 50.3 kB
  • After compression 12.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. Nanzen.net needs all CSS files to be minified and compressed as it can save up to 59.8 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

54

After Optimization

31

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nanzen.net

nanzen.net

571 ms

nanzenji.or.jp

nanzenji.or.jp

1477 ms

js

js

72 ms

css

css

45 ms

css

css

64 ms

css

css

124 ms

jquery-ui.css

jquery-ui.css

34 ms

perfect-scrollbar.min.css

perfect-scrollbar.min.css

50 ms

style.css

style.css

351 ms

media.css

media.css

686 ms

jquery.min.js

jquery.min.js

36 ms

jquery-ui.min.js

jquery-ui.min.js

42 ms

modernizr.min.js

modernizr.min.js

58 ms

perfect-scrollbar.min.js

perfect-scrollbar.min.js

67 ms

script.js

script.js

515 ms

style.css

style.css

518 ms

media.css

media.css

519 ms

jquery.js

jquery.js

758 ms

view.css

view.css

532 ms

responsive-slides.css

responsive-slides.css

756 ms

view.css

view.css

757 ms

slick.min.css

slick.min.css

68 ms

iframe_api

iframe_api

54 ms

slick.min.js

slick.min.js

85 ms

view.js

view.js

587 ms

responsive-slides.js

responsive-slides.js

606 ms

logo-01.png

logo-01.png

237 ms

logo-02.png

logo-02.png

178 ms

nanzenshot-01.png

nanzenshot-01.png

178 ms

icon-insta-01.png

icon-insta-01.png

179 ms

slide4.jpg

slide4.jpg

1100 ms

slide7.jpg

slide7.jpg

856 ms

slide8.jpg

slide8.jpg

1027 ms

slide6.jpg

slide6.jpg

1367 ms

banner_top1.jpg

banner_top1.jpg

516 ms

banner_top2.jpg

banner_top2.jpg

416 ms

banner_top3.jpg

banner_top3.jpg

592 ms

banner_top4.jpg

banner_top4.jpg

688 ms

banner-nanzen_kaikan.jpg

banner-nanzen_kaikan.jpg

770 ms

banner-nanzenjiha.jpg

banner-nanzenjiha.jpg

860 ms

banner-rinnou.jpg

banner-rinnou.jpg

946 ms

nanzenshot-01@white.png

nanzenshot-01@white.png

1027 ms

insta-01.jpg

insta-01.jpg

1032 ms

insta-02.jpg

insta-02.jpg

1124 ms

insta-03.jpg

insta-03.jpg

1198 ms

insta-04.jpg

insta-04.jpg

1198 ms

insta-05.jpg

insta-05.jpg

1203 ms

insta-06.jpg

insta-06.jpg

1274 ms

insta-07.jpg

insta-07.jpg

1300 ms

insta-08.jpg

insta-08.jpg

1369 ms

logo-01@white.png

logo-01@white.png

1370 ms

logo-02@white.png

logo-02@white.png

1373 ms

www-widgetapi.js

www-widgetapi.js

5 ms

bg-01.png

bg-01.png

1559 ms

img-04.jpg

img-04.jpg

1760 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj35TS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj35TS1g.ttf

102 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk35TS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk35TS1g.ttf

245 ms

DdT878IGsGw1aF1JU10PUbTvNNaDMfq41-c.ttf

DdT878IGsGw1aF1JU10PUbTvNNaDMfq41-c.ttf

169 ms

DdT578IGsGw1aF1JU10PUbTvNNaDMfID8vdkPxs.ttf

DdT578IGsGw1aF1JU10PUbTvNNaDMfID8vdkPxs.ttf

176 ms

xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bwDOtbPKrc.ttf

xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bwDOtbPKrc.ttf

286 ms

xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bzWPdbPKrc.ttf

xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bzWPdbPKrc.ttf

275 ms

arrows.gif

arrows.gif

1374 ms

Accessibility Review

nanzen.net accessibility score

89

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

Links do not have a discernible name

Best Practices

nanzen.net 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

High

Page has valid source maps

SEO Factors

nanzen.net SEO score

85

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

Document doesn't have a valid hreflang

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 Nanzen.net 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 Nanzen.net 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

nanzen.net

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