Tools & Wizards About Us
ninokuni.jp screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

ninokuni.jp

二ノ国 シリーズ

Page Load Speed

8.7 sec in total

First Response

356 ms

Resources Loaded

7.7 sec

Page Rendered

612 ms

ninokuni.jp screenshot

About Website

Welcome to ninokuni.jp homepage info - get ready to check Ninokuni best content for Japan right away, or after learning these important things about ninokuni.jp

レベルファイブが贈るRPG『二ノ国』シリーズ公式サイト

Visit ninokuni.jp

Key Findings

We analyzed Ninokuni.jp page load time and found that the first response time was 356 ms and then it took 8.3 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

ninokuni.jp performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value18.6 s

0/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value300 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value10.7 s

22/100

10%

Network Requests Diagram

ninokuni.jp

356 ms

ninokuni.jp

772 ms

www.ninokuni.jp

1107 ms

gtm.js

58 ms

import.css

256 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 Ninokuni.jp, 5% (2 requests) were made to Googletagmanager.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.4 sec) belongs to the original domain Ninokuni.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.4 MB (56%)

Content Size

6.1 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-89%

Potential reduce by 55.1 kB

  • Original 61.6 kB
  • After minification 56.0 kB
  • After compression 6.5 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 55.1 kB or 89% of the original size.

Image Optimization

-56%

Potential reduce by 3.3 MB

  • Original 5.9 MB
  • After minification 2.6 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. Obviously, Ninokuni needs image optimization as it can save up to 3.3 MB or 56% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-56%

Potential reduce by 73.5 kB

  • Original 132.0 kB
  • After minification 128.4 kB
  • After compression 58.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 73.5 kB or 56% of the original size.

CSS Optimization

-75%

Potential reduce by 5.0 kB

  • Original 6.6 kB
  • After minification 3.9 kB
  • After compression 1.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. Ninokuni.jp needs all CSS files to be minified and compressed as it can save up to 5.0 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (25%)

Requests Now

40

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ninokuni. 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 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

ninokuni.jp

ninokuni.jp

356 ms

ninokuni.jp

ninokuni.jp

772 ms

www.ninokuni.jp

www.ninokuni.jp

1107 ms

gtm.js

gtm.js

58 ms

import.css

import.css

256 ms

li-scroller.css

li-scroller.css

490 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

969 ms

jquery.li-scroller.1.0.mod.js

jquery.li-scroller.1.0.mod.js

632 ms

jquery.belatedPNG.min.js

jquery.belatedPNG.min.js

637 ms

smoothRollOver.js

smoothRollOver.js

619 ms

top.js

top.js

640 ms

js

js

60 ms

analytics.js

analytics.js

16 ms

collect

collect

14 ms

default.css

default.css

473 ms

top.css

top.css

607 ms

bg_footer.jpg

bg_footer.jpg

393 ms

logo_level5.png

logo_level5.png

242 ms

bg_header.jpg

bg_header.jpg

440 ms

logo.png

logo.png

244 ms

bg_topics.png

bg_topics.png

394 ms

bg_main.jpg

bg_main.jpg

231 ms

bg_main_top.jpg

bg_main_top.jpg

460 ms

bg_main_bottom.jpg

bg_main_bottom.jpg

668 ms

tit_game.png

tit_game.png

460 ms

btn_ninokuni2-switch_d.png

btn_ninokuni2-switch_d.png

2726 ms

btn_cross-worlds_d.png

btn_cross-worlds_d.png

2550 ms

btn_switch-ps4-steam_d.png

btn_switch-ps4-steam_d.png

2946 ms

btn_ninokuni2_180323_d.png

btn_ninokuni2_180323_d.png

2795 ms

bg_btns.jpg

bg_btns.jpg

1197 ms

btn2_d.png

btn2_d.png

1081 ms

btn3_d.png

btn3_d.png

1323 ms

tit_movie.png

tit_movie.png

1415 ms

bnr_movie.jpg

bnr_movie.jpg

1789 ms

bg_footer_inner.jpg

bg_footer_inner.jpg

1658 ms

link_official.png

link_official.png

1874 ms

footer_memo.png

footer_memo.png

2012 ms

btn_ninokuni2-switch_on.png

btn_ninokuni2-switch_on.png

4380 ms

btn_cross-worlds_on.png

btn_cross-worlds_on.png

4008 ms

btn_switch-ps4-steam_on.png

btn_switch-ps4-steam_on.png

3141 ms

btn_ninokuni2_180323_on.png

btn_ninokuni2_180323_on.png

4254 ms

btn2_on.png

btn2_on.png

3024 ms

btn3_on.png

btn3_on.png

3198 ms

Accessibility Review

ninokuni.jp accessibility score

100

Accessibility Issues

Best Practices

ninokuni.jp best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

ninokuni.jp SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

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

ninokuni.jp

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