Tools & Wizards About Us

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

nni.ne.jp

NNI　ベストな商品とサービスをご提供いたします

Page Load Speed

2.7 sec in total

First Response

730 ms

Resources Loaded

1.9 sec

Page Rendered

74 ms

About Website

Click here to check amazing NNI content. Otherwise, check out these important facts you probably never knew about nni.ne.jp

NNi（エヌエヌアイ）お客様の満足を創造するために、幅広い金融商品をご提供いたします。

Visit nni.ne.jp

Key Findings

We analyzed Nni.ne.jp page load time and found that the first response time was 730 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

nni.ne.jp performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.1 s

99/100

10%

LCP (Largest Contentful Paint)

Value1.1 s

100/100

25%

SI (Speed Index)

Value2.0 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value1.1 s

100/100

10%

Network Requests Diagram

nni.ne.jp

730 ms

part.css

201 ms

flash.js

324 ms

common.css

164 ms

test_back.png

163 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that all of those requests were addressed to Nni.ne.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (867 ms) belongs to the original domain Nni.ne.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 40.4 kB (30%)

Content Size

136.8 kB

After Optimization

96.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nni.ne.jp main page is 136.8 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. 15% of websites need less resources to load. Images take 116.8 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 6.5 kB

  • Original 9.2 kB
  • After minification 7.6 kB
  • After compression 2.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 1.6 kB, which is 17% 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 6.5 kB or 70% of the original size.

Image Optimization

-22%

Potential reduce by 25.8 kB

  • Original 116.8 kB
  • After minification 91.0 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, NNI needs image optimization as it can save up to 25.8 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-57%

Potential reduce by 515 B

  • Original 906 B
  • After minification 849 B
  • After compression 391 B

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 515 B or 57% of the original size.

CSS Optimization

-77%

Potential reduce by 7.6 kB

  • Original 9.9 kB
  • After minification 7.6 kB
  • After compression 2.3 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. Nni.ne.jp needs all CSS files to be minified and compressed as it can save up to 7.6 kB or 77% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

24

After Optimization

24

  • Images
  • JavaScript
  • CSS

The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NNI. According to our analytics all requests are already optimized.

Network Requests Diagram

Accessibility Review

nni.ne.jp accessibility score

61

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

High

<object> elements do not have alternate text

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

nni.ne.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

nni.ne.jp SEO score

58

Search Engine Optimization Advices

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

High

Document uses plugins

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 Nni.ne.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 Nni.ne.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

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