Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

janic.org

NGOの力を最大化する。JANIC

Page Load Speed

11.8 sec in total

First Response

518 ms

Resources Loaded

11 sec

Page Rendered

285 ms

janic.org screenshot

About Website

Visit janic.org now to see the best up-to-date JANIC content for Japan and also check out these interesting facts you probably never knew about janic.org

国際協力NGOを支援する、日本最大のネットワーク型NGO。 社会課題解決のためにNGOの力を最大化することを目標に掲げ、NGOへの能力強化支援や提言活動を行っている。

Visit janic.org

Key Findings

We analyzed Janic.org page load time and found that the first response time was 518 ms and then it took 11.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

janic.org performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

20/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value14.4 s

1/100

10%

TBT (Total Blocking Time)

Value1,730 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value22.5 s

1/100

10%

Network Requests Diagram

janic.org

518 ms

www.janic.org

1673 ms

gtm.js

74 ms

wp-emoji-release.min.js

193 ms

style.min.css

358 ms

Our browser made a total of 205 requests to load all elements on the main page. We found that 85% of them (175 requests) were addressed to the original Janic.org, 6% (12 requests) were made to Static.xx.fbcdn.net and 2% (4 requests) were made to S.w.org. The less responsive or slowest element that took the longest time to load (7.3 sec) belongs to the original domain Janic.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 362.6 kB (13%)

Content Size

2.7 MB

After Optimization

2.4 MB

In fact, the total size of Janic.org main page is 2.7 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. 70% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 158.7 kB

  • Original 189.2 kB
  • After minification 156.2 kB
  • After compression 30.5 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 33.1 kB, which is 17% 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 158.7 kB or 84% of the original size.

Image Optimization

-7%

Potential reduce by 161.9 kB

  • Original 2.3 MB
  • After minification 2.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. JANIC images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 22.8 kB

  • Original 172.3 kB
  • After minification 172.1 kB
  • After compression 149.4 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 22.8 kB or 13% of the original size.

CSS Optimization

-35%

Potential reduce by 19.2 kB

  • Original 54.1 kB
  • After minification 54.0 kB
  • After compression 34.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. Janic.org needs all CSS files to be minified and compressed as it can save up to 19.2 kB or 35% of the original size.

Requests Breakdown

Number of requests can be reduced by 50 (25%)

Requests Now

203

After Optimization

153

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

Accessibility Review

janic.org accessibility score

95

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

janic.org best practices score

58

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

Displays images with incorrect aspect ratio

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

janic.org SEO score

77

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

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

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 Janic.org 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 Janic.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

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