Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 74

    SEO

    Google-friendlier than
    32% of websites

cs.itoki.jp

ショールーム | ITOKI

Page Load Speed

6.6 sec in total

First Response

1.1 sec

Resources Loaded

5.3 sec

Page Rendered

145 ms

cs.itoki.jp screenshot

About Website

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

Key Findings

We 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.

Performance Metrics

cs.itoki.jp performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value740 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.7 s

13/100

10%

Network Requests Diagram

cs.itoki.jp

1119 ms

ren_import.css

321 ms

basic.css

336 ms

top.css

339 ms

import.js

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 Optimization Overview & Recommendations

Page size can be reduced by 170.7 kB (36%)

Content Size

474.0 kB

After Optimization

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.

HTML Optimization

-69%

Potential reduce by 11.7 kB

  • Original 17.0 kB
  • After minification 16.6 kB
  • After compression 5.3 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.

Image Optimization

-0%

Potential reduce by 900 B

  • Original 203.4 kB
  • After minification 202.5 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. Cs ITOKI images are well optimized though.

JavaScript Optimization

-44%

Potential reduce by 61.2 kB

  • Original 140.0 kB
  • After minification 138.6 kB
  • After compression 78.8 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.

CSS Optimization

-85%

Potential reduce by 96.9 kB

  • Original 113.5 kB
  • After minification 88.5 kB
  • After compression 16.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. 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.

Requests Breakdown

Number of requests can be reduced by 18 (38%)

Requests Now

48

After Optimization

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.

Accessibility Review

cs.itoki.jp accessibility score

86

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Links do not have a discernible name

Best Practices

cs.itoki.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

High

Page has valid source maps

SEO Factors

cs.itoki.jp SEO score

74

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

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

High

Tap targets are not sized appropriately

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

Social Sharing Optimization

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: