Tools & Wizards About Us

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

kookan.jp

空間計画提案室：千葉、東京、埼玉、神奈川など、首都圏を中心に建築からガーデンまで幅広い設計を行っている建築設計事務所

Page Load Speed

6.8 sec in total

First Response

543 ms

Resources Loaded

5.6 sec

Page Rendered

636 ms

About Website

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

株式会社空間計画提案室は、千葉・東京・埼玉・神奈川などの首都圏を中心に建築、新築、リフォーム、デザイナーズハウス、店舗デザイン、オフィスデザイン、ガーデンまで幅広い設計を行っている建築設計事務所です。オーダーメイド建築のための無料相談会も開催しておりますので、建築のことならお気軽にご相談ください！

Visit kookan.jp

Key Findings

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

kookan.jp performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value11.9 s

0/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value640 ms

46/100

30%

CLS (Cumulative Layout Shift)

Value0.124

83/100

15%

TTI (Time to Interactive)

Value10.5 s

24/100

10%

Network Requests Diagram

kookan.jp

543 ms

kookan.jp

903 ms

js

75 ms

vue.min.js

1115 ms

jquery-1.12.0.min.js

355 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 79% of them (55 requests) were addressed to the original Kookan.jp, 6% (4 requests) were made to Font.e-trust-test.com and 6% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Kookan.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 183.1 kB (5%)

Content Size

3.5 MB

After Optimization

3.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kookan.jp main page is 3.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. 65% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 54.1 kB

  • Original 61.3 kB
  • After minification 53.0 kB
  • After compression 7.2 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 8.3 kB, which is 14% 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 54.1 kB or 88% of the original size.

Image Optimization

-1%

Potential reduce by 34.7 kB

  • Original 3.1 MB
  • After minification 3.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. Kookan images are well optimized though.

JavaScript Optimization

-25%

Potential reduce by 51.2 kB

  • Original 205.7 kB
  • After minification 205.1 kB
  • After compression 154.5 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 51.2 kB or 25% of the original size.

CSS Optimization

-41%

Potential reduce by 43.1 kB

  • Original 105.6 kB
  • After minification 105.6 kB
  • After compression 62.5 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. Kookan.jp needs all CSS files to be minified and compressed as it can save up to 43.1 kB or 41% of the original size.

Requests Breakdown

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

Requests Now

60

After Optimization

31

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

kookan.jp accessibility score

75

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

ARIA toggle fields do not have accessible names

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

kookan.jp best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

kookan.jp SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

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 Kookan.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 Kookan.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 Kookan. 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: