Tools & Wizards About Us
fgda.or.jp screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 47

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

fgda.or.jp

公益財団法人 九州盲導犬協会

Page Load Speed

5.7 sec in total

First Response

512 ms

Resources Loaded

4.7 sec

Page Rendered

440 ms

fgda.or.jp screenshot

About Website

Visit fgda.or.jp now to see the best up-to-date Fgda content and also check out these interesting facts you probably never knew about fgda.or.jp

公益財団法人 九州盲導犬協会の公式ホームページ

Visit fgda.or.jp

Key Findings

We analyzed Fgda.or.jp page load time and found that the first response time was 512 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

fgda.or.jp performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value14.0 s

0/100

25%

SI (Speed Index)

Value7.3 s

28/100

10%

TBT (Total Blocking Time)

Value260 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value1.093

1/100

15%

TTI (Time to Interactive)

Value7.7 s

46/100

10%

Network Requests Diagram

fgda.or.jp

512 ms

styleswitcher.js

160 ms

smooth.pack.js

331 ms

seltab.js

333 ms

jquery.min.js

9 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 96% of them (79 requests) were addressed to the original Fgda.or.jp, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Fgda.or.jp.

Page Optimization Overview & Recommendations

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

Content Size

1.8 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fgda.or.jp main page is 1.8 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.7 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 37.6 kB

  • Original 45.6 kB
  • After minification 42.0 kB
  • After compression 8.0 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 37.6 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 19.4 kB

  • Original 1.7 MB
  • After minification 1.7 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. Fgda images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 14.7 kB

  • Original 41.5 kB
  • After minification 40.1 kB
  • After compression 26.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 14.7 kB or 35% of the original size.

CSS Optimization

-81%

Potential reduce by 12.2 kB

  • Original 15.1 kB
  • After minification 11.3 kB
  • After compression 2.9 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. Fgda.or.jp needs all CSS files to be minified and compressed as it can save up to 12.2 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (10%)

Requests Now

81

After Optimization

73

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fgda.or.jp

fgda.or.jp

512 ms

styleswitcher.js

styleswitcher.js

160 ms

smooth.pack.js

smooth.pack.js

331 ms

seltab.js

seltab.js

333 ms

jquery.min.js

jquery.min.js

9 ms

jquery.jcarousel.min.js

jquery.jcarousel.min.js

478 ms

top.css

top.css

351 ms

skin.css

skin.css

367 ms

body_back.gif

body_back.gif

176 ms

id.gif

id.gif

361 ms

header_access.gif

header_access.gif

165 ms

header_policy.gif

header_policy.gif

181 ms

header_form.gif

header_form.gif

172 ms

header_text.gif

header_text.gif

164 ms

header_font.gif

header_font.gif

328 ms

icon_small.png

icon_small.png

338 ms

icon_big.png

icon_big.png

341 ms

navi_back.gif

navi_back.gif

332 ms

mainimg.jpg

mainimg.jpg

2173 ms

mainimg2.jpg

mainimg2.jpg

2059 ms

mainimg3.jpg

mainimg3.jpg

1417 ms

mainimg4.jpg

mainimg4.jpg

2273 ms

toph3iten.gif

toph3iten.gif

560 ms

top_iten.gif

top_iten.gif

923 ms

toph3.gif

toph3.gif

742 ms

top_newstitle.gif

top_newstitle.gif

1089 ms

news_back.gif

news_back.gif

1108 ms

top_tabheader.gif

top_tabheader.gif

1259 ms

news_line.gif

news_line.gif

1306 ms

icon_new.gif

icon_new.gif

1470 ms

news_icon.gif

news_icon.gif

1491 ms

icon_topics.gif

icon_topics.gif

1613 ms

news_back_bottom.gif

news_back_bottom.gif

1639 ms

top_topics1.gif

top_topics1.gif

1699 ms

top_topics2.jpg

top_topics2.jpg

1772 ms

top_topics3.gif

top_topics3.gif

1972 ms

top_panel1.jpg

top_panel1.jpg

2248 ms

pagetop.gif

pagetop.gif

1930 ms

right_volunteer.gif

right_volunteer.gif

2088 ms

right_center.gif

right_center.gif

2306 ms

righth3menu.gif

righth3menu.gif

2216 ms

menu_back_bottom.gif

menu_back_bottom.gif

2245 ms

righth3link.gif

righth3link.gif

2345 ms

link_rkb.gif

link_rkb.gif

2348 ms

analytics.js

analytics.js

22 ms

collect

collect

33 ms

link_volunteer.jpg

link_volunteer.jpg

2246 ms

gallary_img1.jpg

gallary_img1.jpg

2272 ms

gallary_img2.jpg

gallary_img2.jpg

2267 ms

gallary_img3.jpg

gallary_img3.jpg

2311 ms

gallary_img4.jpg

gallary_img4.jpg

2360 ms

gallary_img5.jpg

gallary_img5.jpg

2220 ms

gallary_img6.jpg

gallary_img6.jpg

2238 ms

gallary_img7.jpg

gallary_img7.jpg

2298 ms

gallary_img8.jpg

gallary_img8.jpg

2261 ms

gallary_img9.jpg

gallary_img9.jpg

2296 ms

gallary_img10.jpg

gallary_img10.jpg

2159 ms

gallary_img11.jpg

gallary_img11.jpg

1971 ms

gallary_img12.jpg

gallary_img12.jpg

1806 ms

gallary_img13.jpg

gallary_img13.jpg

1676 ms

gallary_img14.jpg

gallary_img14.jpg

1718 ms

footerh4home.gif

footerh4home.gif

1564 ms

footerh4user.gif

footerh4user.gif

1568 ms

footerh4about.gif

footerh4about.gif

1498 ms

footerh4qa.gif

footerh4qa.gif

1415 ms

footerh4guidedog.gif

footerh4guidedog.gif

1447 ms

footerh4donation.gif

footerh4donation.gif

1379 ms

footerh4volunteer.gif

footerh4volunteer.gif

1384 ms

footer_other.gif

footer_other.gif

1336 ms

toph3_2.gif

toph3_2.gif

1272 ms

toph3_3.gif

toph3_3.gif

1175 ms

righth2.gif

righth2.gif

1133 ms

menu_back.gif

menu_back.gif

1110 ms

menu_base.gif

menu_base.gif

1115 ms

footer_wrap.gif

footer_wrap.gif

1030 ms

footer_back.gif

footer_back.gif

985 ms

top_news_head1.gif

top_news_head1.gif

1040 ms

top_news_head2.gif

top_news_head2.gif

1023 ms

footer_slide_prev.gif

footer_slide_prev.gif

1065 ms

footer_slide_next.gif

footer_slide_next.gif

1054 ms

change.css

change.css

162 ms

big.css

big.css

159 ms

Accessibility Review

fgda.or.jp accessibility score

47

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

fgda.or.jp best practices score

67

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

fgda.or.jp SEO score

85

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

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 Fgda.or.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 Fgda.or.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

fgda.or.jp

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