Tools & Wizards About Us
amuuse.jp screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

amuuse.jp

手編みと手芸の情報サイト あむゆーず

Page Load Speed

7.7 sec in total

First Response

529 ms

Resources Loaded

6.7 sec

Page Rendered

471 ms

amuuse.jp screenshot

About Website

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

あむゆーずは、楽しい手芸のハマナカ公式情報サイトです。編み図などの手づくりレシピを無料でダウンロードできたり、ブログや動画で手芸の最新情報をゲットできたりと、お役立ちコンテンツがいっぱい！

Visit amuuse.jp

Key Findings

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

Performance Metrics

amuuse.jp performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

4/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value400 ms

68/100

30%

CLS (Cumulative Layout Shift)

Value1.099

1/100

15%

TTI (Time to Interactive)

Value10.3 s

25/100

10%

Network Requests Diagram

amuuse.jp

529 ms

amuuse.jp

720 ms

index.html

1672 ms

common.css

970 ms

slideshow.min.css

487 ms

Our browser made a total of 111 requests to load all elements on the main page. We found that 89% of them (99 requests) were addressed to the original Amuuse.jp, 5% (5 requests) were made to Google.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Amuuse.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 348.9 kB (13%)

Content Size

2.8 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 41.5 kB

  • Original 51.4 kB
  • After minification 42.4 kB
  • After compression 9.9 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 9.0 kB, which is 17% 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 41.5 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 61.6 kB

  • Original 2.2 MB
  • After minification 2.2 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. Amuuse images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 130.6 kB

  • Original 359.0 kB
  • After minification 358.7 kB
  • After compression 228.4 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 130.6 kB or 36% of the original size.

CSS Optimization

-83%

Potential reduce by 115.3 kB

  • Original 138.2 kB
  • After minification 104.0 kB
  • After compression 22.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. Amuuse.jp needs all CSS files to be minified and compressed as it can save up to 115.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (13%)

Requests Now

107

After Optimization

93

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

amuuse.jp

amuuse.jp

529 ms

amuuse.jp

amuuse.jp

720 ms

index.html

index.html

1672 ms

common.css

common.css

970 ms

slideshow.min.css

slideshow.min.css

487 ms

top.min.css

top.min.css

489 ms

ga.js

ga.js

490 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

873 ms

common.min.js

common.min.js

527 ms

matchHeight.min.js

matchHeight.min.js

647 ms

slick.min.js

slick.min.js

682 ms

gtm.js

gtm.js

179 ms

logo.png

logo.png

206 ms

btn_base-sp.svg

btn_base-sp.svg

198 ms

btn_guide-sp.svg

btn_guide-sp.svg

194 ms

btn_search-sp.svg

btn_search-sp.svg

202 ms

ico_is.png

ico_is.png

194 ms

ico_fb.svg

ico_fb.svg

205 ms

ico_twitter.svg

ico_twitter.svg

476 ms

ico_roomclip.svg

ico_roomclip.svg

462 ms

btn_regist-pc.svg

btn_regist-pc.svg

464 ms

btn_mypage-pc.svg

btn_mypage-pc.svg

531 ms

nav_01-pc.svg

nav_01-pc.svg

468 ms

nav_02-pc.svg

nav_02-pc.svg

472 ms

nav_03-pc.svg

nav_03-pc.svg

604 ms

nav_04-pc.svg

nav_04-pc.svg

595 ms

nav_05-pc.svg

nav_05-pc.svg

590 ms

nav_06-pc.svg

nav_06-pc.svg

593 ms

nav_recipe_tit01-sp.svg

nav_recipe_tit01-sp.svg

606 ms

nav_recipe_tit01-pc.svg

nav_recipe_tit01-pc.svg

857 ms

nav_recipe_tit02-sp.svg

nav_recipe_tit02-sp.svg

752 ms

nav_recipe_tit02-pc.svg

nav_recipe_tit02-pc.svg

912 ms

nav_recipe_tit03-sp.svg

nav_recipe_tit03-sp.svg

759 ms

nav_recipe_tit03-pc.svg

nav_recipe_tit03-pc.svg

823 ms

nav_recipe_tit04-sp.svg

nav_recipe_tit04-sp.svg

779 ms

nav_recipe_tit04-pc.svg

nav_recipe_tit04-pc.svg

920 ms

202405_oliveplus_sp.jpg

202405_oliveplus_sp.jpg

1078 ms

20240305_ws_sp.jpg

20240305_ws_sp.jpg

1653 ms

240214shouten_sp.jpg

240214shouten_sp.jpg

1173 ms

202405mana_sp.jpg

202405mana_sp.jpg

1182 ms

202405_oliveplus_pc.jpg

202405_oliveplus_pc.jpg

1396 ms

