Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

kiito.jp

KIITO|デザイン・クリエイティブセンター神戸

Page Load Speed

10.7 sec in total

First Response

2.4 sec

Resources Loaded

7.6 sec

Page Rendered

691 ms

About Website

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

「デザイン都市・神戸」のシンボルであり“創造と交流”の拠点として、平成24年8月に誕生したデザイン・クリエイティブセンター神戸のサイト。

Visit kiito.jp

Key Findings

We analyzed Kiito.jp page load time and found that the first response time was 2.4 sec and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

kiito.jp performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value20.4 s

0/100

25%

SI (Speed Index)

Value15.1 s

1/100

10%

TBT (Total Blocking Time)

Value520 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value1.297

1/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

kiito.jp

2440 ms

style.css

1659 ms

jquery.js

2005 ms

common.js

876 ms

jquery.bxslider.min.js

1067 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 89% of them (89 requests) were addressed to the original Kiito.jp, 2% (2 requests) were made to Googletagmanager.com and 2% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Kiito.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 606.4 kB (9%)

Content Size

6.7 MB

After Optimization

6.1 MB

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

HTML Optimization

-77%

Potential reduce by 42.6 kB

  • Original 55.3 kB
  • After minification 52.8 kB
  • After compression 12.6 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 42.6 kB or 77% of the original size.

Image Optimization

-2%

Potential reduce by 97.3 kB

  • Original 6.0 MB
  • After minification 5.9 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. KIITO images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 352.7 kB

  • Original 457.9 kB
  • After minification 315.8 kB
  • After compression 105.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 352.7 kB or 77% of the original size.

CSS Optimization

-87%

Potential reduce by 113.8 kB

  • Original 130.8 kB
  • After minification 108.1 kB
  • After compression 16.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. Kiito.jp needs all CSS files to be minified and compressed as it can save up to 113.8 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (19%)

Requests Now

98

After Optimization

79

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

Accessibility Review

kiito.jp accessibility score

53

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

kiito.jp best practices score

75

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

High

Browser errors were logged to the console

SEO Factors

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

High

Image elements do not have [alt] attributes

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 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 Kiito.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 Kiito.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 data is detected on the main page of KIITO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: