Tools & Wizards About Us
infocom-sb.jp screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

infocom-sb.jp

危機管理のＩＣＴソリューション（安否確認と情報共有）｜インフォコム株式会社

Page Load Speed

7.5 sec in total

First Response

570 ms

Resources Loaded

6.5 sec

Page Rendered

442 ms

infocom-sb.jp screenshot

About Website

Click here to check amazing Infocom Sb content for Japan. Otherwise, check out these important facts you probably never knew about infocom-sb.jp

危機対応において、安否確認システム「エマージェンシーコール」と情報共有とコミュニケーション支援システム「BCPortal」を組み合わせて利用することにより、事業継続計画（BCP）のスムーズな実行をICTを使って強力にサポートいたします。

Visit infocom-sb.jp

Key Findings

We analyzed Infocom-sb.jp page load time and found that the first response time was 570 ms and then it took 6.9 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

infocom-sb.jp performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

8/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value11.6 s

4/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value1.054

2/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

infocom-sb.jp

570 ms

www.infocom-sb.jp

1066 ms

gheader.css

480 ms

texts.css

365 ms

gbase.css

365 ms

Our browser made a total of 156 requests to load all elements on the main page. We found that 62% of them (97 requests) were addressed to the original Infocom-sb.jp, 19% (29 requests) were made to Static.xx.fbcdn.net and 6% (10 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Infocom-sb.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 243.5 kB (11%)

Content Size

2.2 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Infocom-sb.jp main page is 2.2 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. 65% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 48.7 kB

  • Original 61.4 kB
  • After minification 45.1 kB
  • After compression 12.7 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 16.3 kB, which is 27% 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 48.7 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 32.1 kB

  • Original 1.9 MB
  • After minification 1.9 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. Infocom Sb images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 114.5 kB

  • Original 193.2 kB
  • After minification 167.7 kB
  • After compression 78.7 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 114.5 kB or 59% of the original size.

CSS Optimization

-83%

Potential reduce by 48.2 kB

  • Original 58.2 kB
  • After minification 44.7 kB
  • After compression 10.0 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. Infocom-sb.jp needs all CSS files to be minified and compressed as it can save up to 48.2 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 66 (44%)

Requests Now

151

After Optimization

85

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

infocom-sb.jp

infocom-sb.jp

570 ms

www.infocom-sb.jp

www.infocom-sb.jp

1066 ms

gheader.css

gheader.css

480 ms

texts.css

texts.css

365 ms

gbase.css

gbase.css

365 ms

gsc.css

gsc.css

370 ms

common.css

common.css

561 ms

style.css

style.css

1086 ms

jcarousel.css

jcarousel.css

545 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

6 ms

base.js

base.js

551 ms

styleswitcher.js

styleswitcher.js

637 ms

jquery.jcarousel.min.js

jquery.jcarousel.min.js

645 ms

heightLine.js

heightLine.js

724 ms

jquery.lightpop-0.8.5.1.min.js

jquery.lightpop-0.8.5.1.min.js

917 ms

function.js

function.js

744 ms

jquery.cookie.js

jquery.cookie.js

794 ms

showcase.css

showcase.css

810 ms

jquery.aw-showcase.js

jquery.aw-showcase.js

1265 ms

gheader-logo.png

gheader-logo.png

167 ms

btn-size-big.png

btn-size-big.png

162 ms

btn-size-small.png

btn-size-small.png

209 ms

pic_logo.jpg

pic_logo.jpg

206 ms

gheader-tel.png

gheader-tel.png

207 ms

gheader-inquiry.png

gheader-inquiry.png

206 ms

gn_01-on.jpg

gn_01-on.jpg

320 ms

gn_02.jpg

gn_02.jpg

330 ms

gn_03.jpg

gn_03.jpg

368 ms

gn_04.jpg

gn_04.jpg

368 ms

gn_05.jpg

gn_05.jpg

371 ms

gn_06.jpg

gn_06.jpg

373 ms

main_01.jpg

main_01.jpg

1276 ms

main_10.jpg

main_10.jpg

987 ms

main_03.jpg

main_03.jpg

1133 ms

main_04.jpg

main_04.jpg

1273 ms

main_07.jpg

main_07.jpg

1104 ms

info.jpg

info.jpg

559 ms

pic_point1.png

pic_point1.png

934 ms

pic_point2.png

pic_point2.png

1309 ms

pic_point3.png

pic_point3.png

1151 ms

btn_inq_01.jpg

btn_inq_01.jpg

1287 ms

img_tel.gif

img_tel.gif

1313 ms

bnr_03.jpg

bnr_03.jpg

1316 ms

bnr_01.jpg

bnr_01.jpg

1460 ms

ttl_blog.gif

ttl_blog.gif

1433 ms

bnr_01.jpg

bnr_01.jpg

1469 ms

bnr_03.jpg

bnr_03.jpg

1502 ms

bnr_iso.jpg

bnr_iso.jpg

1499 ms

img_001.jpg

img_001.jpg

1479 ms

icon_cat_08.gif

icon_cat_08.gif

1591 ms

icon_cat_07.gif

icon_cat_07.gif

1633 ms

icon_cat_03.gif

icon_cat_03.gif

1652 ms

icon_cat_01.gif

icon_cat_01.gif

1643 ms

icon_cat_04.gif

icon_cat_04.gif

1673 ms

gtm.js

gtm.js

68 ms

icon_cat_02.gif

icon_cat_02.gif

1680 ms

all.js

all.js

163 ms

analytics.js

analytics.js

5 ms

cam2.js

cam2.js

1323 ms

conversion.js

conversion.js

19 ms

alog.js

alog.js

793 ms

collect

collect

15 ms

bcp_cycle.jpg

bcp_cycle.jpg

1600 ms

collect

collect

63 ms

bnr_43.jpg

bnr_43.jpg

1659 ms

bnr_40.png

bnr_40.png

1612 ms

bnr_34.jpg

bnr_34.jpg

1640 ms

ttl_news.gif

ttl_news.gif

1658 ms

141 ms

ttl_white.gif

ttl_white.gif

1666 ms

xd_arbiter.php

xd_arbiter.php

132 ms

xd_arbiter.php

xd_arbiter.php

353 ms

ga-audiences

ga-audiences

53 ms

ttl_user.gif

ttl_user.gif

1601 ms

pic_sys01.jpg

pic_sys01.jpg

1654 ms

pic_sys02.jpg

pic_sys02.jpg

1636 ms

txt_inq_01.gif

txt_inq_01.gif

1660 ms

txt_telinq.gif

txt_telinq.gif

1674 ms

txt_telNun.gif

txt_telNun.gif

1691 ms

txt_pcInq.gif

txt_pcInq.gif

1518 ms

btn_inq_07.jpg

btn_inq_07.jpg

1210 ms

footer_bnr01.gif

footer_bnr01.gif

1198 ms

footer_bnr02.gif

footer_bnr02.gif

1108 ms

footer_bnr03.gif

footer_bnr03.gif

1091 ms

footer_bnr04.gif

footer_bnr04.gif

1098 ms

footer_bnr05.gif

footer_bnr05.gif

966 ms

footer_bnr06.gif

footer_bnr06.gif

1037 ms

footer_bnr07.gif

footer_bnr07.gif

1079 ms

icon_arr_03.gif

icon_arr_03.gif

1086 ms

bg_inqBox_01.jpg

bg_inqBox_01.jpg

1090 ms

footer_sitemap_arrow.gif

footer_sitemap_arrow.gif

1080 ms

footer_sitemap_arrow2.gif

footer_sitemap_arrow2.gif

1002 ms

create_new_id_simple

create_new_id_simple

202 ms

gfooter-arrow.png

gfooter-arrow.png

1015 ms

btn-size-big-on.png

btn-size-big-on.png

1075 ms

btn-size-small-on.png

btn-size-small-on.png

1097 ms

gn_02-on.jpg

gn_02-on.jpg

1054 ms

gn_03-on.jpg

gn_03-on.jpg

1080 ms

gn_04-on.jpg

gn_04-on.jpg

1030 ms

gn_05-on.jpg

gn_05-on.jpg

1005 ms

gn_06-on.jpg

gn_06-on.jpg

1081 ms

btn_prev.gif

btn_prev.gif

1061 ms

btn_next.gif

btn_next.gif

1087 ms

img_movie.jpg

img_movie.jpg

1083 ms

img_movie2.jpg

img_movie2.jpg

1055 ms

lightpop-btn-prev.gif

lightpop-btn-prev.gif

1034 ms

btn_kvNext.png

btn_kvNext.png

1060 ms

btn_kvPrev.png

btn_kvPrev.png

1070 ms

bg_kvNavBtn_on.png

bg_kvNavBtn_on.png

1089 ms

bg_kvNavBtn.png

bg_kvNavBtn.png

1077 ms

textl.css

textl.css

167 ms

like.php

like.php

79 ms

like_box.php

like_box.php

296 ms

wy1X4hBW7e7.js

wy1X4hBW7e7.js

142 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

157 ms

wIQ5cz_qN26.css

wIQ5cz_qN26.css

23 ms

DrE_LqJc1gV.css

DrE_LqJc1gV.css

41 ms

rq28xVeqcvr.css

rq28xVeqcvr.css

57 ms

2qKTn8PrC5S.css

2qKTn8PrC5S.css

75 ms

R3qW8mZR52t.css

R3qW8mZR52t.css

69 ms

6AlVa5wn0Ie.css

6AlVa5wn0Ie.css

56 ms

SKUMZfeWCs6.css

SKUMZfeWCs6.css

58 ms

ErRlNvwvHFA.css

ErRlNvwvHFA.css

60 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

89 ms

ehA1CqzHyzE.js

ehA1CqzHyzE.js

149 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

80 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

86 ms

njO1TPvGzoR.js

njO1TPvGzoR.js

102 ms

1QuX41zDRrx.js

1QuX41zDRrx.js

102 ms

Oagsvfb4VWi.js

Oagsvfb4VWi.js

105 ms

LTv6ZK-5zxz.js

LTv6ZK-5zxz.js

130 ms

1FCa-btixu2.js

1FCa-btixu2.js

106 ms

DVtj8v6ogQI.js

DVtj8v6ogQI.js

107 ms

IjqSyiwKeaX.js

IjqSyiwKeaX.js

107 ms

n6VgtouijQL.js

n6VgtouijQL.js

125 ms

1450780_243464115808114_68562796_n.jpg

1450780_243464115808114_68562796_n.jpg

152 ms

safe_image.php

safe_image.php

185 ms

95 ms

safe_image.php

safe_image.php

86 ms

safe_image.php

safe_image.php

63 ms

1455058_243264839161375_391369186_n.png

1455058_243264839161375_391369186_n.png

50 ms

11350709_389243441278451_1615449910919544187_n.jpg

11350709_389243441278451_1615449910919544187_n.jpg

67 ms

486706_106971842791141_1551098687_n.jpg

486706_106971842791141_1551098687_n.jpg

70 ms

12036818_431376833735148_5620299029687426989_n.jpg

12036818_431376833735148_5620299029687426989_n.jpg

94 ms

182987_171837029529273_7104861_n.jpg

182987_171837029529273_7104861_n.jpg

67 ms

10628377_316226328561815_3281595152438243915_n.jpg

10628377_316226328561815_3281595152438243915_n.jpg

69 ms

1455058_243264839161375_391369186_n.png

1455058_243264839161375_391369186_n.png

107 ms

1525003_787359897950808_6371552707439285915_n.jpg

1525003_787359897950808_6371552707439285915_n.jpg

104 ms

5947_563475743672559_1074184425_n.jpg

5947_563475743672559_1074184425_n.jpg

121 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

33 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

34 ms

QDwYpIaRyfG.png

QDwYpIaRyfG.png

31 ms

K00K-UgnsKu.png

K00K-UgnsKu.png

34 ms

MiXXTBbOQzg.png

MiXXTBbOQzg.png

36 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

19 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

37 ms

Accessibility Review

infocom-sb.jp accessibility score

83

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

Links do not have a discernible name

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

infocom-sb.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

SEO Factors

infocom-sb.jp SEO score

90

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

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

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Infocom-sb.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 Infocom-sb.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

infocom-sb.jp

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