Tools & Wizards About Us
inno.go.jp screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

inno.go.jp

異能（Inno）vation

Page Load Speed

2 sec in total

First Response

313 ms

Resources Loaded

1.4 sec

Page Rendered

343 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 313 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

inno.go.jp performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value6.0 s

47/100

10%

TBT (Total Blocking Time)

Value240 ms

85/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value8.4 s

39/100

10%

Network Requests Diagram

inno.go.jp

313 ms

common.css

157 ms

top.css

294 ms

jquery.min.js

27 ms

jquery-contained-sticky-scroll-min.js

311 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 50% of them (10 requests) were addressed to the original Inno.go.jp, 10% (2 requests) were made to Platform.twitter.com and 10% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (585 ms) belongs to the original domain Inno.go.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 98.2 kB (62%)

Content Size

159.0 kB

After Optimization

60.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 17.9 kB

  • Original 23.0 kB
  • After minification 16.6 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 6.4 kB, which is 28% 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 17.9 kB or 78% of the original size.

Image Optimization

-57%

Potential reduce by 41.6 kB

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

JavaScript Optimization

-60%

Potential reduce by 33.2 kB

  • Original 55.0 kB
  • After minification 54.9 kB
  • After compression 21.8 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 33.2 kB or 60% of the original size.

CSS Optimization

-75%

Potential reduce by 5.6 kB

  • Original 7.4 kB
  • After minification 5.8 kB
  • After compression 1.8 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 5.6 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (37%)

Requests Now

19

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 19 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 8 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

inno.go.jp

inno.go.jp

313 ms

common.css

common.css

157 ms

top.css

top.css

294 ms

jquery.min.js

jquery.min.js

27 ms

jquery-contained-sticky-scroll-min.js

jquery-contained-sticky-scroll-min.js

311 ms

ga.js

ga.js

320 ms

logo.png

logo.png

294 ms

soumu.png

soumu.png

169 ms

sub.png

sub.png

439 ms

catch.png

catch.png

169 ms

diagram.gif

diagram.gif

585 ms

widgets.js

widgets.js

84 ms

analytics.js

analytics.js

10 ms

collect

collect

29 ms

like.php

like.php

86 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

127 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

34 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

29 ms

syndication

syndication

85 ms

499399847795904513

499399847795904513

401 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

98

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

    N/A

  • 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 neither this language nor any other was claimed in <html> or <meta> tags. 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 description is not detected on the main page of Inno. 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: