Access itohari.jp. ニットシャツ専門店ITOHARI公式ショップ

itohari.jp screenshot

72

Performance

Renders faster than
82% of other websites
52

Accessibility

Visual factors better than
that of 21% of websites
58

Best Practices

More advanced features
available than in
19% of websites
67

SEO

Google-friendlier than
25% of websites

First Response

615 ms

Resources Loaded

8.8 sec

Page Rendered

1.3 sec

itohari.jp screenshot

About Website

Visit itohari.jp now to see the best up-to-date Itohari content for Japan and also check out these interesting facts you probably never knew about itohari.jp

日本人特有の手先の器用さ、そして真面目さから生まれた世界初の動体裁断ニットシャツ

Visit itohari.jp

Key Findings

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

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

35/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value200 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value2.8 s

97/100

10%

itohari.jp

615 ms

www.itohari.jp

1014 ms

style_001.css

381 ms

ticker-style.css

422 ms

jquery.min.js

30 ms

Our browser made a total of 196 requests to load all elements on the main page. We found that 55% of them (107 requests) were addressed to the original Itohari.jp, 37% (72 requests) were made to C24.future-shop.jp and 2% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Itohari.jp.

Content Size

3.7 MB

After Optimization

3.3 MB

In fact, the total size of Itohari.jp main page is 3.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 3.5 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 77.3 kB

Original 89.8 kB
After minification 76.9 kB
After compression 12.4 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. This page needs HTML code to be minified as it can gain 12.9 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 77.3 kB or 86% of the original size.

Image Optimization

-6%

Potential reduce by 224.5 kB

Original 3.5 MB
After minification 3.3 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. Itohari images are well optimized though.

JavaScript Optimization

-40%

Potential reduce by 40.7 kB

Original 101.3 kB
After minification 94.0 kB
After compression 60.5 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 40.7 kB or 40% of the original size.

Requests Now

189

After Optimization

171

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

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

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

High

Browser errors were logged to the console

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

Language and Encoding

Language Detected

JA
Language Claimed

N/A
Encoding

SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Itohari.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Itohari.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

itohari.jp

Open Graph description is not detected on the main page of Itohari. 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: