Tools & Wizards About Us
iic-hq.co.jp screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

iic-hq.co.jp

株式会社IHI検査計測（IIC）

Page Load Speed

11.7 sec in total

First Response

518 ms

Resources Loaded

10.3 sec

Page Rendered

967 ms

iic-hq.co.jp screenshot

About Website

Click here to check amazing IIC Hq content for Japan. Otherwise, check out these important facts you probably never knew about iic-hq.co.jp

IHI検査計測（IIC）は、時代に対応した最先端の検査・計測・システム技術で製品開発をトータルに支援。社会の安心・安全に貢献します。

Visit iic-hq.co.jp

Key Findings

We analyzed Iic-hq.co.jp page load time and found that the first response time was 518 ms and then it took 11.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

iic-hq.co.jp performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

3/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value600 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

iic-hq.co.jp

518 ms

www.iic-hq.co.jp

829 ms

main.css

661 ms

global.css

504 ms

page.css

520 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 97% of them (60 requests) were addressed to the original Iic-hq.co.jp, 2% (1 request) were made to Googletagmanager.com and 2% (1 request) were made to Go.ihi.co.jp. The less responsive or slowest element that took the longest time to load (5.7 sec) belongs to the original domain Iic-hq.co.jp.

Page Optimization Overview & Recommendations

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

Content Size

1.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 37.0 kB

  • Original 44.3 kB
  • After minification 33.4 kB
  • After compression 7.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 10.9 kB, which is 25% 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 37.0 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 6.9 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. IIC Hq images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 16.7 kB

  • Original 80.6 kB
  • After minification 80.6 kB
  • After compression 63.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 16.7 kB or 21% of the original size.

CSS Optimization

-33%

Potential reduce by 20.1 kB

  • Original 60.6 kB
  • After minification 60.6 kB
  • After compression 40.4 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. Iic-hq.co.jp needs all CSS files to be minified and compressed as it can save up to 20.1 kB or 33% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (29%)

Requests Now

52

After Optimization

37

  • Images
  • JavaScript
  • CSS

The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IIC Hq. 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

iic-hq.co.jp

iic-hq.co.jp

518 ms

www.iic-hq.co.jp

www.iic-hq.co.jp

829 ms

main.css

main.css

661 ms

global.css

global.css

504 ms

page.css

page.css

520 ms

common2024.css

common2024.css

695 ms

index2024.css

index2024.css

539 ms

lib.js

lib.js

1071 ms

main_new.js

main_new.js

1052 ms

c24.js

c24.js

1061 ms

gtm.js

gtm.js

226 ms

ico_04_blue.svg

ico_04_blue.svg

488 ms

logo_01.svg

logo_01.svg

819 ms

logo_01_white.svg

logo_01_white.svg

843 ms

fig_header_01_sp.png

fig_header_01_sp.png

977 ms

ico_04.svg

ico_04.svg

837 ms

ico_03.svg

ico_03.svg

850 ms

logo_02.svg

logo_02.svg

992 ms

logo_02_white.svg

logo_02_white.svg

1329 ms

pic_slider_01_sp.jpg_sp.jpg

pic_slider_01_sp.jpg_sp.jpg

1495 ms

pic_slider_02_sp.jpg_sp.jpg

pic_slider_02_sp.jpg_sp.jpg

1499 ms

pic_about_01.jpg

pic_about_01.jpg

1696 ms

arrow_02.svg

arrow_02.svg

1482 ms

arrow_03.svg

arrow_03.svg

1519 ms

pic_about_02.jpg

pic_about_02.jpg

2040 ms

pic_pick_01.jpg

pic_pick_01.jpg

2667 ms

pic_pick_02.jpg

pic_pick_02.jpg

2507 ms

pic_pick_04.jpg

pic_pick_04.jpg

2548 ms

pic_pick_08.jpg

pic_pick_08.jpg

2539 ms

pic_pick_05.jpg

pic_pick_05.jpg

2699 ms

pic_pick_06.jpg

pic_pick_06.jpg

2904 ms

pic_01.jpg

pic_01.jpg

3177 ms

pic_02.jpg

pic_02.jpg

3212 ms

pic_03.jpg

pic_03.jpg

3233 ms

pic_04.jpg

pic_04.jpg

3336 ms

pic_05.jpg

pic_05.jpg

3370 ms

pic_07.jpg

pic_07.jpg

3608 ms

pic_08.jpg

pic_08.jpg

3856 ms

pic_09.jpg

pic_09.jpg

3906 ms

pic_10.jpg

pic_10.jpg

3904 ms

pic_11.jpg

pic_11.jpg

4176 ms

pic_12.jpg

pic_12.jpg

4060 ms

pic_16.jpg

pic_16.jpg

4265 ms

pic_13.jpg

pic_13.jpg

4348 ms

RobotoCondensed-Bold.ttf

RobotoCondensed-Bold.ttf

4697 ms

RobotoCondensed-Medium.ttf

RobotoCondensed-Medium.ttf

4747 ms

RobotoCondensed-Regular.ttf

RobotoCondensed-Regular.ttf

4944 ms

NotoSerifCJKjp-Bold_sub.woff

NotoSerifCJKjp-Bold_sub.woff

5658 ms

NotoSerifCJKjp-Medium_sub.woff

NotoSerifCJKjp-Medium_sub.woff

5647 ms

NotoSerifCJKjp-Regular_sub.woff

NotoSerifCJKjp-Regular_sub.woff

5581 ms

pic_14.jpg

pic_14.jpg

4862 ms

pic_lib_01.jpg

pic_lib_01.jpg

5428 ms

pic_rec_01.jpg

pic_rec_01.jpg

5468 ms

bnr_01.jpg

bnr_01.jpg

5404 ms

bnr_02.jpg

bnr_02.jpg

5481 ms

bnr_03.jpg

bnr_03.jpg

5497 ms

ico_01.svg

ico_01.svg

5412 ms

ico_02.png

ico_02.png

5430 ms

pagetop.svg

pagetop.svg

5428 ms

print.css

print.css

488 ms

print_new.css

print_new.css

523 ms

pd.js

pd.js

187 ms

Accessibility Review

iic-hq.co.jp accessibility score

79

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

iic-hq.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

High

Page has valid source maps

SEO Factors

iic-hq.co.jp SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    JA

  • Encoding

    UTF-8

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

iic-hq.co.jp

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