Report Summary

  • 33

    Performance

    Renders faster than
    52% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

waterchapel.jp

水の教会 CHAPEL ON THE WATER | TOMAMU the Wedding

Page Load Speed

7.2 sec in total

First Response

583 ms

Resources Loaded

5.1 sec

Page Rendered

1.5 sec

waterchapel.jp screenshot

About Website

Click here to check amazing WATER CHAPEL content for Japan. Otherwise, check out these important facts you probably never knew about waterchapel.jp

星野リゾートトマムのリゾート滞在型の北海道家族旅ウエディング。建築家 安藤忠雄設計の自然と対話し創造した聖なる空間「水の教会」。白樺の森に囲まれ「L」字の壁で仕切られた敷地は、独特な雰囲気に包まれた非日常空間。聖なる空間に佇む十字架を前にここに集う人々の心は一つになり、厳粛な挙式が始まる。

Visit waterchapel.jp

Key Findings

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

Performance Metrics

waterchapel.jp performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value12.5 s

0/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value510 ms

57/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.5 s

3/100

10%

Network Requests Diagram

waterchapel.jp

583 ms

1319 ms

css

32 ms

style.css

666 ms

vegas.min.css

557 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Waterchapel.jp, 91% (51 requests) were made to Tomamu-wedding.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Tomamu-wedding.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 462.2 kB (6%)

Content Size

7.2 MB

After Optimization

6.7 MB

In fact, the total size of Waterchapel.jp main page is 7.2 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. 35% of websites need less resources to load. Images take 6.6 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 45.1 kB

  • Original 59.0 kB
  • After minification 55.2 kB
  • After compression 13.9 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 45.1 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 10.6 kB

  • Original 6.6 MB
  • After minification 6.6 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. WATER CHAPEL images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 105.0 kB

  • Original 151.8 kB
  • After minification 140.5 kB
  • After compression 46.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 105.0 kB or 69% of the original size.

CSS Optimization

-85%

Potential reduce by 301.5 kB

  • Original 353.5 kB
  • After minification 319.1 kB
  • After compression 52.0 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. Waterchapel.jp needs all CSS files to be minified and compressed as it can save up to 301.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (24%)

Requests Now

54

After Optimization

41

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

Accessibility Review

waterchapel.jp accessibility score

83

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.

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

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

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

waterchapel.jp SEO score

93

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Waterchapel.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Waterchapel.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

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