Tools & Wizards About Us
indesign.jp screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 62

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

indesign.jp

プロダクトデザイン 印デザイン(インデザイン) In Design website

Page Load Speed

1.9 sec in total

First Response

522 ms

Resources Loaded

1.2 sec

Page Rendered

111 ms

indesign.jp screenshot

About Website

Welcome to indesign.jp homepage info - get ready to check In Design best content right away, or after learning these important things about indesign.jp

印デザイン(インデザイン)は池内昭仁と石井保幸からなるプロダクトデザインユニット。企業とのコラボレーションなどを行いつつも、ハンドメイドによるプロトタイプの製作など、大量生産では作ることのできない斬新なデザインの試みを積極的に行っている。

Visit indesign.jp

Key Findings

We analyzed Indesign.jp page load time and found that the first response time was 522 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

indesign.jp performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

98/100

10%

LCP (Largest Contentful Paint)

Value1.4 s

100/100

25%

SI (Speed Index)

Value2.0 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.4 s

100/100

10%

Network Requests Diagram

indesign.jp

522 ms

index.css

170 ms

jquery.js

514 ms

common.js

346 ms

logo_off.gif

164 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 78.1 kB (67%)

Content Size

116.9 kB

After Optimization

38.8 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Indesign.jp main page is 116.9 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. Only 5% of websites need less resources to load. Javascripts take 113.7 kB which makes up the majority of the site volume.

HTML Optimization

-53%

Potential reduce by 1.1 kB

  • Original 2.1 kB
  • After minification 2.0 kB
  • After compression 966 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 1.1 kB or 53% of the original size.

JavaScript Optimization

-67%

Potential reduce by 76.4 kB

  • Original 113.7 kB
  • After minification 107.9 kB
  • After compression 37.3 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 76.4 kB or 67% of the original size.

CSS Optimization

-54%

Potential reduce by 613 B

  • Original 1.1 kB
  • After minification 741 B
  • After compression 517 B

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. Indesign.jp needs all CSS files to be minified and compressed as it can save up to 613 B or 54% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

5

After Optimization

5

  • Images
  • JavaScript
  • CSS

The browser has sent 5 CSS, Javascripts, AJAX and image requests in order to completely render the main page of In Design. According to our analytics all requests are already optimized.

Network Requests Diagram

indesign.jp

indesign.jp

522 ms

index.css

index.css

170 ms

jquery.js

jquery.js

514 ms

common.js

common.js

346 ms

logo_off.gif

logo_off.gif

164 ms

logo_on.gif

logo_on.gif

172 ms

Accessibility Review

indesign.jp accessibility score

100

Accessibility Issues

Best Practices

indesign.jp best practices score

62

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

High

Registers an unload listener

Low

Detected JavaScript libraries

SEO Factors

indesign.jp SEO score

75

Search Engine Optimization Advices

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

indesign.jp

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