Access kucca.jp. オーガニック布おむつのお店「kucca」

kucca.jp screenshot

16

Performance

Renders faster than
30% of other websites
50

Accessibility

Visual factors better than
that of 20% of websites
58

Best Practices

More advanced features
available than in
19% of websites
82

SEO

Google-friendlier than
44% of websites

First Response

1.1 sec

Resources Loaded

9.5 sec

Page Rendered

331 ms

kucca.jp screenshot

About Website

Click here to check amazing Kucca content. Otherwise, check out these important facts you probably never knew about kucca.jp

日本国内生産ではじめての、日本人の体型を考えて作った布おむつ育児グッズのお店です。

Visit kucca.jp

Key Findings

We analyzed Kucca.jp page load time and found that the first response time was 1.1 sec and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster. This domain responded with an error, which can significantly jeopardize Kucca.jp rating and web reputation

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value1,900 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.141

78/100

15%

TTI (Time to Interactive)

Value18.0 s

3/100

10%

www.kucca.jp

1116 ms

cross-border-cart.css

308 ms

index.css

856 ms

top.css

312 ms

jquery.min.js

24 ms

Our browser made a total of 152 requests to load all elements on the main page. We found that 7% of them (11 requests) were addressed to the original Kucca.jp, 66% (100 requests) were made to Img13.shop-pro.jp and 7% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.4 sec) relates to the external source Img13.shop-pro.jp.

Content Size

2.6 MB

After Optimization

2.3 MB

In fact, the total size of Kucca.jp main page is 2.6 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. 55% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 97.4 kB

Original 121.2 kB
After minification 114.0 kB
After compression 23.8 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 97.4 kB or 80% of the original size.

Image Optimization

-4%

Potential reduce by 100.2 kB

Original 2.4 MB
After minification 2.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. Kucca images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 21.7 kB

Original 62.9 kB
After minification 59.1 kB
After compression 41.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 21.7 kB or 35% of the original size.

CSS Optimization

-82%

Potential reduce by 25.6 kB

Original 31.4 kB
After minification 21.7 kB
After compression 5.7 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. Kucca.jp needs all CSS files to be minified and compressed as it can save up to 25.6 kB or 82% of the original size.

Requests Now

144

After Optimization

85

The browser has sent 144 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kucca. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 6 to 1 for CSS 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

Form elements do not have associated labels

High

Links do not have a discernible name

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

JA
Language Claimed

JA
Encoding

EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kucca.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 Kucca.jp main page’s claimed encoding is euc-jp. 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

kucca.jp

Open Graph data is detected on the main page of Kucca. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: