15.9 sec in total
3.8 sec
11.7 sec
433 ms
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.jpWe analyzed Kiito.jp page load time and found that the first response time was 3.8 sec and then it took 12.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
kiito.jp performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value25.2 s
0/100
25%
Value19.5 s
0/100
10%
Value430 ms
65/100
30%
Value1.395
0/100
15%
Value25.9 s
0/100
10%
3813 ms
330 ms
342 ms
346 ms
1292 ms
Our browser made a total of 158 requests to load all elements on the main page. We found that 60% of them (95 requests) were addressed to the original Kiito.jp, 10% (16 requests) were made to Static.xx.fbcdn.net and 9% (15 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Kiito.jp.
Page size can be reduced by 439.4 kB (13%)
3.3 MB
2.8 MB
In fact, the total size of Kiito.jp main page is 3.3 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 2.9 MB which makes up the majority of the site volume.
Potential reduce by 36.0 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 36.0 kB or 78% of the original size.
Potential reduce by 171.8 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. KIITO images are well optimized though.
Potential reduce by 187.7 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 187.7 kB or 61% of the original size.
Potential reduce by 43.8 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 43.8 kB or 82% of the original size.
Number of requests can be reduced by 47 (30%)
157
110
The browser has sent 157 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 23 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
kiito.jp
3813 ms
style.css
330 ms
styles.css
342 ms
pagenavi-css.css
346 ms
jquery.js
1292 ms
jquery.js
1262 ms
jquery.tile.js
505 ms
jquery.carouFredSel.js
1184 ms
common.js
520 ms
common.css
550 ms
top.css
850 ms
ga.js
12 ms
btn_english.gif
175 ms
logo_header.gif
166 ms
all.js
11 ms
bg_white.png
183 ms
logo_kiito.gif
174 ms
navi_about_off.gif
173 ms
navi_schedule_off.gif
322 ms
navi_rentalspace_off.gif
342 ms
navi_project_off.gif
343 ms
navi_floorguide_off.gif
345 ms
navi_access_off.gif
364 ms
navi_news_off.gif
482 ms
navi_lab_off.gif
513 ms
navi_connection_off.gif
512 ms
navi_mailmaga_off.gif
514 ms
navi_staff_off.gif
545 ms
navi_contact_off.gif
645 ms
__utm.gif
29 ms
54 ms
xd_arbiter.php
33 ms
xd_arbiter.php
46 ms
bosai_top.jpg
582 ms
bg_red.png
165 ms
arrow.png
184 ms
KIITONIGHT10_main.jpg
1055 ms
hajimete_main.jpg
889 ms
160210_web_lab-bread_main.jpg
2437 ms
nagashimatalk-banner.jpg
2865 ms
dKfesta2016_top.jpg
4009 ms
5d2e3ee15efeffd2979850ad800074f1.jpg
3589 ms
Marching-KOBE_TOP.jpg
4132 ms
KIITOFLYERS_main.jpg
4661 ms
categorynavi_all.png
3142 ms
categorynavi_zemi.png
3575 ms
categorynavi_lecture.png
3926 ms
categorynavi_workshop.png
4283 ms
categorynavi_exhibit.png
4346 ms
categorynavi_event.png
4654 ms
categorynavi_news.png
4643 ms
categorynavi_rental.png
4815 ms
a94e1f3891052b25404101369f56d6cc.jpg
4217 ms
ic_event.gif
4210 ms
KIITOFLYERS_eyecatch.jpg
4462 ms
ic_exhibition.gif
4436 ms
160210_web_lab-bread_thum.jpg
4455 ms
ic_seminar.gif
4440 ms
nagashimatalk-eyacatch.jpg
4639 ms
ic_lecture.gif
4764 ms
AIR2015-nagashima-eyecatch.jpg
5106 ms
ic_news.gif
4813 ms
KIITONIGHT10_eyecatch.jpg
4834 ms
hajimete_ec3.jpg
4837 ms
bosai_eye.jpg
5080 ms
dKfesta2016_thumb.jpg
5072 ms
91d91abc62f76cf835985a494c789594.jpg
5195 ms
b64c60dee4b0c15238075cbdee91002f-220x150.jpg
5160 ms
0223_ws_banner_nit_02.jpg
5150 ms
ic_workshop.gif
5486 ms
a11b4bb3ba448d1fa402ac3dc62cc91f-220x150.jpg
5505 ms
widgets.js
83 ms
jquery.form.min.js
5447 ms
scripts.js
5283 ms
jquery.infinitescroll.js
5172 ms
thumnail_makers.jpg
4244 ms
datekobe_th.jpg
3425 ms
mikaeru_web_thumb.jpg
3366 ms
KIITO_ppssub.png
3000 ms
shikisai_ec.jpg
3053 ms
0314kodomo-work1.jpg
2593 ms
30dee24fecdfeeccbc790a1188abedcc.jpg
2899 ms
93d49d92c73e8e5776cd820544eb131b.jpg
2688 ms
114ef7d33c973308758378f73b2789a7-220x150.jpg
2594 ms
omusubi_web_thumb.gif
2622 ms
title_access.gif
2226 ms
access_map_03.gif
2268 ms
arrow_red.gif
2287 ms
title_news.gif
2486 ms
cafebanner2.jpg
2507 ms
d80dec3c70e289d07933119c867b8a1b.jpg
2370 ms
chibibanner.jpg
3458 ms
1d1032aab2ef1fa529104476abe0be77.jpg
2492 ms
72ea58f3ccebb1dee0ebbe46790c9817.jpg
2221 ms
seisakubutsu-banner-s.jpg
2511 ms
btn_pagetop_off.gif
2210 ms
foot_logo.gif
2123 ms
txt_copy.gif
2198 ms
footnavi_contact.gif
2321 ms
footnavi_release.gif
2349 ms
footnavi_privacy.gif
2142 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
122 ms
carousel_circle.gif
1672 ms
page.php
179 ms
syndication
91 ms
279493802039836672
344 ms
pQ7eOEs7xah.css
48 ms
bSm8X_J4qDU.css
52 ms
8kS9cSrZ-wV.css
47 ms
q68gy-v_YMF.js
50 ms
k19Xse48j5I.js
68 ms
ihptErjAmMX.js
43 ms
3So47A9WcrL.js
83 ms
cUsKAwzqrQw.js
85 ms
538934_460864213953272_1567290248_n.jpg
187 ms
safe_image.php
195 ms
lRyN50VcaFW.js
36 ms
10151220_719874778052213_9140311627813463738_n.jpg
94 ms
12804796_771025826375851_5118448850162894390_n.jpg
262 ms
12074793_765124363595928_7511827413427965977_n.jpg
91 ms
75542_510629739124853_7203070781223123122_n.jpg
55 ms
530947_277778072335856_191468251_n.jpg
51 ms
11407120_1110762422272871_845351649438795492_n.jpg
129 ms
1924013_1095331057173248_6765737357118205969_n.jpg
62 ms
5444_1095331087173245_7050932556714674122_n.jpg
134 ms
72347_1095331093839911_1653224729974871604_n.jpg
88 ms
1557715_1095331120506575_1690801554506260595_n.jpg
93 ms
10360550_1093121487394205_497085257935168263_n.jpg
91 ms
12832494_1092426157463738_3636528443933335379_n.jpg
101 ms
10338314_1091751530864534_6969827601200726293_n.jpg
105 ms
wL6VQj7Ab77.png
32 ms
s7jcwEQH7Sx.png
31 ms
GtIpNnEyqq_.png
31 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
29 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
69 ms
_UrLT_5X_normal.png
181 ms
logo_normal.png
56 ms
O9YosYKQ_normal.jpg
56 ms
qCvl-oSf_normal.jpg
55 ms
Resatoshi_normal.jpg
56 ms
jFrZCjH9_normal.jpeg
192 ms
Hayase_Twicon_150_normal.png
61 ms
Cdb9zJmUAAEG6fh.jpg:small
167 ms
CdVxBlEUAAAAPVj.jpg:small
174 ms
Cdz7iHvVIAAobDS.jpg:small
59 ms
Cdz7iHwUIAA4VW3.jpg:small
180 ms
Cdz7iIVUEAAI4Vd.jpg:small
182 ms
CdfA5AqUUAARbZS.jpg:small
165 ms
CdfA5oQUYAAAQzD.jpg:small
183 ms
CdfA34yUMAAHmn5.jpg:small
208 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
58 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
150 ms
R9a_DtVRZgv.js
25 ms
cUDgRFxaoIk.js
21 ms
0JBr1QHp8Gi.js
23 ms
kDOzhTr2W91.js
23 ms
link_v1_e64f66f5650df987d97cc5f00c4cb5987f367028.svg
11 ms
jot.html
28 ms
kiito.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
kiito.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
kiito.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
JA
JA
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.
kiito.jp
Open Graph description is not detected on the main page of KIITO. 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: