24.1 sec in total
933 ms
21.3 sec
1.9 sec
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.comWe analyzed Kyoto.gracery.com page load time and found that the first response time was 933 ms and then it took 23.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
kyoto.gracery.com performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value21.7 s
0/100
25%
Value29.6 s
0/100
10%
Value31,680 ms
0/100
30%
Value0.434
21/100
15%
Value43.3 s
0/100
10%
933 ms
81 ms
437 ms
123 ms
363 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 26% of them (28 requests) were addressed to the original Kyoto.gracery.com, 13% (14 requests) were made to Maps.google.com and 11% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (19.5 sec) relates to the external source Tripadvisor.com.
Page size can be reduced by 823.3 kB (26%)
3.2 MB
2.4 MB
In fact, the total size of Kyoto.gracery.com main page is 3.2 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 775.8 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 775.8 kB or 91% of the original size.
Potential reduce by 33.0 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. Kyoto Gracery images are well optimized though.
Potential reduce by 12.8 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.
Potential reduce by 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. Kyoto.gracery.com has all CSS files already compressed.
Number of requests can be reduced by 55 (60%)
91
36
The browser has sent 91 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 44 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
kyoto.gracery.com
933 ms
gtm.js
81 ms
core.min.css
437 ms
js
123 ms
app.css
363 ms
custom.css
630 ms
app.js
572 ms
helper.js
719 ms
bind.js
717 ms
run.js
716 ms
jquery.min.js
87 ms
core.min.js
1505 ms
tpl-home.min.js
718 ms
tpl-home-websdk-offers.min.js
829 ms
fb_tracking.js
917 ms
wp-embed.min.js
930 ms
tripla.min.js
638 ms
wejs
19514 ms
gen_204
67 ms
webfontloader.js
38 ms
logo-whg-white.png
441 ms
fgmc_bnr_En.png
654 ms
concierge_en1.jpg
565 ms
480-x-140_en.png
1073 ms
css
52 ms
CoE2017_WidgetAsset-14348-2.png
72 ms
instagram-ico.png
639 ms
css
43 ms
vendor.js
639 ms
tripla.min.js
1343 ms
_app.js
75 ms
en-GB.js
98 ms
allavailabilities
686 ms
style.css
213 ms
icons.min.css
373 ms
trans.gif
303 ms
offers
1940 ms
admin-ajax.php
1320 ms
load.sumome.com
386 ms
1-1920x940.jpg
1918 ms
2-1920x940.jpg
2540 ms
3-1920x940.jpg
2511 ms
exterior-hotel-gracery-kyotosanjo-kyoto-21.jpg
906 ms
double-room-kyotosanjo-gracery-hotel-kyoto-1.jpg
900 ms
icon-close-white.png
222 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
224 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
326 ms
tss5ApVBdCYD5Q7hcxTE1ArZ0Zz8oY2KRmwvKhhvy1a6o3mp.ttf
364 ms
tss5ApVBdCYD5Q7hcxTE1ArZ0Zz8oY2KRmwvKhhvLFG6o3mp.ttf
365 ms
fontawesome-webfont.woff
68 ms
slick.woff
131 ms
72.0a035390359aab65eb82.js
214 ms
73.0a035390359aab65eb82.js
222 ms
admin-ajax.php
1429 ms
Kyoto-Sanjo.svg
38 ms
common.js
45 ms
util.js
45 ms
map.js
86 ms
marker.js
73 ms
StaticMapService.GetMapImage
388 ms
openhand_8_8.cur
60 ms
onion.js
29 ms
ViewportInfoService.GetViewportInfo
128 ms
icon-map-marker-washington.png
212 ms
AuthenticationService.Authenticate
74 ms
vt
122 ms
vt
123 ms
vt
120 ms
vt
136 ms
vt
33 ms
vt
34 ms
vt
58 ms
QuotaService.RecordEvent
72 ms
transparent.png
28 ms
controls.js
21 ms
css
50 ms
css
49 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
13 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
12 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
12 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
47 ms
ribbon.css
215 ms
custom.css
213 ms
tpl-home.min.css
214 ms
410 ms
services
177 ms
4.0a035390359aab65eb82.js
5 ms
64.0a035390359aab65eb82.js
4 ms
0.0a035390359aab65eb82.js
5 ms
1.0a035390359aab65eb82.js
5 ms
2.0a035390359aab65eb82.js
18 ms
3.0a035390359aab65eb82.js
35 ms
11.0a035390359aab65eb82.js
36 ms
15.0a035390359aab65eb82.js
44 ms
css
160 ms
sumome-white-60.png
141 ms
shares.json
355 ms
graph.facebook.com
346 ms
links.getStats
345 ms
rpc
358 ms
count.json
330 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
110 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf
26 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
110 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
113 ms
jsonpcallback
215 ms
button_info.json
95 ms
jsonpcallback
355 ms
jsonpcallback
244 ms
kyoto.gracery.com accessibility score
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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
[aria-*] attributes do not have valid values
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
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
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
kyoto.gracery.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
kyoto.gracery.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Image elements do not have [alt] attributes
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
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.
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: