Tools & Wizards About Us
idi.or.jp screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

idi.or.jp

IDI-JAPAN | IDI-JAPAN contribute to the development of world wide social infrastructures with outstanding consulting skills and remarkable experiences...

Page Load Speed

7.7 sec in total

First Response

1.6 sec

Resources Loaded

5.9 sec

Page Rendered

145 ms

idi.or.jp screenshot

About Website

Click here to check amazing IDI content. Otherwise, check out these important facts you probably never knew about idi.or.jp

IDI-JAPAN contribute to the development of world wide social infrastructures with outstanding consulting skills and remarkable experiences.

Visit idi.or.jp

Key Findings

We analyzed Idi.or.jp page load time and found that the first response time was 1.6 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

idi.or.jp performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value15.3 s

0/100

25%

SI (Speed Index)

Value13.8 s

1/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.019

100/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

1596 ms

style.css

516 ms

styles.css

346 ms

frontend.css

347 ms

wp-style.css

860 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 93% of them (40 requests) were addressed to the original Idi.or.jp, 2% (1 request) were made to Yubinbango.github.io and 2% (1 request) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Idi.or.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 298.9 kB (18%)

Content Size

1.7 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 18.4 kB

  • Original 24.7 kB
  • After minification 24.2 kB
  • After compression 6.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. 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 18.4 kB or 75% of the original size.

Image Optimization

-2%

Potential reduce by 30.3 kB

  • Original 1.3 MB
  • After minification 1.3 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. IDI images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 219.3 kB

  • Original 331.3 kB
  • After minification 324.7 kB
  • After compression 112.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 219.3 kB or 66% of the original size.

CSS Optimization

-62%

Potential reduce by 30.8 kB

  • Original 50.1 kB
  • After minification 42.8 kB
  • After compression 19.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. Idi.or.jp needs all CSS files to be minified and compressed as it can save up to 30.8 kB or 62% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (64%)

Requests Now

42

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

1596 ms

style.css

style.css

516 ms

styles.css

styles.css

346 ms

frontend.css

frontend.css

347 ms

wp-style.css

wp-style.css

860 ms

admin.css

admin.css

411 ms

wpfront-scroll-top.min.css

wpfront-scroll-top.min.css

391 ms

child-pages-shortcode.min.css

child-pages-shortcode.min.css

545 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

545 ms

jquery.js

jquery.js

909 ms

jquery-migrate.min.js

jquery-migrate.min.js

588 ms

jquery.tablesorter.min.js

jquery.tablesorter.min.js

857 ms

jquery.metadata.js

jquery.metadata.js

689 ms

wp-script.js

wp-script.js

692 ms

child-pages-shortcode.min.js

child-pages-shortcode.min.js

765 ms

jquery-1.12.0.min.js

jquery-1.12.0.min.js

1207 ms

script.js

script.js

865 ms

yubinbango.js

yubinbango.js

24 ms

all.css

all.css

36 ms

js

js

70 ms

flexslider.css

flexslider.css

725 ms

public.css

public.css

813 ms

scripts.js

scripts.js

1038 ms

hlst-extend.min.js

hlst-extend.min.js

822 ms

wpfront-scroll-top.min.js

wpfront-scroll-top.min.js

865 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

902 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

984 ms

wp-embed.min.js

wp-embed.min.js

1037 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

1042 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

754 ms

logo_en.png

logo_en.png

174 ms

jp.png

jp.png

174 ms

us.png

us.png

173 ms

slide1_en.jpg

slide1_en.jpg

889 ms

slide2.jpg

slide2.jpg

554 ms

DSC02988-1200x485.jpg

DSC02988-1200x485.jpg

781 ms

DSC02970-1200x485.jpg

DSC02970-1200x485.jpg

689 ms

IMG_002-1200x485.jpg

IMG_002-1200x485.jpg

521 ms

slide4.jpg

slide4.jpg

1387 ms

top_katudou_back.jpg

top_katudou_back.jpg

694 ms

katudou_pic2.jpg

katudou_pic2.jpg

727 ms

logo_footer_en.png

logo_footer_en.png

860 ms

1.png

1.png

867 ms

Accessibility Review

idi.or.jp accessibility score

77

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.

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

Form elements do not have associated labels

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

idi.or.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

idi.or.jp SEO score

83

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

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Idi.or.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Idi.or.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

idi.or.jp

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