Tools & Wizards About Us
big-i.jp screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

big-i.jp

Home　|　国際障害者交流センター（ビッグ・アイ）

Page Load Speed

8.4 sec in total

First Response

1.5 sec

Resources Loaded

6.7 sec

Page Rendered

184 ms

big-i.jp screenshot

About Website

Welcome to big-i.jp homepage info - get ready to check Big I best content for Japan right away, or after learning these important things about big-i.jp

国際障害者交流センター（ビッグ・アイ）は、障がいのある方も、ない方も、すべての人にご利用いただける施設です。障がい者が主役の芸術・文化・国際交流活動の機会を創出し、障がい者の社会参加促進をめざします。施設内には、多目的ホールや研修室、宿泊室、レストランを備えています。

Visit big-i.jp

Key Findings

We analyzed Big-i.jp page load time and found that the first response time was 1.5 sec 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

big-i.jp performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

6/100

25%

SI (Speed Index)

Value30.8 s

0/100

10%

TBT (Total Blocking Time)

Value1,700 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value60.8 s

0/100

10%

Network Requests Diagram

big-i.jp

1508 ms

wincfg.css

752 ms

maccfg.js

378 ms

fontswitcher.js

378 ms

bytefx.js

987 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 98% of them (47 requests) were addressed to the original Big-i.jp, 2% (1 request) were made to Cse.google.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Big-i.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 250.3 kB (50%)

Content Size

504.3 kB

After Optimization

254.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Big-i.jp main page is 504.3 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. 15% of websites need less resources to load. Javascripts take 267.6 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 14.6 kB

  • Original 18.7 kB
  • After minification 17.7 kB
  • After compression 4.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 14.6 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 5.7 kB

  • Original 205.7 kB
  • After minification 200.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. Big I images are well optimized though.

JavaScript Optimization

-82%

Potential reduce by 220.7 kB

  • Original 267.6 kB
  • After minification 159.9 kB
  • After compression 46.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 220.7 kB or 82% of the original size.

CSS Optimization

-75%

Potential reduce by 9.3 kB

  • Original 12.3 kB
  • After minification 8.5 kB
  • After compression 3.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. Big-i.jp needs all CSS files to be minified and compressed as it can save up to 9.3 kB or 75% of the original size.

Requests Breakdown

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

Requests Now

47

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

big-i.jp

big-i.jp

1508 ms

wincfg.css

wincfg.css

752 ms

maccfg.js

maccfg.js

378 ms

fontswitcher.js

fontswitcher.js

378 ms

bytefx.js

bytefx.js

987 ms

jquery.js

jquery.js

2027 ms

fixHeight.js

fixHeight.js

786 ms

jquery.cookie.js

jquery.cookie.js

786 ms

ui.core.js

ui.core.js

608 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

811 ms

cfg.css

cfg.css

936 ms

jquery.belatedPNG.min.js

jquery.belatedPNG.min.js

1157 ms

home_float.js

home_float.js

971 ms

google_brand.js

google_brand.js

814 ms

styleswitcher.js

styleswitcher.js

372 ms

hdr_line.gif

hdr_line.gif

201 ms

hdr_logo.gif

hdr_logo.gif

197 ms

arw.gif

arw.gif

189 ms

140421_bigi_facebook.gif

140421_bigi_facebook.gif

187 ms

130809_bigi_yoyaku.gif

130809_bigi_yoyaku.gif

187 ms

hdr_search_btn.gif

hdr_search_btn.gif

202 ms

hdr_zize_tt.gif

hdr_zize_tt.gif

370 ms

home_btn_logo.gif

home_btn_logo.gif

370 ms

home_btn_1.gif

home_btn_1.gif

370 ms

home_btn_2.gif

home_btn_2.gif

390 ms

home_btn_3.gif

home_btn_3.gif

398 ms

home_tpc_bg_btn.gif

home_tpc_bg_btn.gif

413 ms

arw2.gif

arw2.gif

554 ms

home_copy.gif

home_copy.gif

553 ms

report_ban.gif

report_ban.gif

553 ms

hdr_font_nv.gif

hdr_font_nv.gif

515 ms

hdr_gnv.gif

hdr_gnv.gif

531 ms

home_bg.jpg

home_bg.jpg

732 ms

home_float_bg.png

home_float_bg.png

667 ms

dummy.gif

dummy.gif

668 ms

viewimg.php

viewimg.php

1103 ms

viewimg.php

viewimg.php

837 ms

viewimg.php

viewimg.php

1021 ms

viewimg.php

viewimg.php

1115 ms

viewimg.php

viewimg.php

1118 ms

viewimg.php

viewimg.php

2267 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

27 ms

font_win_small.css

font_win_small.css

202 ms

font_win_normal.css

font_win_normal.css

202 ms

font_win_large.css

font_win_large.css

204 ms

font_mac_small.css

font_mac_small.css

205 ms

font_mac_normal.css

font_mac_normal.css

207 ms

font_mac_large.css

font_mac_large.css

208 ms

Accessibility Review

big-i.jp accessibility score

93

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

big-i.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

SEO Factors

big-i.jp SEO score

75

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

High

robots.txt is not valid

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 doesn't use 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 Big-i.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 Big-i.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

big-i.jp

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