14.9 sec in total
529 ms
11.5 sec
2.8 sec
Click here to check amazing Nnr H content for Japan. Otherwise, check out these important facts you probably never knew about nnr-h.com
【最低価格保証|ご予約は当サイトが一番お得です。】西日本鉄道株式会社が運営するホテルグループです。観光、催事、ビジネスなど多彩なシーンでご利用いただける国内外のホテルをご案内いたします。
Visit nnr-h.comWe analyzed Nnr-h.com page load time and found that the first response time was 529 ms and then it took 14.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
nnr-h.com performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value9.9 s
0/100
25%
Value18.1 s
0/100
10%
Value2,850 ms
3/100
30%
Value0.074
95/100
15%
Value32.8 s
0/100
10%
529 ms
1374 ms
75 ms
118 ms
477 ms
Our browser made a total of 159 requests to load all elements on the main page. We found that 73% of them (116 requests) were addressed to the original Nnr-h.com, 16% (25 requests) were made to Google.com and 6% (9 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (6.9 sec) belongs to the original domain Nnr-h.com.
Page size can be reduced by 558.2 kB (9%)
5.9 MB
5.3 MB
In fact, the total size of Nnr-h.com main page is 5.9 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 5.2 MB which makes up the majority of the site volume.
Potential reduce by 111.3 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 25.0 kB, which is 19% 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 111.3 kB or 84% of the original size.
Potential reduce by 94.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. Nnr H images are well optimized though.
Potential reduce by 168.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 168.8 kB or 42% of the original size.
Potential reduce by 183.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. Nnr-h.com needs all CSS files to be minified and compressed as it can save up to 183.6 kB or 89% of the original size.
Number of requests can be reduced by 31 (20%)
154
123
The browser has sent 154 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nnr H. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
nnr-h.com
529 ms
nnr-h.com
1374 ms
gtm.js
75 ms
gtm.js
118 ms
default.css
477 ms
common.css
985 ms
slick.css
490 ms
magnific-popup.css
491 ms
font-awesome.css
49 ms
ionicons.min.css
61 ms
jquery-ui.min.css
794 ms
homepage.css
977 ms
jquery-2.1.4.min.js
1312 ms
config.js
660 ms
slick.min.js
830 ms
jquery.magnific-popup.min.js
988 ms
common.js
956 ms
jquery-ui.min.js
1002 ms
search.js
1115 ms
homepage.js
1139 ms
map.js
1145 ms
setNewsAjax.js
1147 ms
keyword_search.js
685 ms
logo_nishitetsu_grandhotel.png
382 ms
logo_nishitetsu_grandhotel_white.png
382 ms
logo_solaria.png
383 ms
logo_solaria_white.png
383 ms
logo_croom.png
381 ms
logo_croom_white.png
382 ms
logo_nishitetsuinn.png
388 ms
logo_nishitetsuinn_white.png
384 ms
logo_group_white.png
385 ms
st_bestrate.png
384 ms
bn_app.jpg
388 ms
ic_region.png
386 ms
logo_nitshitetsu_grand_hotel.png
497 ms
logo_nitshitetsu_grand_hotel_white.png
504 ms
logo_solaria_nishitetsu_hotel.png
505 ms
logo_solaria_nishitetsu_hotel_white.png
507 ms
logo_nishitetsu_hotel_croom.png
509 ms
logo_nishitetsu_hotel_croom_white.png
515 ms
logo_nishitetsu_inn.png
656 ms
logo_nishitetsu_inn_white.png
668 ms
img_point01.png
669 ms
img_point02.png
670 ms
img_point03.png
671 ms
bn_magazine01.png
846 ms
nnr-h.com
1828 ms
283x188_ea1e9d427fb5664c32c517a73e421e58_c133d787652553db34b8b4ea1c4383a8368c90b3.jpg
1149 ms
283x188_ea1e9d427fb5664c32c517a73e421e58_af19ec9186f9caad8351ad1140a34746aca70b36.jpg
1318 ms
283x188_ea1e9d427fb5664c32c517a73e421e58_798e00d1fddbce1c19956b133687a29b946ad8ad.png
833 ms
283x188_ea1e9d427fb5664c32c517a73e421e58_6b2f3a62c3335e79b6106247f83fc64db464d9e6.png
836 ms
ajax-loader.gif
1001 ms
bn_kurashinet.jpg
1003 ms
bn_sdgs.png
1022 ms
bn_nishitetsu_group.jpg
1163 ms
ic_group.png
1162 ms
bn_nishitetsu_hotel_group.png
1183 ms
sdk.js
145 ms
embed
348 ms
embed
526 ms
embed
551 ms
embed
602 ms
embed
551 ms
embed
541 ms
embed
562 ms
embed
703 ms
embed
721 ms
embed
556 ms
embed
759 ms
embed
749 ms
embed
735 ms
embed
772 ms
embed
889 ms
embed
906 ms
embed
1004 ms
embed
907 ms
embed
963 ms
embed
979 ms
embed
1131 ms
embed
1093 ms
embed
1124 ms
embed
1160 ms
embed
1169 ms
bn_nitshitetsu_grand_hotel.png
1253 ms
ajax_grandhotel_news.php
952 ms
1268 ms
1317 ms
1341 ms
1545 ms
bn_solaria_nishitetsu_hotel.png
1112 ms
bn_nishitetsu_hotel_croom.png
1275 ms
bn_nishitetsu_inn.png
1427 ms
img_pickup_restaurant.jpg
1438 ms
img_pickup_wedding.jpg
1478 ms
img_pickup_banquet.jpg
1658 ms
js
61 ms
img_grandhotel.jpg
1911 ms
sdk.js
13 ms
ionicons.ttf
36 ms
fontawesome-webfont.woff
37 ms
105 ms
search.js
4 ms
geometry.js
7 ms
main.js
12 ms
img_solaria_sapporo.jpg
1815 ms
img_solaria_ginza.jpg
2302 ms
img_solaria_kyoto_p.jpg
1693 ms
img_solaria.jpg
2235 ms
img_solaria_kagoshima.jpg
2184 ms
img_solaria_seoul.jpg
1851 ms
js
18 ms
search.js
5 ms
geometry.js
3 ms
main.js
10 ms
img_solaria_busan.jpg
1972 ms
img_solaria_bangkok.jpg
1977 ms
img_solaria_taipei.jpg
2194 ms
img_croom_nagoya.jpg
2285 ms
img_croom_fukuoka.jpg
2144 ms
js
17 ms
img_croom_gion.jpg
2679 ms
img_croom_bangkoksilom.jpg
3214 ms
img_n-inn_nihonbashi.jpg
2915 ms
img_n-inn_shinjuku.jpg
1984 ms
img_n-inn_kamata.jpg
2030 ms
img_n-inn_nagoyanishiki.jpg
2102 ms
img_n-inn_kochi.jpg
2004 ms
img_n-inn_tenjin.jpg
2045 ms
img_n-inn_fukuoka.jpg
2997 ms
img_n-inn_kurosaki.jpg
2140 ms
img_n-inn_kokura.jpg
2069 ms
img_n-inn_beppu.jpg
2181 ms
img_n-inn_naha.jpg
2227 ms
img_main19.jpg
2334 ms
img_main17.jpg
6897 ms
ic_st_brand.png
2067 ms
img_grandhotel.jpg
2191 ms
img_solaria.jpg
2526 ms
img_croom.jpg
2187 ms
img_inn.jpg
2240 ms
ic_st_group.png
2336 ms
img_restaurant.jpg
2849 ms
img_wedding.jpg
2314 ms
img_cruising.jpg
3115 ms
img_banquet.jpg
2303 ms
780x200_ea1e9d427fb5664c32c517a73e421e58_a918e60ef111c591d502a74a2fdb8723f85390e1.png
2465 ms
bn_magazine03-pc.png
3286 ms
img_nophoto.jpg
2302 ms
283x188_ea1e9d427fb5664c32c517a73e421e58_47d9d9ec993c34206cd20a72a877cd35a426a0b0.jpg
2215 ms
283x188_ea1e9d427fb5664c32c517a73e421e58_9f61a55c908e904813c1607d033f97a60b4d51b8.jpg
2567 ms
283x188_ea1e9d427fb5664c32c517a73e421e58_34d1e47bd8297790838077f627befd8a4948ad68.jpg
2245 ms
283x188_ea1e9d427fb5664c32c517a73e421e58_933debe02fb5a4d8c992829dfbced9e90320843b.jpg
2274 ms
283x188_ea1e9d427fb5664c32c517a73e421e58_4858a8a7042c6c0bfef734aba92bd31703c07677.jpg
2313 ms
283x188_ea1e9d427fb5664c32c517a73e421e58_0c5ecd83b920f82acd5efb4c80a05ad42a6ac7a2.jpg
2375 ms
283x188_ea1e9d427fb5664c32c517a73e421e58_dc67e2cce6e7f2e926da9eea2f5f3fd13e28d58e.jpg
2429 ms
283x188_ea1e9d427fb5664c32c517a73e421e58_f8e6c24b591374e5d9de1a8605dd35bc986cde79.jpg
2376 ms
283x188_ea1e9d427fb5664c32c517a73e421e58_724af7d32f36a4ca959e0da512c821e9efbc5126.png
2370 ms
print.css
165 ms
nnr-h.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 input fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
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.
nnr-h.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
Browser errors were logged to the console
nnr-h.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 Nnr-h.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 Nnr-h.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.
nnr-h.com
Open Graph data is detected on the main page of Nnr H. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: