Tools & Wizards About Us
inno.go.jp screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

inno.go.jp

異能（Inno）vation

Page Load Speed

4.2 sec in total

First Response

73 ms

Resources Loaded

3.6 sec

Page Rendered

561 ms

inno.go.jp screenshot

About Website

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

【異能（Inno）vation】独創的な人向け特別枠「異能(Inno)vation」プログラム。総務省は、失敗を恐れず探求するICT技術課題への挑戦者-異能（Inno）な人を探しています。

Visit inno.go.jp

Key Findings

We analyzed Inno.go.jp page load time and found that the first response time was 73 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

inno.go.jp performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value10.4 s

0/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value740 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.146

77/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

inno.go.jp

73 ms

inno.go.jp

737 ms

www.inno.go.jp

694 ms

gtm.js

64 ms

slick.css

731 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 84% of them (27 requests) were addressed to the original Inno.go.jp, 6% (2 requests) were made to Googletagmanager.com and 6% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Inno.go.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 65.8 kB (6%)

Content Size

1.0 MB

After Optimization

977.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Inno.go.jp main page is 1.0 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. 40% of websites need less resources to load. Images take 943.9 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 19.5 kB

  • Original 25.6 kB
  • After minification 23.3 kB
  • After compression 6.1 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 19.5 kB or 76% of the original size.

Image Optimization

-4%

Potential reduce by 38.3 kB

  • Original 943.9 kB
  • After minification 905.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. Inno images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 4.0 kB

  • Original 45.1 kB
  • After minification 45.1 kB
  • After compression 41.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. This website has mostly compressed JavaScripts.

CSS Optimization

-14%

Potential reduce by 4.0 kB

  • Original 28.1 kB
  • After minification 28.1 kB
  • After compression 24.2 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. Inno.go.jp needs all CSS files to be minified and compressed as it can save up to 4.0 kB or 14% of the original size.

Requests Breakdown

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

Requests Now

26

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

inno.go.jp

inno.go.jp

73 ms

inno.go.jp

inno.go.jp

737 ms

www.inno.go.jp

www.inno.go.jp

694 ms

gtm.js

gtm.js

64 ms

slick.css

slick.css

731 ms

slick-theme.css

slick-theme.css

731 ms

fontawesome-all.min.css

fontawesome-all.min.css

34 ms

common_ja.css

common_ja.css

39 ms

top_ja.css

top_ja.css

747 ms

css2

css2

39 ms

css2

css2

59 ms

jquery.js

jquery.js

17 ms

totop.js

totop.js

10 ms

slick.js

slick.js

808 ms

gtm.js

gtm.js

232 ms

logo-header.png

logo-header.png

519 ms

innouvators2.jpg

innouvators2.jpg

698 ms

book2022.jpg

book2022.jpg

790 ms

icon-facebook.svg

icon-facebook.svg

726 ms

icon-instagram.svg

icon-instagram.svg

699 ms

logo-black2.png

logo-black2.png

666 ms

icon-youtube.svg

icon-youtube.svg

1026 ms

footer01.png

footer01.png

1188 ms

footer02.png

footer02.png

883 ms

bg_02.png

bg_02.png

854 ms

bg_01.png

bg_01.png

888 ms

bg_01_r.png

bg_01_r.png

1443 ms

arrow_right.png

arrow_right.png

1031 ms

arrow_dots.png

arrow_dots.png

1361 ms

ajax-loader.gif

ajax-loader.gif

1168 ms

VdGDAZweH5EbgHY6YExcZfDoj0B4Z9Cm5A.ttf

VdGDAZweH5EbgHY6YExcZfDoj0B4Z9Cm5A.ttf

417 ms

slick.woff

slick.woff

891 ms

Accessibility Review

inno.go.jp accessibility score

98

Accessibility Issues

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.

Best Practices

inno.go.jp best practices score

75

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

High

Browser errors were logged to the console

SEO Factors

inno.go.jp SEO score

99

Search Engine Optimization Advices

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 Inno.go.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 Inno.go.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

inno.go.jp

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