Tools & Wizards About Us
kyoto.gracery.com screenshot

Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

kyoto.gracery.com

Hotel Gracery Kyoto Sanjo in Kyoto – Book a Deluxe hotel Near JR Kyoto Station and Sanjo station

Page Load Speed

8.3 sec in total

First Response

893 ms

Resources Loaded

7 sec

Page Rendered

320 ms

kyoto.gracery.com screenshot

About Website

Welcome to kyoto.gracery.com homepage info - get ready to check Kyoto Gracery best content for Taiwan right away, or after learning these important things about kyoto.gracery.com

Official website of Hotel Gracery Kyoto Sanjo , a Deluxe 4 stars hotel Near JR Kyoto Station and Sanjo station. Book your hotel in Kyoto at the best price

Visit kyoto.gracery.com

Key Findings

We analyzed Kyoto.gracery.com page load time and found that the first response time was 893 ms and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

kyoto.gracery.com performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value23.8 s

0/100

25%

SI (Speed Index)

Value23.7 s

0/100

10%

TBT (Total Blocking Time)

Value10,350 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.359

30/100

15%

TTI (Time to Interactive)

Value35.4 s

0/100

10%

Network Requests Diagram

kyoto.gracery.com

893 ms

gtm.js

75 ms

core.min.css

432 ms

js

100 ms

app.css

445 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 46% of them (26 requests) were addressed to the original Kyoto.gracery.com, 7% (4 requests) were made to Cdnjs.cloudflare.com and 7% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Kyoto.gracery.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 114.0 kB (7%)

Content Size

1.7 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 82.1 kB

  • Original 98.7 kB
  • After minification 90.7 kB
  • After compression 16.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 82.1 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 28.9 kB

  • Original 1.4 MB
  • After minification 1.3 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. Kyoto Gracery images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.5 kB

  • Original 191.4 kB
  • After minification 191.4 kB
  • After compression 189.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-5%

Potential reduce by 1.6 kB

  • Original 34.6 kB
  • After minification 34.5 kB
  • After compression 33.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. Kyoto.gracery.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 30 (64%)

Requests Now

47

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kyoto.gracery.com

kyoto.gracery.com

893 ms

gtm.js

gtm.js

75 ms

core.min.css

core.min.css

432 ms

js

js

100 ms

app.css

app.css

445 ms

custom.css

custom.css

645 ms

app.js

app.js

547 ms

helper.js

helper.js

648 ms

bind.js

bind.js

648 ms

jquery.min.js

jquery.min.js

38 ms

core.min.js

core.min.js

1522 ms

tpl-home.min.js

tpl-home.min.js

659 ms

tpl-home-websdk-offers.min.js

tpl-home-websdk-offers.min.js

661 ms

fb_tracking.js

fb_tracking.js

857 ms

wp-embed.min.js

wp-embed.min.js

867 ms

tripla.min.js

tripla.min.js

595 ms

wejs

wejs

58 ms

webfontloader.js

webfontloader.js

15 ms

logo-whg-white.png

logo-whg-white.png

420 ms

concierge_en1.jpg

concierge_en1.jpg

434 ms

CoE2017_WidgetAsset-14348-2.png

CoE2017_WidgetAsset-14348-2.png

17 ms

css

css

32 ms

instagram-ico.png

instagram-ico.png

437 ms

WidgetEmbed-certificateOfExcellence

WidgetEmbed-certificateOfExcellence

62 ms

css

css

22 ms

t4b_widget_coe-v2381509749a.css

t4b_widget_coe-v2381509749a.css

16 ms

cdswidgets_min-c-v2395114504a.js

cdswidgets_min-c-v2395114504a.js

18 ms

vendor.js

vendor.js

643 ms

tripla.min.js

tripla.min.js

641 ms

_app.js

_app.js

70 ms

en-GB.js

en-GB.js

72 ms

ga4crossdomain.js

ga4crossdomain.js

70 ms

trans.gif

trans.gif

126 ms

offers

offers

1289 ms

admin-ajax.php

admin-ajax.php

1568 ms

load.sumome.com

load.sumome.com

31 ms

290A3400-1920x1080.jpg

290A3400-1920x1080.jpg

1929 ms

290A3011-1920x1080.jpg

290A3011-1920x1080.jpg

2343 ms

290A3196-1920x1080.jpg

290A3196-1920x1080.jpg

1495 ms

sumome.js

sumome.js

2 ms

kyoto.gracery.com

kyoto.gracery.com

235 ms

standarddoubleroom-400x240.jpg

standarddoubleroom-400x240.jpg

433 ms

290A3003-1920x1080.jpg

290A3003-1920x1080.jpg

1729 ms

icon-close-white.png

icon-close-white.png

650 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

33 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

34 ms

tss5ApVBdCYD5Q7hcxTE1ArZ0Zz8oY2KRmwvKhhvy1a6o3mq.woff

tss5ApVBdCYD5Q7hcxTE1ArZ0Zz8oY2KRmwvKhhvy1a6o3mq.woff

48 ms

tss5ApVBdCYD5Q7hcxTE1ArZ0Zz8oY2KRmwvKhhvLFG6o3mq.woff

tss5ApVBdCYD5Q7hcxTE1ArZ0Zz8oY2KRmwvKhhvLFG6o3mq.woff

57 ms

slick.woff

slick.woff

14 ms

admin-ajax.php

admin-ajax.php

1433 ms

Kyoto-Sanjo.svg

Kyoto-Sanjo.svg

27 ms

style.css

style.css

217 ms

icons.min.css

icons.min.css

215 ms

custom.css

custom.css

215 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

12 ms

tpl-home.min.css

tpl-home.min.css

216 ms

Accessibility Review

kyoto.gracery.com accessibility score

56

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-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

Heading elements are not in a sequentially-descending order

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

kyoto.gracery.com 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

Missing source maps for large first-party JavaScript

SEO Factors

kyoto.gracery.com 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

High

Document doesn't have a valid hreflang

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kyoto.gracery.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Kyoto.gracery.com 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

kyoto.gracery.com

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