20240305_ws_pc.jpg

20240305_ws_pc.jpg

1398 ms

240214shouten_pc.jpg

240214shouten_pc.jpg

1405 ms

202405mana_pc.jpg

202405mana_pc.jpg

1348 ms

news_tit-sp.svg

news_tit-sp.svg

1345 ms

news_tit-pc.svg

news_tit-pc.svg

1509 ms

cse.js

cse.js

148 ms

202405_AFWSnews.png

202405_AFWSnews.png

1490 ms

H145-223-121news.jpg

H145-223-121news.jpg

1400 ms

cse_element__en.js

cse_element__en.js

56 ms

default+en.css

default+en.css

122 ms

default.css

default.css

250 ms

icomoon.ttf

icomoon.ttf

1368 ms

amidaoremark.JPG

amidaoremark.JPG

1376 ms

AMO-061news.jpg

AMO-061news.jpg

1474 ms

H145-228-103cnews.jpg

H145-228-103cnews.jpg

1501 ms

btn_list.svg

btn_list.svg

1519 ms

js

js

97 ms

analytics.js

analytics.js

216 ms

rank_tit.svg

rank_tit.svg

1500 ms

async-ads.js

async-ads.js

175 ms

branding.png

branding.png

215 ms

clear.png

clear.png

67 ms

H145-223-121.jpg

H145-223-121.jpg

1271 ms

H145-183-130b.jpg

H145-183-130b.jpg

1360 ms

X-5.jpg

X-5.jpg

1366 ms

richmorepress_monthly.png

richmorepress_monthly.png

1404 ms

collect

collect

35 ms

olivier_bnr.png

olivier_bnr.png

1534 ms

amuuse_friends2023_sp.jpg

amuuse_friends2023_sp.jpg

1515 ms

collect

collect

11 ms

amuuse_friends2023_pc.jpg

amuuse_friends2023_pc.jpg

1306 ms

shichifukujin_br.jpg

shichifukujin_br.jpg

1410 ms

hokuouzakka_bnr.jpg

hokuouzakka_bnr.jpg

1406 ms

mofurabi_topic.jpg

mofurabi_topic.jpg

1444 ms

event_tit-sp.svg

event_tit-sp.svg

1449 ms

event_tit-pc.svg

event_tit-pc.svg

1410 ms

20240629_b.jpg

20240629_b.jpg

1420 ms

20240406_b20240406_3.jpg

20240406_b20240406_3.jpg

1426 ms

b20240210.jpg

b20240210.jpg

1383 ms

edit_tit-sp.svg

edit_tit-sp.svg

1371 ms

edit_tit-pc.svg

edit_tit-pc.svg

1307 ms

edit_press.svg

edit_press.svg

1405 ms

edit_blog.svg

edit_blog.svg

1279 ms

edit_tv.svg

edit_tv.svg

1360 ms

bnr_01.jpg

bnr_01.jpg

1358 ms

bnr_02.jpg

bnr_02.jpg

1041 ms

bnrS_01.png

bnrS_01.png

1058 ms

bnrS_02.png

bnrS_02.png

1099 ms

bnrS_03.png

bnrS_03.png

1143 ms

bnrS_04.png

bnrS_04.png

1148 ms

bnrS_05.png

bnrS_05.png

1072 ms

bnrS_06.png

bnrS_06.png

1133 ms

bnrS_07.png

bnrS_07.png

1134 ms

bnrS_08.png

bnrS_08.png

1124 ms

bnrS_10.png

bnrS_10.png

1113 ms

bnrS_12.png

bnrS_12.png

1064 ms

bnrS_15.jpg

bnrS_15.jpg

1085 ms

bnrS_16.jpg

bnrS_16.jpg

1121 ms

nav_01-sp.svg

nav_01-sp.svg

1131 ms

nav_02-sp.svg

nav_02-sp.svg

1132 ms

nav_03-sp.svg

nav_03-sp.svg

1153 ms

nav_04-sp.svg

nav_04-sp.svg

1049 ms

nav_05-sp.svg

nav_05-sp.svg

1098 ms

nav_06-sp.svg

nav_06-sp.svg

1109 ms

hr-pc.svg

hr-pc.svg

1123 ms

ico_rank01.svg

ico_rank01.svg

1021 ms

ico_rank02.svg

ico_rank02.svg

1040 ms

ico_rank03.svg

ico_rank03.svg

1016 ms

bg_01.jpg

bg_01.jpg

1067 ms

ajax-loader.gif

ajax-loader.gif

1097 ms

Accessibility Review

amuuse.jp accessibility score

95

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

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.

Tables and lists

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

Impact

Issue

High

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

Best Practices

amuuse.jp best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

amuuse.jp SEO score

99

Search Engine Optimization Advices

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

amuuse.jp

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