Tools & Wizards About Us
i-inagi-support.org screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% 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

  • 100

    SEO

    Google-friendlier than
    94% of websites

i-inagi-support.org

特定非営利活動法人 市民活動サポートセンターいなぎ

Page Load Speed

5.6 sec in total

First Response

1.2 sec

Resources Loaded

4 sec

Page Rendered

434 ms

i-inagi-support.org screenshot

About Website

Visit i-inagi-support.org now to see the best up-to-date I Inagi Support content and also check out these interesting facts you probably never knew about i-inagi-support.org

市民活動を推進するための拠点施設となり、市民同士、市民活動団体同士がお互いに協力し、持てる力を出し合いながら稲城のまちづくりに貢献することを目指しています。また、稲城市地域振興プラザの指定管理者として地域振興プラザの施設管理も行なっています。

Visit i-inagi-support.org

Key Findings

We analyzed I-inagi-support.org page load time and found that the first response time was 1.2 sec and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

i-inagi-support.org performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value5.4 s

57/100

10%

TBT (Total Blocking Time)

Value500 ms

58/100

30%

CLS (Cumulative Layout Shift)

Value0.358

30/100

15%

TTI (Time to Interactive)

Value6.4 s

59/100

10%

Network Requests Diagram

i-inagi-support.org

1160 ms

style.css

350 ms

e7610eab4c.js

59 ms

js

13 ms

style.min.css

529 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 80% of them (36 requests) were addressed to the original I-inagi-support.org, 7% (3 requests) were made to Static.addtoany.com and 4% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain I-inagi-support.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 69.2 kB (5%)

Content Size

1.3 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of I-inagi-support.org main page is 1.3 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. 35% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 49.6 kB

  • Original 65.3 kB
  • After minification 63.6 kB
  • After compression 15.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. 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 49.6 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 14.4 kB

  • Original 1.1 MB
  • After minification 1.1 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. I Inagi Support images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.4 kB

  • Original 108.6 kB
  • After minification 108.6 kB
  • After compression 107.2 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. This website has mostly compressed JavaScripts.

CSS Optimization

-11%

Potential reduce by 3.7 kB

  • Original 35.2 kB
  • After minification 35.2 kB
  • After compression 31.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. I-inagi-support.org needs all CSS files to be minified and compressed as it can save up to 3.7 kB or 11% of the original size.

Requests Breakdown

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

Requests Now

43

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

i-inagi-support.org

i-inagi-support.org

1160 ms

style.css

style.css

350 ms

e7610eab4c.js

e7610eab4c.js

59 ms

js

js

13 ms

style.min.css

style.min.css

529 ms

addtoany.min.css

addtoany.min.css

375 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

373 ms

frontend-gtag.min.js

frontend-gtag.min.js

375 ms

page.js

page.js

40 ms

jquery.min.js

jquery.min.js

20 ms

addtoany.min.js

addtoany.min.js

376 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

701 ms

js

js

59 ms

flexslider.css

flexslider.css

356 ms

public.css

public.css

370 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

371 ms

script.min.js

script.min.js

370 ms

jQuery.easing.min.js

jQuery.easing.min.js

608 ms

nav_fixed.js

nav_fixed.js

607 ms

eso.BRQnzO8v.js

eso.BRQnzO8v.js

19 ms

embed

embed

217 ms

logo.png

logo.png

195 ms

mail.png

mail.png

194 ms

login.png

login.png

194 ms

slide_001-1400x500.jpg

slide_001-1400x500.jpg

1494 ms

7DMK9268-scaled-1400x500.jpg

7DMK9268-scaled-1400x500.jpg

1426 ms

fig_p21-851x303.jpg

fig_p21-851x303.jpg

1266 ms

bg_slash.png

bg_slash.png

367 ms

0b566b2b5465f5048e06c1b837f14492-2-pdf-709x600.jpg

0b566b2b5465f5048e06c1b837f14492-2-pdf-709x600.jpg

1266 ms

38614df11aeb8f6a446e5fd9c045d899-720x600.jpg

38614df11aeb8f6a446e5fd9c045d899-720x600.jpg

1448 ms

b383e1164f7882634e6b3fac9a00fdd5-800x600.jpg

b383e1164f7882634e6b3fac9a00fdd5-800x600.jpg

1621 ms

9e06dda3032d50cb772fd17f85cd64ce-2-720x600.jpg

9e06dda3032d50cb772fd17f85cd64ce-2-720x600.jpg

1791 ms

c37db02bd8e82029d0efad99129195c7-720x600.jpg

c37db02bd8e82029d0efad99129195c7-720x600.jpg

1792 ms

75311ded1a031ac8b9847b4160744bf5-2-720x600.jpg

75311ded1a031ac8b9847b4160744bf5-2-720x600.jpg

1773 ms

ico_shortcut_01.png

ico_shortcut_01.png

1625 ms

ico_shortcut_02.png

ico_shortcut_02.png

1657 ms

ico_shortcut_03.png

ico_shortcut_03.png

1796 ms

ico_shortcut_04.png

ico_shortcut_04.png

1802 ms

ico_shortcut_05.png

ico_shortcut_05.png

1822 ms

ico_shortcut_06.png

ico_shortcut_06.png

1947 ms

logo_footer.png

logo_footer.png

192 ms

sm.25.html

sm.25.html

20 ms

js

js

58 ms

mobile.css

mobile.css

177 ms

tablet.css

tablet.css

177 ms

Accessibility Review

i-inagi-support.org 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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

i-inagi-support.org 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

i-inagi-support.org 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 I-inagi-support.org 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 I-inagi-support.org 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

i-inagi-support.org

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