Tools & Wizards About Us
ninja.co.jp screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

ninja.co.jp

忍者ツールズ｜ホームページ ブログ アクセス解析 カウンター メールフォーム

Page Load Speed

6.4 sec in total

First Response

572 ms

Resources Loaded

5.7 sec

Page Rendered

130 ms

ninja.co.jp screenshot

About Website

Visit ninja.co.jp now to see the best up-to-date Ninja content for Japan and also check out these interesting facts you probably never knew about ninja.co.jp

無料ホームページ、ブログ、アクセス解析、アクセスカウンターなど、HPやレンタルCGIの定番『忍者ツールズ』。無料で作成・登録できます。携帯にも対応。

Visit ninja.co.jp

Key Findings

We analyzed Ninja.co.jp page load time and found that the first response time was 572 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

ninja.co.jp performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

1/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value3,360 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.8 s

5/100

10%

Network Requests Diagram

ninja.co.jp

572 ms

www.ninja.co.jp

585 ms

common.css

184 ms

reset.css

364 ms

contents.css

545 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 63% of them (34 requests) were addressed to the original Ninja.co.jp, 11% (6 requests) were made to Asumi.shinobi.jp and 9% (5 requests) were made to V2st.shinobi.jp. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source V2st.shinobi.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 191.3 kB (56%)

Content Size

342.7 kB

After Optimization

151.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ninja.co.jp main page is 342.7 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. 20% of websites need less resources to load. Javascripts take 184.5 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 10.9 kB

  • Original 14.2 kB
  • After minification 9.9 kB
  • After compression 3.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 4.4 kB, which is 31% 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 10.9 kB or 77% of the original size.

Image Optimization

-5%

Potential reduce by 3.5 kB

  • Original 71.0 kB
  • After minification 67.6 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. Ninja images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 117.5 kB

  • Original 184.5 kB
  • After minification 184.4 kB
  • After compression 67.0 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 117.5 kB or 64% of the original size.

CSS Optimization

-81%

Potential reduce by 59.4 kB

  • Original 72.9 kB
  • After minification 53.9 kB
  • After compression 13.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. Ninja.co.jp needs all CSS files to be minified and compressed as it can save up to 59.4 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

51

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ninja.co.jp

ninja.co.jp

572 ms

www.ninja.co.jp

www.ninja.co.jp

585 ms

common.css

common.css

184 ms

reset.css

reset.css

364 ms

contents.css

contents.css

545 ms

ninja.css

ninja.css

549 ms

index.css

index.css

374 ms

409 ms

ninja-ui-unreset.js

ninja-ui-unreset.js

394 ms

pageNavigation.js

pageNavigation.js

546 ms

encount

encount

526 ms

108000001

108000001

701 ms

fire

fire

533 ms

ui-unreset.min.css

ui-unreset.min.css

548 ms

ninja.min.js

ninja.min.js

614 ms

fire

fire

169 ms

jquery.min.js

jquery.min.js

1976 ms

1.13.17

1.13.17

415 ms

logoNt.gif

logoNt.gif

183 ms

logoHp.gif

logoHp.gif

190 ms

logoBlog.gif

logoBlog.gif

184 ms

logoAdmax.gif

logoAdmax.gif

200 ms

logoAnalyze.gif

logoAnalyze.gif

189 ms

logoAnalysis.gif

logoAnalysis.gif

184 ms

logoCluster.gif

logoCluster.gif

361 ms

logoSandbox.gif

logoSandbox.gif

364 ms

logoBarrier.gif

logoBarrier.gif

364 ms

logoVisitor.gif

logoVisitor.gif

376 ms

logoCounter.gif

logoCounter.gif

374 ms

logoOmatome.gif

logoOmatome.gif

396 ms

logoEnqueteform.gif

logoEnqueteform.gif

542 ms

logoMailform.gif

logoMailform.gif

545 ms

logoRecommend.gif

logoRecommend.gif

546 ms

logoTranslator.gif

logoTranslator.gif

559 ms

btnRegist.gif

btnRegist.gif

560 ms

txtLogin.gif

txtLogin.gif

594 ms

btnLogin.gif

btnLogin.gif

723 ms

gtm.js

gtm.js

46 ms

ico-guideListDark.gif

ico-guideListDark.gif

723 ms

ico-guideList.gif

ico-guideList.gif

724 ms

iconTwitter.gif

iconTwitter.gif

741 ms

iconFacebook.gif

iconFacebook.gif

744 ms

track

track

178 ms

995

995

808 ms

track

track

174 ms

track

track

342 ms

backPageTop.gif

backPageTop.gif

760 ms

analytics.js

analytics.js

6 ms

NewScript

NewScript

544 ms

collect

collect

3 ms

collect

collect

61 ms

sync

sync

175 ms

track

track

167 ms

NewReceive

NewReceive

368 ms

Accessibility Review

ninja.co.jp accessibility score

58

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-*] attributes do not match their roles

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

ninja.co.jp best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

ninja.co.jp SEO score

89

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ninja.co.jp 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 Ninja.co.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

ninja.co.jp

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