3.5 sec in total
258 ms
3.1 sec
142 ms
Visit kinezo.jp now to see the best up-to-date KINEZO content for Japan and also check out these interesting facts you probably never knew about kinezo.jp
Visit kinezo.jpWe analyzed Kinezo.jp page load time and found that the first response time was 258 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
kinezo.jp performance score
name
value
score
weighting
Value5.6 s
6/100
10%
Value7.6 s
3/100
25%
Value7.9 s
23/100
10%
Value1,710 ms
11/100
30%
Value0.078
95/100
15%
Value11.6 s
18/100
10%
258 ms
165 ms
312 ms
493 ms
338 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 80% of them (37 requests) were addressed to the original Kinezo.jp, 15% (7 requests) were made to Cdn.kinezo.jp and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Kinezo.jp.
Page size can be reduced by 401.2 kB (45%)
900.7 kB
499.5 kB
In fact, the total size of Kinezo.jp main page is 900.7 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. 35% of websites need less resources to load. Images take 527.9 kB which makes up the majority of the site volume.
Potential reduce by 17.5 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 17.5 kB or 77% of the original size.
Potential reduce by 119.1 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. Obviously, KINEZO needs image optimization as it can save up to 119.1 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 139.0 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 139.0 kB or 68% of the original size.
Potential reduce by 125.6 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. Kinezo.jp needs all CSS files to be minified and compressed as it can save up to 125.6 kB or 85% of the original size.
Number of requests can be reduced by 10 (22%)
45
35
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of KINEZO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
258 ms
normalize.css
165 ms
common.css
312 ms
content.css
493 ms
common_add.css
338 ms
jquery-1.11.2.min.js
538 ms
menu.js
338 ms
banner.css
355 ms
kinezo_top.css
464 ms
iscroll.js
505 ms
jquery.tinyTips.js
506 ms
1449215663xa97i6eibl.jpg
673 ms
1450333725h8h0imdyp3.jpg
533 ms
1454064419qdgj7ubdh2.jpg
709 ms
1449816591jfa1kfketg.jpg
711 ms
1450332369ytfwetkjga.jpg
735 ms
1426844966ijfrk2fnjv.jpg
561 ms
1438335516r32l3y563c.jpg
706 ms
headBg.png
166 ms
header_logo.png
155 ms
theaterLogo_niigata.png
169 ms
theaterLogo_nagaoka.png
169 ms
theaterLogo_shinjuku.png
181 ms
theaterLogo_oizumi.png
170 ms
theaterLogo_yokohama.png
310 ms
theaterLogo_soga.png
328 ms
theaterLogo_umeda.png
336 ms
theaterLogo_kyoto.png
336 ms
theaterLogo_hiroshima.png
338 ms
theaterLogo_higashihiroshima.png
356 ms
theaterLogo_izumo.png
462 ms
theaterLogo_hakata.png
492 ms
theaterLogo_kitakyusyu.png
502 ms
theaterLogo_kurume.png
502 ms
theaterLogo_oita.png
504 ms
theaterLogo_kagoshima.png
531 ms
theaterLogo_konosu.png
614 ms
ktop_user_aroow.png
655 ms
icon_close.png
667 ms
ktop_logo.png
670 ms
footer_logo.png
672 ms
top_theater.jpg
1593 ms
ktt_map02.png
1223 ms
analytics.js
20 ms
collect
13 ms
print.css
165 ms
kinezo.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
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.
kinezo.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
Page has valid source maps
kinezo.jp SEO score
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 doesn't use legible font sizes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kinezo.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 Kinezo.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.
kinezo.jp
Open Graph description is not detected on the main page of KINEZO. 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: