Report Summary

  • 96

    Performance

    Renders faster than
    94% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

terracehouse.jp

Terrace House yamabare | 石垣島の貸別荘

Page Load Speed

2.2 sec in total

First Response

523 ms

Resources Loaded

1.6 sec

Page Rendered

119 ms

About Website

Welcome to terracehouse.jp homepage info - get ready to check Terrace House best content right away, or after learning these important things about terracehouse.jp

石垣島の北西部、川平山原(ヤマバレー)に建つ、東シナ海が一望できる一組限定の一戸建て貸し別荘。ミシュランガイドで三ツ星に選ばれた川平湾から、石垣島最北端、平久保崎まで見渡せます。目の前に広がる海・・・亜熱帯の珊瑚の島で、あなただけの贅沢空間を提供します。

Visit terracehouse.jp

Key Findings

We analyzed Terracehouse.jp page load time and found that the first response time was 523 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

terracehouse.jp performance score

96

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.9 s

100/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

86/100

25%

SI (Speed Index)

Value2.2 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.9 s

100/100

10%

Network Requests Diagram

terracehouse.jp

523 ms

rollover.js

162 ms

def.css

323 ms

nav_main01_rollout.jpg

197 ms

nav_main02_rollout.jpg

316 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 13.7 kB (16%)

Content Size

83.8 kB

After Optimization

70.1 kB

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

HTML Optimization

-63%

Potential reduce by 2.4 kB

  • Original 3.9 kB
  • After minification 3.6 kB
  • After compression 1.5 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 2.4 kB or 63% of the original size.

Image Optimization

-0%

Potential reduce by 243 B

  • Original 66.6 kB
  • After minification 66.3 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. Terrace House images are well optimized though.

JavaScript Optimization

-80%

Potential reduce by 2.8 kB

  • Original 3.5 kB
  • After minification 2.0 kB
  • After compression 718 B

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 2.8 kB or 80% of the original size.

CSS Optimization

-83%

Potential reduce by 8.2 kB

  • Original 9.8 kB
  • After minification 7.2 kB
  • After compression 1.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. Terracehouse.jp needs all CSS files to be minified and compressed as it can save up to 8.2 kB or 83% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

17

After Optimization

17

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

Accessibility Review

terracehouse.jp accessibility score

70

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

terracehouse.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

terracehouse.jp SEO score

67

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

Image elements do not have [alt] attributes

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 Terracehouse.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 Terracehouse.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 Terrace House. 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: