Tools & Wizards About Us
kuum.jp screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

kuum.jp

Kuum.jp: Online Shopping for wooden toy blocks | Felissimo

Page Load Speed

5.9 sec in total

First Response

366 ms

Resources Loaded

5.2 sec

Page Rendered

350 ms

kuum.jp screenshot

About Website

Welcome to kuum.jp homepage info - get ready to check Kuum best content for Japan right away, or after learning these important things about kuum.jp

KUUM is a collection of wooden toy blocks with 12 stories on the various elements of nature, stimulating both logical and emotional creativity in children of all ages.

Visit kuum.jp

Key Findings

We analyzed Kuum.jp page load time and found that the first response time was 366 ms 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

kuum.jp performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value20.7 s

0/100

10%

TBT (Total Blocking Time)

Value8,800 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

Network Requests Diagram

kuum.jp

366 ms

kuum.jp

629 ms

main.css

300 ms

jquery-1.10.2.min.js

581 ms

jquery.easing.1.3.js

438 ms

Our browser made a total of 130 requests to load all elements on the main page. We found that 98% of them (127 requests) were addressed to the original Kuum.jp, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Kuum.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 99.2 kB (2%)

Content Size

4.8 MB

After Optimization

4.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kuum.jp main page is 4.8 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.6 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 24.5 kB

  • Original 30.0 kB
  • After minification 26.0 kB
  • After compression 5.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 3.9 kB, which is 13% 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 24.5 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 43.5 kB

  • Original 4.6 MB
  • After minification 4.5 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. Kuum images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 9.6 kB

  • Original 125.5 kB
  • After minification 125.5 kB
  • After compression 115.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-79%

Potential reduce by 21.6 kB

  • Original 27.3 kB
  • After minification 27.3 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. Kuum.jp needs all CSS files to be minified and compressed as it can save up to 21.6 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (4%)

Requests Now

126

After Optimization

121

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kuum.jp

kuum.jp

366 ms

kuum.jp

kuum.jp

629 ms

main.css

main.css

300 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

581 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

438 ms

plugins.js

plugins.js

732 ms

jquery.easymask.js

jquery.easymask.js

442 ms

index.js

index.js

605 ms

top-visual.jpg

top-visual.jpg

612 ms

top-visual-smp.jpg

top-visual-smp.jpg

450 ms

index-logo.svg

index-logo.svg

301 ms

about-visual.jpg

about-visual.jpg

443 ms

about-visual-smp.jpg

about-visual-smp.jpg

438 ms

title.svg

title.svg

166 ms

01_soil.jpg

01_soil.jpg

446 ms

01_soil.jpg

01_soil.jpg

590 ms

02_fire.jpg

02_fire.jpg

721 ms

02_fire.jpg

02_fire.jpg

586 ms

03_flower.jpg

03_flower.jpg

736 ms

03_flower.jpg

03_flower.jpg

593 ms

04_tree.jpg

04_tree.jpg

731 ms

04_tree.jpg

04_tree.jpg

735 ms

05_mountain.jpg

05_mountain.jpg

739 ms

05_mountain.jpg

05_mountain.jpg

736 ms

06_sea.jpg

06_sea.jpg

862 ms

06_sea.jpg

06_sea.jpg

875 ms

07_ice.jpg

07_ice.jpg

1026 ms

07_ice.jpg

07_ice.jpg

880 ms

08_stone.jpg

08_stone.jpg

879 ms

08_stone.jpg

08_stone.jpg

883 ms

09_earth.jpg

09_earth.jpg

1003 ms

09_earth.jpg

09_earth.jpg

1023 ms

10_moon.jpg

10_moon.jpg

1026 ms

10_moon.jpg

10_moon.jpg

1027 ms

11_sun.jpg

11_sun.jpg

1031 ms

11_sun.jpg

11_sun.jpg

1144 ms

12_sand.jpg

12_sand.jpg

1163 ms

12_sand.jpg

12_sand.jpg

1162 ms

01_soil.svg

01_soil.svg

1162 ms

02_fire.svg

02_fire.svg

1167 ms

03_flower.svg

03_flower.svg

1174 ms

04_tree.svg

04_tree.svg

1282 ms

05_mountain.svg

05_mountain.svg

1306 ms

06_sea.svg

06_sea.svg

1309 ms

analytics.js

analytics.js

87 ms

30FDFF_0_0.woff

30FDFF_0_0.woff

1158 ms

collect

collect

14 ms

collect

collect

32 ms

30DDFD_1_0.woff

30DDFD_1_0.woff

1177 ms

07_ice.svg

07_ice.svg

939 ms

08_stone.svg

08_stone.svg

995 ms

09_earth.svg

09_earth.svg

1018 ms

10_moon.svg

10_moon.svg

1027 ms

11_sun.svg

11_sun.svg

885 ms

12_sand.svg

12_sand.svg

912 ms

00_title.png

00_title.png

988 ms

01_soil.png

01_soil.png

1013 ms

02_fire.png

02_fire.png

895 ms

03_flower.png

03_flower.png

885 ms

04_tree.png

04_tree.png

883 ms

05_mountain.png

05_mountain.png

893 ms

06_sea.png

06_sea.png

985 ms

07_ice.png

07_ice.png

1011 ms

08_stone.png

08_stone.png

891 ms

09_earth.png

09_earth.png

888 ms

10_moon.png

10_moon.png

902 ms

11_sun.png

11_sun.png

902 ms

12_sand.png

12_sand.png

980 ms

title.svg

title.svg

890 ms

01.jpg

01.jpg

1017 ms

01.jpg

01.jpg

875 ms

02.jpg

02.jpg

1025 ms

02.jpg

02.jpg

892 ms

03.jpg

03.jpg

984 ms

03.jpg

03.jpg

893 ms

04.jpg

04.jpg

884 ms

04.jpg

04.jpg

911 ms

00_title.png

00_title.png

981 ms

01.png

01.png

1011 ms

02.png

02.png

1004 ms

03.png

03.png

907 ms

04.png

04.png

932 ms

title.svg

title.svg

929 ms

01.jpg

01.jpg

964 ms

01.jpg

01.jpg

965 ms

02.jpg

02.jpg

905 ms

02.jpg

02.jpg

889 ms

03.jpg

03.jpg

882 ms

03.jpg

03.jpg

897 ms

04.jpg

04.jpg

962 ms

04.jpg

04.jpg

994 ms

05.jpg

05.jpg

930 ms

05.jpg

05.jpg

891 ms

06.jpg

06.jpg

896 ms

06.jpg

06.jpg

944 ms

07.jpg

07.jpg

975 ms

07.jpg

07.jpg

997 ms

08.jpg

08.jpg

921 ms

08.jpg

08.jpg

884 ms

09.jpg

09.jpg

886 ms

09.jpg

09.jpg

881 ms

10.jpg

10.jpg

950 ms

10.jpg

10.jpg

973 ms

11.jpg

11.jpg

916 ms

11.jpg

11.jpg

886 ms

00_title.png

00_title.png

887 ms

01.png

01.png

909 ms

02.png

02.png

860 ms

03.png

03.png

873 ms

04.png

04.png

878 ms

05.png

05.png

877 ms

06.png

06.png

856 ms

07.png

07.png

864 ms

08.png

08.png

868 ms

09.png

09.png

871 ms

10.png

10.png

883 ms

11.png

11.png

889 ms

spec-visual.jpg

spec-visual.jpg

842 ms

spec-visual-smp.jpg

spec-visual-smp.jpg

836 ms

cart.svg

cart.svg

830 ms

credit-visual.jpg

credit-visual.jpg

868 ms

credit-visual-smp.jpg

credit-visual-smp.jpg

863 ms

credit-logo.png

credit-logo.png

868 ms

flight.svg

flight.svg

860 ms

instagram.svg

instagram.svg

881 ms

logo.svg

logo.svg

846 ms

logo-fellisimo@x2.png

logo-fellisimo@x2.png

857 ms

cart-gray.svg

cart-gray.svg

858 ms

logo-fellisimo2@x2.png

logo-fellisimo2@x2.png

861 ms

instagram-grey.svg

instagram-grey.svg

862 ms

Accessibility Review

kuum.jp accessibility score

70

Accessibility Issues

Internationalization and localization

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

Impact

Issue

High

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

SEO Factors

kuum.jp SEO score

92

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

Image elements do not have [alt] attributes

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kuum.jp can be misinterpreted by Google and other search engines. Our service has detected that English 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 Kuum.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

kuum.jp

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