8.5 sec in total
1.4 sec
6.8 sec
305 ms
Click here to check amazing Shinjuku Gracery content for Taiwan. Otherwise, check out these important facts you probably never knew about shinjuku.gracery.com
Official website of Gracery Shinjuku , a Leisure 4 stars hotel City Center. Book your hotel in Tokyo at the best price
Visit shinjuku.gracery.comWe analyzed Shinjuku.gracery.com page load time and found that the first response time was 1.4 sec and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
shinjuku.gracery.com performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value19.2 s
0/100
25%
Value12.3 s
3/100
10%
Value1,160 ms
22/100
30%
Value0.33
34/100
15%
Value23.9 s
1/100
10%
1375 ms
558 ms
476 ms
478 ms
11 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 44% of them (50 requests) were addressed to the original Shinjuku.gracery.com, 20% (23 requests) were made to Maps.google.com and 8% (9 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Shinjuku.gracery.com.
Page size can be reduced by 1.3 MB (36%)
3.6 MB
2.3 MB
In fact, the total size of Shinjuku.gracery.com main page is 3.6 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. 65% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 105.2 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 20.8 kB, which is 17% 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 105.2 kB or 86% of the original size.
Potential reduce by 270.4 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. Obviously, Shinjuku Gracery needs image optimization as it can save up to 270.4 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 648.4 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 648.4 kB or 66% of the original size.
Potential reduce by 295.4 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. Shinjuku.gracery.com needs all CSS files to be minified and compressed as it can save up to 295.4 kB or 83% of the original size.
Number of requests can be reduced by 66 (61%)
109
43
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shinjuku 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 34 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
shinjuku.gracery.com
1375 ms
wp-emoji-release.min.js
558 ms
reset.css
476 ms
style.css
478 ms
jquery-ui.css
11 ms
main.css
482 ms
jquery.fancybox.css
479 ms
jquery.min.js
9 ms
core.min.js
571 ms
jquery.ui.datepicker.min.js
947 ms
jquery.ui.datepicker-en.js
952 ms
js
27 ms
jquery.gmap.min.js
951 ms
fbparam.js
962 ms
fblib.js
1029 ms
jquery.cycle2.js
1046 ms
jquery.fancybox.pack.js
1418 ms
custom.js
1421 ms
jquery.cookie.js
1424 ms
browser-redirect.js
1425 ms
fb_custom.js
1516 ms
fbfulltrack.js
1524 ms
sitepress.js
1892 ms
font-awesome.css
9 ms
css
28 ms
common.js
3 ms
util.js
13 ms
geocoder.js
12 ms
trans.gif
176 ms
ga.js
40 ms
logo-header2.png
544 ms
router.php
230 ms
ja.png
531 ms
en.png
534 ms
fr.png
534 ms
zh-hans.png
568 ms
zh-hant.png
568 ms
de.png
931 ms
it.png
932 ms
ru.png
946 ms
es.png
951 ms
Hong-Kong-Flag.jpg
1017 ms
id.png
1025 ms
ko.png
1407 ms
ms.png
1406 ms
pt-pt.png
1415 ms
Flag_of_the_Philippines.jpg
1427 ms
th.png
1487 ms
vi.png
1494 ms
bg_calendar.png
1877 ms
bnr_godz.jpg
1881 ms
en_evening_img_Gracery-Shinjuku-440x350.jpg
2118 ms
loader.GIF
1916 ms
loading.html
1927 ms
VEvp19rd0TY
84 ms
__utm.gif
14 ms
__utm.gif
19 ms
bg_offers.png
1897 ms
fontawesome-webfont.woff
7 ms
logo_wifi.png
2277 ms
visit.phtml
102 ms
www-embed-player-vflfNyN_r.css
34 ms
www-embed-player.js
47 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
46 ms
ad_status.js
49 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
44 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
46 ms
fbX.min.js
193 ms
map.js
21 ms
marker.js
19 ms
router.php
261 ms
router.php
290 ms
ui-bg_flat_75_ffffff_40x100.png
38 ms
1_Gracery-Shinjuku.jpg
3017 ms
2_Gracery-Shinjuku.jpg
3022 ms
3_Gracery-Shinjuku.jpg
3082 ms
4_Gracery-Shinjuku.jpg
3091 ms
5_Gracery-Shinjuku.jpg
3238 ms
6_Gracery-Shinjuku.jpg
3490 ms
onion.js
20 ms
openhand_8_8.cur
32 ms
stats.js
22 ms
controls.js
15 ms
ViewportInfoService.GetViewportInfo
72 ms
transparent.png
17 ms
css
36 ms
marker.png
32 ms
google4.png
33 ms
infowindow.js
29 ms
mapcnt6.png
22 ms
sv5.png
22 ms
tmapctrl.png
23 ms
cb_scout5.png
26 ms
tmapctrl4.png
23 ms
imgs8.png
20 ms
vt
11 ms
vt
7 ms
vt
10 ms
vt
9 ms
vt
12 ms
vt
9 ms
vt
8 ms
vt
14 ms
vt
12 ms
vt
13 ms
vt
12 ms
vt
13 ms
vt
11 ms
AuthenticationService.Authenticate
233 ms
87616a303a36bc7408cea12c214f60fc.jpg
939 ms
c1764ceba38462f50a8deb248f210683.jpg
1087 ms
4cbd727f83d9dc094dd50ad3be65c65b.jpg
1094 ms
1729b67afdfb1c39e77d37e18fffe052.jpg
1105 ms
shinjuku.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
Image elements do not have [alt] attributes
Links do not have a discernible name
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
shinjuku.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
Missing source maps for large first-party JavaScript
shinjuku.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
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 Shinjuku.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 Shinjuku.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.
shinjuku.gracery.com
Open Graph description is not detected on the main page of Shinjuku 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: