Tools & Wizards About Us
supporter.jica.go.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

supporter.jica.go.jp

サポーター宣言　グローバル人材・CSR・BOPビジネスの可能性 - JICA海外協力隊

Page Load Speed

7.4 sec in total

First Response

663 ms

Resources Loaded

6.5 sec

Page Rendered

239 ms

supporter.jica.go.jp screenshot

About Website

Click here to check amazing Supporter Jica content for Japan. Otherwise, check out these important facts you probably never knew about supporter.jica.go.jp

企業や団体、自治体、教育機関等の皆様に青年海外協力隊をはじめとしたJICAボランティア事業をご支援いただくとともに、 JICAボランティア事業をそれぞれのご活動に有益なものとして積極的に役立てていただけるよう、様々な連携事例をご紹介するサイトです。

Visit supporter.jica.go.jp

Key Findings

We analyzed Supporter.jica.go.jp page load time and found that the first response time was 663 ms and then it took 6.8 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

supporter.jica.go.jp performance score

0

Network Requests Diagram

supporter.jica.go.jp

663 ms

reset.css

326 ms

common.css

338 ms

index.css

383 ms

jquery.fancybox-1.3.4.css

383 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 97% of them (66 requests) were addressed to the original Supporter.jica.go.jp, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Supporter.jica.go.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 170.8 kB (17%)

Content Size

986.6 kB

After Optimization

815.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Supporter.jica.go.jp main page is 986.6 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. 20% of websites need less resources to load. Images take 749.1 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 14.9 kB

  • Original 20.0 kB
  • After minification 17.5 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 2.5 kB, which is 13% 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 14.9 kB or 75% of the original size.

Image Optimization

-1%

Potential reduce by 10.7 kB

  • Original 749.1 kB
  • After minification 738.4 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. Supporter Jica images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 126.2 kB

  • Original 193.8 kB
  • After minification 188.7 kB
  • After compression 67.6 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 126.2 kB or 65% of the original size.

CSS Optimization

-80%

Potential reduce by 19.1 kB

  • Original 23.7 kB
  • After minification 17.2 kB
  • After compression 4.6 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. Supporter.jica.go.jp needs all CSS files to be minified and compressed as it can save up to 19.1 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (42%)

Requests Now

67

After Optimization

39

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

supporter.jica.go.jp

supporter.jica.go.jp

663 ms

reset.css

reset.css

326 ms

common.css

common.css

338 ms

index.css

index.css

383 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

383 ms

jquery.bxslider.css

jquery.bxslider.css

400 ms

jquery.js

jquery.js

1362 ms

jquery.cookie.js

jquery.cookie.js

695 ms

rollover.js

rollover.js

712 ms

pagetop.js

pagetop.js

739 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

955 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

962 ms

tab.js

tab.js

1093 ms

search-index.js

search-index.js

1079 ms

analytics.js

analytics.js

56 ms

logo.gif

logo.gif

172 ms

nav_top_on.png

nav_top_on.png

325 ms

nav_about.png

nav_about.png

341 ms

nav_company.png

nav_company.png

357 ms

nav_celebrity.png

nav_celebrity.png

369 ms

nav_material.png

nav_material.png

370 ms

btn_Volunteer.gif

btn_Volunteer.gif

539 ms

main_01.jpg

main_01.jpg

2099 ms

main_02.jpg

main_02.jpg

2025 ms

main_03.jpg

main_03.jpg

1597 ms

ttl_supporter_on.gif

ttl_supporter_on.gif

706 ms

ttl_celebrity_off.gif

ttl_celebrity_off.gif

767 ms

bg.gif

bg.gif

918 ms

ttl_case.gif

ttl_case.gif

1104 ms

btn_info.gif

btn_info.gif

1123 ms

ttl_org.gif

ttl_org.gif

1255 ms

btn_search.gif

btn_search.gif

1459 ms

arrow.gif

arrow.gif

1489 ms

ic_new.gif

ic_new.gif

1641 ms

ic_volunteer.gif

ic_volunteer.gif

1826 ms

logo.gif

logo.gif

1888 ms

logo.gif

logo.gif

1964 ms

logo.gif

logo.gif

2039 ms

logo.gif

logo.gif

2194 ms

logo.gif

logo.gif

2269 ms

logo.gif

logo.gif

2332 ms

logo.gif

logo.gif

2358 ms

logo.gif

logo.gif

2423 ms

logo.gif

logo.gif

2419 ms

logo.png

logo.png

2516 ms

logo.png

logo.png

2666 ms

logo2.png

logo2.png

2716 ms

supporter_list.gif

supporter_list.gif

2738 ms

pickup.png

pickup.png

2799 ms

photo1.png

photo1.png

4017 ms

celebrity_list.gif

celebrity_list.gif

2900 ms

collect

collect

26 ms

top.png

top.png

2902 ms

copy.gif

copy.gif

2722 ms

jica.jpg

jica.jpg

2805 ms

young.jpg

young.jpg

2805 ms

senior.jpg

senior.jpg

2909 ms

disk_off.png

disk_off.png

3078 ms

btn_left.png

btn_left.png

2919 ms

btn_right.png

btn_right.png

2807 ms

disk_on.png

disk_on.png

1419 ms

nav_about_on.png

nav_about_on.png

195 ms

nav_company_on.png

nav_company_on.png

339 ms

nav_celebrity_on.png

nav_celebrity_on.png

339 ms

nav_material_on.png

nav_material_on.png

383 ms

btn_Volunteer_on.gif

btn_Volunteer_on.gif

386 ms

btn_search_on.gif

btn_search_on.gif

428 ms

celebrity_list_on.gif

celebrity_list_on.gif

579 ms

SEO Factors

supporter.jica.go.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

supporter.jica.go.jp

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