Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 94

    SEO

    Google-friendlier than
    90% of websites

jsbc.or.jp

一般社団法人 日本サステナブル建築協会(JSBC)

Page Load Speed

1.2 sec in total

First Response

548 ms

Resources Loaded

560 ms

Page Rendered

59 ms

About Website

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

一般社団法人日本サステナブル建築協会(JSBC)のウェブサイトです。

Visit jsbc.or.jp

Key Findings

We analyzed Jsbc.or.jp page load time and found that the first response time was 548 ms and then it took 619 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

jsbc.or.jp performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.0 s

100/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value690 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value5.1 s

76/100

10%

Network Requests Diagram

jsbc.or.jp

548 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Jsbc.or.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (548 ms) belongs to the original domain Jsbc.or.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 64.9 kB (55%)

Content Size

118.8 kB

After Optimization

53.9 kB

In fact, the total size of Jsbc.or.jp main page is 118.8 kB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Javascripts take 63.8 kB which makes up the majority of the site volume.

HTML Optimization

-26%

Potential reduce by 84 B

  • Original 325 B
  • After minification 323 B
  • After compression 241 B

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 84 B or 26% of the original size.

Image Optimization

-6%

Potential reduce by 818 B

  • Original 14.6 kB
  • After minification 13.7 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. JSBC images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 29.6 kB

  • Original 63.8 kB
  • After minification 55.9 kB
  • After compression 34.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 29.6 kB or 46% of the original size.

CSS Optimization

-86%

Potential reduce by 34.4 kB

  • Original 40.1 kB
  • After minification 18.2 kB
  • After compression 5.7 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. Jsbc.or.jp needs all CSS files to be minified and compressed as it can save up to 34.4 kB or 86% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

jsbc.or.jp accessibility score

90

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

jsbc.or.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

jsbc.or.jp SEO score

94

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

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 Jsbc.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 Jsbc.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

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