Tools & Wizards About Us
icr.co.jp screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 95% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    82% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

icr.co.jp

ICR：情報通信総合研究所 公式ホームページ

Page Load Speed

7.9 sec in total

First Response

740 ms

Resources Loaded

6.9 sec

Page Rendered

262 ms

icr.co.jp screenshot

About Website

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

情報通信総合研究所（ICR）の公式Webサイト。当社はNTT発足とともに誕生した、情報通信分野に特化したシンクタンクです。ICTに関わる調査分析を広く実施し、お客様の課題解決を支援します。情報誌や論文誌の発行も。

Visit icr.co.jp

Key Findings

We analyzed Icr.co.jp page load time and found that the first response time was 740 ms and then it took 7.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

icr.co.jp performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value36.7 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value1,270 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.258

48/100

15%

TTI (Time to Interactive)

Value38.7 s

0/100

10%

Network Requests Diagram

icr.co.jp

740 ms

import.css

671 ms

import.js

691 ms

jquery.bxslider.css

693 ms

jquery.bxslider.min.js

912 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 63% of them (49 requests) were addressed to the original Icr.co.jp, 27% (21 requests) were made to Google.com and 4% (3 requests) were made to Cse.google.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 349.3 kB (25%)

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Icr.co.jp main page is 1.4 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 964.7 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 26.9 kB

  • Original 36.0 kB
  • After minification 32.7 kB
  • After compression 9.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 26.9 kB or 75% of the original size.

Image Optimization

-5%

Potential reduce by 51.7 kB

  • Original 964.7 kB
  • After minification 913.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. ICR images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 216.9 kB

  • Original 342.8 kB
  • After minification 339.6 kB
  • After compression 125.9 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 216.9 kB or 63% of the original size.

CSS Optimization

-84%

Potential reduce by 53.8 kB

  • Original 64.3 kB
  • After minification 45.7 kB
  • After compression 10.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. Icr.co.jp needs all CSS files to be minified and compressed as it can save up to 53.8 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (53%)

Requests Now

74

After Optimization

35

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

icr.co.jp

icr.co.jp

740 ms

import.css

import.css

671 ms

import.js

import.js

691 ms

jquery.bxslider.css

jquery.bxslider.css

693 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

912 ms

default.css

default.css

168 ms

top.css

top.css

197 ms

style.css

style.css

548 ms

yahoo.css

yahoo.css

333 ms

sub_accordion.css

sub_accordion.css

366 ms

jquery.min.js

jquery.min.js

44 ms

analytics.js

analytics.js

177 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

703 ms

jquery.cookie.js

jquery.cookie.js

179 ms

textsize.js

textsize.js

194 ms

current.js

current.js

184 ms

icon_new_window.js

icon_new_window.js

218 ms

icon_pdf.js

icon_pdf.js

354 ms

jsapi

jsapi

39 ms

feed_info.js

feed_info.js

353 ms

feed_press.js

feed_press.js

365 ms

feed_press_ICTecon.js

feed_press_ICTecon.js

384 ms

feed_opinion.js

feed_opinion.js

393 ms

feed_NL.js

feed_NL.js

529 ms

feed_icrpr.js

feed_icrpr.js

529 ms

analytics.js

analytics.js

21 ms

track.js

track.js

311 ms

collect

collect

11 ms

collect

collect

53 ms

ga-audiences

ga-audiences

17 ms

14 ms

default+en.css

default+en.css

4 ms

default+en.I.js

default+en.I.js

7 ms

logo_ej_big.gif

logo_ej_big.gif

206 ms

size_s.jpg

size_s.jpg

335 ms

size_m.jpg

size_m.jpg

345 ms

size_b.jpg

size_b.jpg

354 ms

tBnr_WTR.png

tBnr_WTR.png

723 ms

tBnr_DP.png

tBnr_DP.png

740 ms

tBnr_ICT.png

tBnr_ICT.png

827 ms

tBnr_prof.png

tBnr_prof.png

1993 ms

thumb.png

thumb.png

684 ms

thumb_NL.png

thumb_NL.png

882 ms

thumb_ICT.png

thumb_ICT.png

1026 ms

thumb_DP.png

thumb_DP.png

1266 ms

thumb.png

thumb.png

924 ms

sBnr_IQS.png

sBnr_IQS.png

1222 ms

e_shimizu.png

e_shimizu.png

1060 ms

nakashima.jpg

nakashima.jpg

1110 ms

noguchi.jpg

noguchi.jpg

1198 ms

teshima.jpg

teshima.jpg

1236 ms

yamamoto.jpg

yamamoto.jpg

1294 ms

sato-y.png

sato-y.png

1538 ms

kubota.jpg

kubota.jpg

1420 ms

washio.jpg

washio.jpg

1412 ms

cse.js

cse.js

61 ms

navi_bg.png

navi_bg.png

192 ms

gNav_li_bg.png

gNav_li_bg.png

190 ms

cse.js

cse.js

66 ms

bx_loader.gif

bx_loader.gif

178 ms

controls.png

controls.png

192 ms

jsapi

jsapi

19 ms

default+ja.css

default+ja.css

6 ms

default.css

default.css

14 ms

default+ja.I.js

default+ja.I.js

13 ms

default.css

default.css

25 ms

async-ads.js

async-ads.js

67 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

33 ms

small-logo.png

small-logo.png

17 ms

search_box_icon.png

search_box_icon.png

16 ms

clear.png

clear.png

16 ms

nav_logo114.png

nav_logo114.png

10 ms

Gfeeds

Gfeeds

1244 ms

Gfeeds

Gfeeds

985 ms

Gfeeds

Gfeeds

1161 ms

Gfeeds

Gfeeds

800 ms

Gfeeds

Gfeeds

2313 ms

Gfeeds

Gfeeds

35 ms

Accessibility Review

icr.co.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

icr.co.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

icr.co.jp SEO score

100

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

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 Icr.co.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 Icr.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

icr.co.jp

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