Tools & Wizards About Us
nnr-h.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

nnr-h.com

【公式】西鉄ホテルグループ since1969

Page Load Speed

4 sec in total

First Response

714 ms

Resources Loaded

2.9 sec

Page Rendered

367 ms

nnr-h.com screenshot

About Website

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.com

Key Findings

We analyzed Nnr-h.com page load time and found that the first response time was 714 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

nnr-h.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value20.6 s

0/100

25%

SI (Speed Index)

Value12.8 s

2/100

10%

TBT (Total Blocking Time)

Value1,050 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.112

86/100

15%

TTI (Time to Interactive)

Value26.2 s

0/100

10%

Network Requests Diagram

nnr-h.com

714 ms

normalize.css

307 ms

font.css

334 ms

base.css

673 ms

skin.css

340 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 86% of them (37 requests) were addressed to the original Nnr-h.com, 7% (3 requests) were made to Google-analytics.com and 5% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Nnr-h.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 190.8 kB (18%)

Content Size

1.1 MB

After Optimization

887.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nnr-h.com main page is 1.1 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. 25% of websites need less resources to load. Images take 813.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 21.9 kB

  • Original 27.6 kB
  • After minification 23.7 kB
  • After compression 5.7 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 3.9 kB, which is 14% 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 21.9 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 1.1 kB

  • Original 813.2 kB
  • After minification 812.1 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.

JavaScript Optimization

-67%

Potential reduce by 126.0 kB

  • Original 188.2 kB
  • After minification 176.6 kB
  • After compression 62.2 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 126.0 kB or 67% of the original size.

CSS Optimization

-85%

Potential reduce by 41.7 kB

  • Original 49.1 kB
  • After minification 29.2 kB
  • After compression 7.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. Nnr-h.com needs all CSS files to be minified and compressed as it can save up to 41.7 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (50%)

Requests Now

38

After Optimization

19

  • Images
  • JavaScript
  • CSS

The browser has sent 38 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 8 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

nnr-h.com

nnr-h.com

714 ms

normalize.css

normalize.css

307 ms

font.css

font.css

334 ms

base.css

base.css

673 ms

skin.css

skin.css

340 ms

jquery.bxslider.css

jquery.bxslider.css

356 ms

jquery.js

jquery.js

935 ms

smoothScroll.js

smoothScroll.js

458 ms

common.js

common.js

502 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

674 ms

jkl-calendar.js

jkl-calendar.js

547 ms

directin-search.js

directin-search.js

599 ms

analytics.js

analytics.js

90 ms

bg_header.jpg

bg_header.jpg

1351 ms

bg_white.png

bg_white.png

155 ms

logo.png

logo.png

194 ms

ico_arrow01.png

ico_arrow01.png

194 ms

btn_point.png

btn_point.png

192 ms

main_img05.jpg

main_img05.jpg

892 ms

main_img04.jpg

main_img04.jpg

801 ms

main_img03.jpg

main_img03.jpg

578 ms

main_img01.gif

main_img01.gif

698 ms

main_img02.jpg

main_img02.jpg

699 ms

btn_navi.png

btn_navi.png

766 ms

ico_arrow02.png

ico_arrow02.png

868 ms

ico_ttl01.png

ico_ttl01.png

868 ms

img_grand.jpg

img_grand.jpg

956 ms

img_solaria.jpg

img_solaria.jpg

956 ms

img_croom.jpg

img_croom.jpg

1204 ms

img_inn.jpg

img_inn.jpg

1039 ms

bnr01.gif

bnr01.gif

1067 ms

bnr02.gif

bnr02.gif

1143 ms

bnr03.gif

bnr03.gif

1109 ms

bnr04.gif

bnr04.gif

1206 ms

btn_top.gif

btn_top.gif

1245 ms

full

full

90 ms

linkid.js

linkid.js

10 ms

bx_loader.gif

bx_loader.gif

1146 ms

btn_prev.gif

btn_prev.gif

1215 ms

btn_next.gif

btn_next.gif

1257 ms

collect

collect

26 ms

collect

collect

74 ms

ga-audiences

ga-audiences

36 ms

Accessibility Review

nnr-h.com accessibility score

86

Accessibility Issues

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

High

ARIA input fields do not have accessible names

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

nnr-h.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

nnr-h.com SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    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 it matches the claimed language. 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.

Social Sharing Optimization

nnr-h.com

Open Graph description is not detected on the main page of Nnr H. 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: