Tools & Wizards About Us
wataya.co.jp screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    50% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 70% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

wataya.co.jp

【公式】和多屋別荘 - 佐賀県 嬉野温泉 川辺に佇む二万坪の温泉宿

Page Load Speed

7 sec in total

First Response

551 ms

Resources Loaded

6.2 sec

Page Rendered

305 ms

wataya.co.jp screenshot

About Website

Visit wataya.co.jp now to see the best up-to-date Wataya content for Japan and also check out these interesting facts you probably never knew about wataya.co.jp

嬉野温泉 和多屋別荘は、ゆっくりと流れる嬉野川沿いの広々とした二万坪の敷地に佇んでおります。眼下に雄大な嬉野川を望む客室や、日本伝統の趣を感じる特別客室。佐賀食材を使った料理の数々。「日本三大美肌の湯」に選ばれた嬉野の湯を、館内全ての湯舟に並々と注いでおります。穏やかな自然に包まれながら、特別なひと時をお過ごしください。

Visit wataya.co.jp

Key Findings

We analyzed Wataya.co.jp page load time and found that the first response time was 551 ms and then it took 6.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

wataya.co.jp performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value1,330 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

wataya.co.jp

551 ms

index.html

1225 ms

default.css

324 ms

top.css

339 ms

smoothscroll.js

386 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 80% of them (57 requests) were addressed to the original Wataya.co.jp, 4% (3 requests) were made to S.ytimg.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Wataya.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 441.7 kB (33%)

Content Size

1.3 MB

After Optimization

877.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 16.1 kB

  • Original 21.2 kB
  • After minification 15.9 kB
  • After compression 5.2 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 5.3 kB, which is 25% 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 16.1 kB or 76% of the original size.

Image Optimization

-8%

Potential reduce by 60.1 kB

  • Original 792.7 kB
  • After minification 732.6 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. Wataya images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 150.9 kB

  • Original 246.2 kB
  • After minification 240.3 kB
  • After compression 95.3 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 150.9 kB or 61% of the original size.

CSS Optimization

-83%

Potential reduce by 214.6 kB

  • Original 259.2 kB
  • After minification 256.4 kB
  • After compression 44.6 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. Wataya.co.jp needs all CSS files to be minified and compressed as it can save up to 214.6 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

67

After Optimization

58

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wataya.co.jp

wataya.co.jp

551 ms

index.html

index.html

1225 ms

default.css

default.css

324 ms

top.css

top.css

339 ms

smoothscroll.js

smoothscroll.js

386 ms

search.js

search.js

414 ms

js_library.js

js_library.js

416 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

547 ms

ga.js

ga.js

51 ms

hd_btm.gif

hd_btm.gif

490 ms

top_bg.gif

top_bg.gif

608 ms

hd_title.gif

hd_title.gif

403 ms

hd_tel.png

hd_tel.png

576 ms

menu.gif

menu.gif

597 ms

sub_menu.gif

sub_menu.gif

421 ms

top_nav1.jpg

top_nav1.jpg

889 ms

top_nav2.jpg

top_nav2.jpg

926 ms

top_nav3.jpg

top_nav3.jpg

1256 ms

main_bg.gif

main_bg.gif

898 ms

side_bg.gif

side_bg.gif

887 ms

top_news_bg.gif

top_news_bg.gif

959 ms

top_news_ttl.png

top_news_ttl.png

1178 ms

icn1.gif

icn1.gif

1251 ms

top01.jpg

top01.jpg

2169 ms

spacer.gif

spacer.gif

1340 ms

top_guide_ttl.jpg

top_guide_ttl.jpg

1486 ms

top_img1.jpg

top_img1.jpg

1881 ms

top_icn1.gif

top_icn1.gif

1577 ms

top_hl1.gif

top_hl1.gif

1633 ms

top_img2.jpg

top_img2.jpg

1918 ms

top_hl2.gif

top_hl2.gif

1807 ms

top_img3.jpg

top_img3.jpg

2212 ms

top_hl3.gif

top_hl3.gif

1991 ms

top_img4.jpg

top_img4.jpg

2383 ms

top_hl4.gif

top_hl4.gif

2233 ms

top_img6.jpg

top_img6.jpg

2353 ms

top_hl5.gif

top_hl5.gif

2325 ms

bunner_webshop.jpg

bunner_webshop.jpg

2961 ms

side_rsv_ttl.jpg

side_rsv_ttl.jpg

2547 ms

side_rsv_text1.gif

side_rsv_text1.gif

2568 ms

side_rsv_btn1.gif

side_rsv_btn1.gif

2708 ms

bnr_wifi.png

bnr_wifi.png

2854 ms

imagebook01.jpg

imagebook01.jpg

3086 ms

imagebookspa01.jpg

imagebookspa01.jpg

3126 ms

panf.gif

panf.gif

2953 ms

qQi7Tzu_n3M

qQi7Tzu_n3M

101 ms

__utm.gif

__utm.gif

28 ms

2SbXxgGiOsI

2SbXxgGiOsI

83 ms

like.php

like.php

160 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

72 ms

www-embed-player.js

www-embed-player.js

95 ms

base.js

base.js

169 ms

TY3MhkXpWJ-.js

TY3MhkXpWJ-.js

120 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

22 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

40 ms

ad_status.js

ad_status.js

26 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

85 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

86 ms

side_rsv_text2-2.gif

side_rsv_text2-2.gif

2662 ms

side_rsv_menu2.gif

side_rsv_menu2.gif

2822 ms

side_rsv_menu3.gif

side_rsv_menu3.gif

2861 ms

side_rsv_menu4.gif

side_rsv_menu4.gif

2796 ms

side_rsv_menu5.gif

side_rsv_menu5.gif

2805 ms

side_rsv_menu6.gif

side_rsv_menu6.gif

2846 ms

side_banner2.jpg

side_banner2.jpg

2826 ms

facebook.gif

facebook.gif

2771 ms

side_ft_link.gif

side_ft_link.gif

2850 ms

ft_line.gif

ft_line.gif

2829 ms

ft_title.gif

ft_title.gif

2828 ms

ft_tel.gif

ft_tel.gif

2626 ms

icn2.gif

icn2.gif

2792 ms

Accessibility Review

wataya.co.jp accessibility score

88

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

wataya.co.jp best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

wataya.co.jp SEO score

76

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

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 Wataya.co.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 Wataya.co.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

wataya.co.jp

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