5.8 sec in total
521 ms
5.2 sec
105 ms
Visit grandpalace.co.jp now to see the best up-to-date Grandpalace content for Japan and also check out these interesting facts you probably never knew about grandpalace.co.jp
2021年6月30日をもちましてホテルの営業を終了いたしました。
Visit grandpalace.co.jpWe analyzed Grandpalace.co.jp page load time and found that the first response time was 521 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
grandpalace.co.jp performance score
name
value
score
weighting
Value7.4 s
1/100
10%
Value8.5 s
1/100
25%
Value10.6 s
7/100
10%
Value260 ms
83/100
30%
Value0.026
100/100
15%
Value8.6 s
37/100
10%
521 ms
525 ms
730 ms
185 ms
368 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that 91% of them (39 requests) were addressed to the original Grandpalace.co.jp, 2% (1 request) were made to Fonts.googleapis.com and 2% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Grandpalace.co.jp.
Page size can be reduced by 36.6 kB (15%)
240.4 kB
203.8 kB
In fact, the total size of Grandpalace.co.jp main page is 240.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Javascripts take 194.1 kB which makes up the majority of the site volume.
Potential reduce by 5.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 5.8 kB or 68% of the original size.
Potential reduce by 1.7 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, Grandpalace needs image optimization as it can save up to 1.7 kB or 43% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 24.5 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 24.5 kB or 13% of the original size.
Potential reduce by 4.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. Grandpalace.co.jp needs all CSS files to be minified and compressed as it can save up to 4.6 kB or 14% of the original size.
Number of requests can be reduced by 28 (82%)
34
6
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Grandpalace. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
grandpalace.co.jp
521 ms
www.grandpalace.co.jp
525 ms
www.grandpalace.co.jp
730 ms
default.css
185 ms
design.css
368 ms
design_close.css
504 ms
jquery.fancybox-1.3.4.css
514 ms
jquery-ui-1.9.2.custom.css
513 ms
jquery-ui-fix.css
516 ms
flexslider.fix.css
511 ms
slick.css
544 ms
slick-theme.css
676 ms
css
42 ms
embed
227 ms
sugar-1.4.1.min.js
856 ms
jquery-1.9.1.min.js
939 ms
jquery-migrate-1.2.1.min.js
716 ms
jquery-ui-1.9.2.custom.min.js
1204 ms
jquery.ui.datepicker-ja.min.js
722 ms
gcalendar-holidays.min.js
847 ms
jquery.cookie.min.js
854 ms
jquery.fancybox-1.3.4.pack.js
909 ms
underscore-1.8.3.min.js
1018 ms
base64.min.js
1025 ms
jsdeferred.jquery.min.js
1027 ms
jquery.easing.1.3.min.js
1086 ms
jquery.flexslider-min.js
1110 ms
slick.min.js
1198 ms
jquery.matchHeight-min.js
1196 ms
common.js
1200 ms
sumaho_nav.js
1270 ms
topics_list_index.js
1392 ms
weather.min.js
1367 ms
js
57 ms
footer_bg.png
719 ms
footerclose_logo.svg
701 ms
AozoraMinchoRegular-Sub.woff
2342 ms
6xKhdSpbNNCT-sWPCms.ttf
17 ms
NotoSansCJKjp-DemiLight-Sub.woff
2710 ms
fontawesome-webfont.woff
1368 ms
sumaho_nav.html
172 ms
index.php
176 ms
index.php
176 ms
grandpalace.co.jp 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.
grandpalace.co.jp 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
grandpalace.co.jp 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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grandpalace.co.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 Grandpalace.co.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.
grandpalace.co.jp
Open Graph description is not detected on the main page of Grandpalace. 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: