Tools & Wizards About Us
designcommittee.jp screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

designcommittee.jp

日本デザインコミッティー

Page Load Speed

5.1 sec in total

First Response

524 ms

Resources Loaded

4.2 sec

Page Rendered

426 ms

designcommittee.jp screenshot

About Website

Welcome to designcommittee.jp homepage info - get ready to check Designcommittee best content for Japan right away, or after learning these important things about designcommittee.jp

日本デザインコミッティーは「グッドデザインの啓蒙」を目的に設立されました。松屋銀座での活動を中心として、様々なグッドデザイン運動を展開しています。

Visit designcommittee.jp

Key Findings

We analyzed Designcommittee.jp page load time and found that the first response time was 524 ms and then it took 4.6 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

designcommittee.jp performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.8 s

0/100

25%

SI (Speed Index)

Value13.0 s

2/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.7 s

14/100

10%

Network Requests Diagram

designcommittee.jp

524 ms

designcommittee.jp

1211 ms

js

70 ms

font_ja.css

173 ms

style.css

346 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 58% of them (22 requests) were addressed to the original Designcommittee.jp, 21% (8 requests) were made to Fonts.gstatic.com and 11% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Designcommittee.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 33.5 kB (2%)

Content Size

1.5 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Designcommittee.jp main page is 1.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 28.9 kB

  • Original 36.2 kB
  • After minification 35.4 kB
  • After compression 7.3 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 28.9 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 2.9 kB

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

JavaScript Optimization

-2%

Potential reduce by 856 B

  • Original 52.0 kB
  • After minification 52.0 kB
  • After compression 51.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

-10%

Potential reduce by 759 B

  • Original 7.6 kB
  • After minification 7.6 kB
  • After compression 6.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. Designcommittee.jp has all CSS files already compressed.

Requests Breakdown

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

Requests Now

28

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Designcommittee. 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

designcommittee.jp

designcommittee.jp

524 ms

designcommittee.jp

designcommittee.jp

1211 ms

js

js

70 ms

font_ja.css

font_ja.css

173 ms

style.css

style.css

346 ms

home.css

home.css

520 ms

jquery.min.js

jquery.min.js

845 ms

vendor.js

vendor.js

836 ms

site.js

site.js

670 ms

widgets.js

widgets.js

162 ms

css2

css2

39 ms

home_w.svg

home_w.svg

178 ms

jdc_bk_1l.svg

jdc_bk_1l.svg

175 ms

dg_logo_w.svg

dg_logo_w.svg

180 ms

grey_pc.gif

grey_pc.gif

197 ms

grey.gif

grey.gif

189 ms

main01_pc.jpg

main01_pc.jpg

1160 ms

designcollection_w.svg

designcollection_w.svg

361 ms

main02_pc.jpg

main02_pc.jpg

1186 ms

main03_pc.jpg

main03_pc.jpg

1007 ms

main04_pc.jpg

main04_pc.jpg

1258 ms

i_twitter.png

i_twitter.png

384 ms

i_instagram.png

i_instagram.png

557 ms

home_bk.svg

home_bk.svg

492 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

56 ms

xn77YHs72GKoTvER4Gn3b5eMZGKLRkg.otf

xn77YHs72GKoTvER4Gn3b5eMZGKLRkg.otf

116 ms

xn77YHs72GKoTvER4Gn3b5eMZCqNRkg.otf

xn77YHs72GKoTvER4Gn3b5eMZCqNRkg.otf

563 ms

xn7mYHs72GKoTvER4Gn3b5eMXNg.otf

xn7mYHs72GKoTvER4Gn3b5eMXNg.otf

585 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEi75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEi75s.ttf

493 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j75s.ttf

505 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf

505 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75s.ttf

548 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf

607 ms

settings

settings

90 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

37 ms

dg788_pctop.jpg

dg788_pctop.jpg

1294 ms

embeds

embeds

54 ms

follow_button.2f70fb173b9000da126c79afe2098f02.ja.html

follow_button.2f70fb173b9000da126c79afe2098f02.ja.html

52 ms

Accessibility Review

designcommittee.jp 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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

designcommittee.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

designcommittee.jp SEO score

99

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

designcommittee.jp

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