6.6 sec in total
1.1 sec
5.3 sec
145 ms
Welcome to cs.itoki.jp homepage info - get ready to check Cs ITOKI best content for Japan right away, or after learning these important things about cs.itoki.jp
イトーキのショールームでは、最新ソリューションや話題の製品のプレゼンテーションを行っております。お近くのショールームへお越しいただき、イトーキの考える新しい提案を是非ご体感ください。
Visit cs.itoki.jpWe analyzed Cs.itoki.jp page load time and found that the first response time was 1.1 sec and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
cs.itoki.jp performance score
name
value
score
weighting
Value5.4 s
6/100
10%
Value9.6 s
0/100
25%
Value8.5 s
18/100
10%
Value740 ms
40/100
30%
Value0
100/100
15%
Value12.7 s
13/100
10%
1119 ms
321 ms
336 ms
339 ms
342 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 86% of them (43 requests) were addressed to the original Cs.itoki.jp, 8% (4 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Cs.itoki.jp.
Page size can be reduced by 170.7 kB (36%)
474.0 kB
303.3 kB
In fact, the total size of Cs.itoki.jp main page is 474.0 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. 20% of websites need less resources to load. Images take 203.4 kB which makes up the majority of the site volume.
Potential reduce by 11.7 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 11.7 kB or 69% of the original size.
Potential reduce by 900 B
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. Cs ITOKI images are well optimized though.
Potential reduce by 61.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 61.2 kB or 44% of the original size.
Potential reduce by 96.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. Cs.itoki.jp needs all CSS files to be minified and compressed as it can save up to 96.9 kB or 85% of the original size.
Number of requests can be reduced by 18 (38%)
48
30
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cs ITOKI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
cs.itoki.jp
1119 ms
ren_import.css
321 ms
basic.css
336 ms
top.css
339 ms
import.js
342 ms
pagenavi-css.css
316 ms
ren2014_main.css
326 ms
ren2014_menu.css
365 ms
ren2014_frame.css
1363 ms
jquery.min.js
26 ms
rollover.js
346 ms
smoothScroll.js
353 ms
wp-emoji-release.min.js
661 ms
ga.js
34 ms
analytics.js
34 ms
n56xPA1VYYkbnuMCkuViLRoQMx1IYhdo_tcB0AVS8w--.gif
1143 ms
ren2014_logo.gif
336 ms
ren2014_headernavi01_off.gif
336 ms
ren2014_headernavi02_ov.gif
356 ms
ren2014_headernavi03_off.gif
359 ms
ren2014_headernavi04_off.gif
361 ms
ren2014_headernavi05_off.gif
700 ms
ren2014_headernavi06_off.gif
701 ms
ren_headernavi07_off.gif
701 ms
ren2014_gnavi01_off.gif
702 ms
ren2014_gnavi02_off.gif
702 ms
ren2014_gnavi03_off.gif
986 ms
title1.gif
997 ms
img01.jpg
1319 ms
img02.jpg
1367 ms
title2.gif
1053 ms
img03.jpg
1599 ms
title3.gif
1347 ms
img04.jpg
1537 ms
img05.jpg
1532 ms
img06.jpg
1856 ms
img07.jpg
2034 ms
ren_footer_bg01.gif
1728 ms
ren_footer_bg02.gif
1892 ms
ren_footer_bg03.gif
1896 ms
ren_footer_banner01_off.jpg
2320 ms
ren_footer_banner02_off.gif
2105 ms
ren_footer_banner03_off.gif
2166 ms
ren_footer_bg04.gif
2435 ms
footer_twitter_bt.gif
2253 ms
footer_fb_bt.gif
2386 ms
footer_youtube_bt.gif
2462 ms
__utm.gif
11 ms
collect
14 ms
collect
60 ms
cs.itoki.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
cs.itoki.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
cs.itoki.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
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
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cs.itoki.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 Cs.itoki.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.
cs.itoki.jp
Open Graph description is not detected on the main page of Cs ITOKI. 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: