Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

crownpalais.jp

クラウンパレス|HMIホテルグループ

Page Load Speed

1.3 sec in total

First Response

594 ms

Resources Loaded

602 ms

Page Rendered

95 ms

crownpalais.jp screenshot

About Website

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

ハイレベルの個性を誇る「ホテルクラウンパレス」はフルサービスの上級ブランドであり、宿泊施設としての利用のみならず、地域の人々にも洗練された様々なサービスを提供しています。

Visit crownpalais.jp

Key Findings

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

Performance Metrics

crownpalais.jp performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

24/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.746

6/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

Network Requests Diagram

crownpalais.jp

594 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 267 B (38%)

Content Size

708 B

After Optimization

441 B

In fact, the total size of Crownpalais.jp main page is 708 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 708 B which makes up the majority of the site volume.

HTML Optimization

-38%

Potential reduce by 267 B

  • Original 708 B
  • After minification 700 B
  • After compression 441 B

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 267 B or 38% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

crownpalais.jp accessibility score

75

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

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

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

crownpalais.jp SEO score

81

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