15.4 sec in total
1.6 sec
13.4 sec
384 ms
Welcome to gracery.com homepage info - get ready to check Gracery best content for Taiwan right away, or after learning these important things about gracery.com
ホテルグレイスリー チェーンの公式サイトです。札幌、銀座、田町のホテルグレイスリーのご案内とネット最安値での宿泊予約ができます。
Visit gracery.comWe analyzed Gracery.com page load time and found that the first response time was 1.6 sec and then it took 13.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
gracery.com performance score
name
value
score
weighting
Value7.9 s
0/100
10%
Value8.6 s
1/100
25%
Value16.3 s
0/100
10%
Value6,610 ms
0/100
30%
Value0.183
66/100
15%
Value19.4 s
2/100
10%
1631 ms
499 ms
509 ms
348 ms
351 ms
Our browser made a total of 129 requests to load all elements on the main page. We found that 77% of them (99 requests) were addressed to the original Gracery.com, 7% (9 requests) were made to Google.com and 5% (7 requests) were made to Fujita-kanko.co.jp. The less responsive or slowest element that took the longest time to load (5.6 sec) belongs to the original domain Gracery.com.
Page size can be reduced by 755.8 kB (21%)
3.5 MB
2.8 MB
In fact, the total size of Gracery.com main page is 3.5 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. 45% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 78.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. This page needs HTML code to be minified as it can gain 16.9 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 78.8 kB or 82% of the original size.
Potential reduce by 64.5 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. Gracery images are well optimized though.
Potential reduce by 454.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 454.8 kB or 66% of the original size.
Potential reduce by 157.7 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. Gracery.com needs all CSS files to be minified and compressed as it can save up to 157.7 kB or 86% of the original size.
Number of requests can be reduced by 58 (47%)
124
66
The browser has sent 124 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 27 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
gracery.com
1631 ms
normalize.css
499 ms
main.css
509 ms
nav.css
348 ms
navres.css
351 ms
whgnav.css
380 ms
base.css
1381 ms
datepicker.css
719 ms
bnrslider.css
946 ms
portal.css
1374 ms
jquery-1.11.1.min.js
1645 ms
bootstrap.min.js
1423 ms
jquery.smooth-scroll.min.js
1078 ms
jquery-ui.min.js
2324 ms
modernizr.custom.79639.js
1576 ms
jp-holidays.js
1892 ms
jquery.fontSizer.min.js
1728 ms
plantabs.js
1785 ms
main.js
2144 ms
jQueryAutoHeight.js
2013 ms
reserve.js
2096 ms
featherlight.min.js
2373 ms
flipsnap.js
2582 ms
jcaption.min.js
2386 ms
smart_form.js
2634 ms
mds_waon_f.png
540 ms
breakfast_thumb.jpg
1109 ms
logo_whg.png
178 ms
logo_whgb.png
355 ms
btn_res.png
372 ms
btn_res_mem.png
573 ms
sitelogo.png
389 ms
mds_waon_f.png
534 ms
gr_shinjyuku5.jpg
1273 ms
bnr_680_3002.jpg
1611 ms
smile_sengen_waku.jpg
1230 ms
02_01A.jpg
1257 ms
pointservice_new_680_300.jpg
1548 ms
kodawari.jpg
1603 ms
top_3.jpg
2440 ms
top_1.jpg
2140 ms
top_6.jpg
2620 ms
top_11.jpg
2580 ms
top_31.jpg
2610 ms
top_2.jpg
2722 ms
whg_logo.png
2643 ms
pointservice_new_480_360_2.jpg
3480 ms
ambassordor.jpg
3637 ms
2015_mi_thumb.jpg
3312 ms
thumb_sapporo.jpg
4064 ms
thumb_ginza.jpg
3918 ms
thumb_tamachi.jpg
3996 ms
thumb_shinjuku.jpg
4467 ms
icon_new.png
3837 ms
thumb_naha.jpg
4798 ms
thumb_kyoto.jpg
4678 ms
concept.jpg
4944 ms
bestrate.jpg
4878 ms
mobile.jpg
4923 ms
pointservice260_70.jpg
5195 ms
service.jpg
5238 ms
QUOplan_thumb.jpg
940 ms
dayuse_thumb.jpg
964 ms
Ladiesplan_thumb.jpg
1159 ms
hotel_lunch_thum.jpg
615 ms
girls_sab.jpg
625 ms
buffet_sab.jpg
1144 ms
gtm.js
70 ms
ambassador_bnr_21.jpg
5505 ms
dc.js
41 ms
conversion_async.js
17 ms
60 ms
70 ms
__utm.gif
15 ms
repeater_bnr_2.jpg
5463 ms
48 ms
36 ms
bnr_godz2.jpg
5229 ms
cse.js
13 ms
cse.js
168 ms
fbds.js
89 ms
s_retargeting.js
589 ms
sp.html
4920 ms
pc.html
5181 ms
144 ms
whglist.html
5559 ms
jsapi
26 ms
default+ja.css
10 ms
minimalist.css
15 ms
default+ja.I.js
13 ms
minimalist.css
70 ms
async-ads.js
56 ms
google_custom_search_watermark.gif
37 ms
small-logo.png
19 ms
grouplist.html
5411 ms
members_bnr_twocards_yellow.jpg
5596 ms
soine.jpg
4850 ms
bnr_breakfast.jpg
4980 ms
bnr_michelin1.jpg
5094 ms
bnr_mail_whgnew_fix.jpg
4912 ms
waon_260x70_140425.jpg
4879 ms
ci26070.jpg
4968 ms
jaldp_bnr260_70_2.gif
4545 ms
limitedplan_bnr_orange.jpg
4557 ms
logo_fujita.png
4159 ms
icon_fb.png
4178 ms
icon_tw.png
4247 ms
icon_gp.png
4299 ms
bg_headerline.png
4299 ms
bg_header.png
3775 ms
icon_res.png
3649 ms
bg_devide_up.png
3593 ms
btn_arrowl.gif
3481 ms
btn_arrowr.gif
3430 ms
bg_grcy.png
3552 ms
icon_res2.png
3390 ms
bg_divide.png
3034 ms
btn_top.png
2887 ms
calender_icon.png
2853 ms
layout_sp.css
2467 ms
module_sp.js
3364 ms
layout.css
2311 ms
module.js
3180 ms
jquery.flickable.js
2612 ms
whg_sp.png
290 ms
whg.png
525 ms
medium.css
364 ms
small.css
642 ms
24 ms
gracery.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
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.
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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
gracery.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gracery.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 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.
gracery.com
Open Graph description is not detected on the main page of 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: