Tools & Wizards About Us
9hours.jp screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

9hours.jp

ナインアワーズ｜最低価格保証｜公式サイト

Page Load Speed

9.2 sec in total

First Response

497 ms

Resources Loaded

8.5 sec

Page Rendered

197 ms

9hours.jp screenshot

About Website

Welcome to 9hours.jp homepage info - get ready to check 9 Hours best content right away, or after learning these important things about 9hours.jp

都市生活にフィットする宿泊機能と新しい滞在価値を提供する『9h(ナインアワーズ)』公式サイトです。都市の新たなインフラトランジット・ステイをご体験下さい。ご予約はこちらから。

Visit 9hours.jp

Key Findings

We analyzed 9hours.jp page load time and found that the first response time was 497 ms and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

9hours.jp performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value25.6 s

0/100

25%

SI (Speed Index)

Value9.7 s

10/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.1 s

52/100

10%

Network Requests Diagram

9hours.jp

497 ms

ninehours.co.jp

456 ms

ninehours.co.jp

755 ms

jquery-1.9.1.min.js

985 ms

base.js

481 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original 9hours.jp, 74% (26 requests) were made to Ninehours.co.jp and 11% (4 requests) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Ninehours.co.jp.

Page Optimization Overview & Recommendations

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

Content Size

2.5 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 9hours.jp main page is 2.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. 30% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 6.8 kB

  • Original 9.7 kB
  • After minification 9.4 kB
  • After compression 2.9 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 6.8 kB or 70% of the original size.

Image Optimization

-3%

Potential reduce by 65.3 kB

  • Original 2.0 MB
  • After minification 1.9 MB

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. 9 Hours images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 312.7 kB

  • Original 477.0 kB
  • After minification 445.2 kB
  • After compression 164.3 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 312.7 kB or 66% of the original size.

CSS Optimization

-84%

Potential reduce by 75.4 kB

  • Original 89.9 kB
  • After minification 69.8 kB
  • After compression 14.5 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. 9hours.jp needs all CSS files to be minified and compressed as it can save up to 75.4 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (63%)

Requests Now

32

After Optimization

12

  • Images
  • JavaScript
  • CSS

The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 9 Hours. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

9hours.jp

9hours.jp

497 ms

ninehours.co.jp

ninehours.co.jp

456 ms

ninehours.co.jp

ninehours.co.jp

755 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

985 ms

base.js

base.js

481 ms

modernizr.custom.js

modernizr.custom.js

507 ms

respond.min.js

respond.min.js

512 ms

jquery.backstretch.min.js

jquery.backstretch.min.js

530 ms

footerFixed.js

footerFixed.js

540 ms

js

js

99 ms

jquery.easing.js

jquery.easing.js

1024 ms

jquery.flexslider.js

jquery.flexslider.js

1512 ms

reset.css

reset.css

1108 ms

option.css

option.css

1304 ms

base.css

base.css

1166 ms

flexslider.css

flexslider.css

2836 ms

analytics_nin.js

analytics_nin.js

1755 ms

overlaymenu.js

overlaymenu.js

1754 ms

responsive_pc.css

responsive_pc.css

1076 ms

analytics.js

analytics.js

117 ms

logo_sogo.png

logo_sogo.png

784 ms

icon_tw.png

icon_tw.png

374 ms

icon_fb.png

icon_fb.png

609 ms

icon_youtube.png

icon_youtube.png

607 ms

kv1.jpg

kv1.jpg

2400 ms

kv2.jpg

kv2.jpg

2867 ms

kv3.jpg

kv3.jpg

2783 ms

kv4.jpg

kv4.jpg

3035 ms

collect

collect

60 ms

collect

collect

72 ms

responsive_sp.css

responsive_sp.css

494 ms

common.js

common.js

49 ms

util.js

util.js

368 ms

stats.js

stats.js

114 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

394 ms

Accessibility Review

9hours.jp accessibility score

74

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-hidden="true"] elements contain focusable descendents

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

9hours.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

9hours.jp SEO score

73

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document doesn't use 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 9hours.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 9hours.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.

Social Sharing Optimization

9hours.jp

Open Graph data is detected on the main page of 9 Hours. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: