Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

resorttrust.co.jp

リゾートトラスト株式会社|resorttrust【公式】

Page Load Speed

11.6 sec in total

First Response

405 ms

Resources Loaded

10.5 sec

Page Rendered

620 ms

About Website

Welcome to resorttrust.co.jp homepage info - get ready to check Resorttrust best content for Japan right away, or after learning these important things about resorttrust.co.jp

リゾートトラスト株式会社の公式サイトです。会社概要をはじめ、会員権の販売情報、資料請求、ホテル情報や予約サービス、メディカル・シニア施設、ゴルフ場などをご案内します。リゾートトラストグループは、最上のホスピタリティで、「夢と感動、美とやすらぎ」を提供します。

Visit resorttrust.co.jp

Key Findings

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

Performance Metrics

resorttrust.co.jp performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

6/100

10%

LCP (Largest Contentful Paint)

Value15.0 s

0/100

25%

SI (Speed Index)

Value20.9 s

0/100

10%

TBT (Total Blocking Time)

Value2,980 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.176

68/100

15%

TTI (Time to Interactive)

Value20.7 s

2/100

10%

Network Requests Diagram

resorttrust.co.jp

405 ms

resorttrust.co.jp

796 ms

www.resorttrust.co.jp

391 ms

www.resorttrust.co.jp

1628 ms

slick.css

549 ms

Our browser made a total of 198 requests to load all elements on the main page. We found that 70% of them (139 requests) were addressed to the original Resorttrust.co.jp, 3% (5 requests) were made to Googletagmanager.com and 3% (5 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Resorttrust.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 939.7 kB (8%)

Content Size

11.7 MB

After Optimization

10.7 MB

In fact, the total size of Resorttrust.co.jp main page is 11.7 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. Only a small number of websites need less resources to load. Images take 10.1 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 226.6 kB

  • Original 269.6 kB
  • After minification 244.5 kB
  • After compression 43.0 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 226.6 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 16.8 kB

  • Original 10.1 MB
  • After minification 10.0 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. Resorttrust images are well optimized though.

JavaScript Optimization

-50%

Potential reduce by 622.0 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 611.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 622.0 kB or 50% of the original size.

CSS Optimization

-86%

Potential reduce by 74.3 kB

  • Original 86.9 kB
  • After minification 70.3 kB
  • After compression 12.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. Resorttrust.co.jp needs all CSS files to be minified and compressed as it can save up to 74.3 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 53 (29%)

Requests Now

184

After Optimization

131

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

Accessibility Review

resorttrust.co.jp accessibility score

74

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

ARIA toggle fields do not have accessible names

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

SEO Factors

resorttrust.co.jp SEO score

92

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

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

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