Tools & Wizards About Us
textilecare.jp screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

textilecare.jp

テキスタイルケア 日本テキスタイルケア協会

Page Load Speed

7.9 sec in total

First Response

502 ms

Resources Loaded

7.1 sec

Page Rendered

256 ms

textilecare.jp screenshot

About Website

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

日本テキスタイルケア協会は「プロフェッショナル・テキスタイルケア産業」の創造を目指しています。

Visit textilecare.jp

Key Findings

We analyzed Textilecare.jp page load time and found that the first response time was 502 ms and then it took 7.4 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

textilecare.jp performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value450 ms

62/100

30%

CLS (Cumulative Layout Shift)

Value0.329

35/100

15%

TTI (Time to Interactive)

Value10.0 s

27/100

10%

Network Requests Diagram

textilecare.jp

502 ms

textilecare.jp

720 ms

www.textilecare.jp

525 ms

www.textilecare.jp

1853 ms

reset.css

333 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 98% of them (81 requests) were addressed to the original Textilecare.jp, 1% (1 request) were made to Ajax.googleapis.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Textilecare.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 71.1 kB (5%)

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 56.6 kB

  • Original 69.0 kB
  • After minification 64.0 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. 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 56.6 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 8.4 kB

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

JavaScript Optimization

-2%

Potential reduce by 2.0 kB

  • Original 118.1 kB
  • After minification 118.1 kB
  • After compression 116.1 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

-7%

Potential reduce by 4.0 kB

  • Original 54.6 kB
  • After minification 54.6 kB
  • After compression 50.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. Textilecare.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 35 (45%)

Requests Now

78

After Optimization

43

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

textilecare.jp

textilecare.jp

502 ms

textilecare.jp

textilecare.jp

720 ms

www.textilecare.jp

www.textilecare.jp

525 ms

www.textilecare.jp

www.textilecare.jp

1853 ms

reset.css

reset.css

333 ms

style.css

style.css

508 ms

index.css

index.css

668 ms

menu.css

menu.css

671 ms

style.min.css

style.min.css

694 ms

classic-themes.min.css

classic-themes.min.css

705 ms

jquery.fancybox.css

jquery.fancybox.css

698 ms

jquery-ui.min.css

jquery-ui.min.css

712 ms

default.css

default.css

838 ms

jquery.min.js

jquery.min.js

1009 ms

jquery-migrate.min.js

jquery-migrate.min.js

853 ms

jquery.fancybox.js

jquery.fancybox.js

870 ms

jquery.easing.js

jquery.easing.js

880 ms

jquery.ui.datepicker-ja.min.js

jquery.ui.datepicker-ja.min.js

30 ms

frontend-user-admin.css

frontend-user-admin.css

893 ms

net-shop-admin.css

net-shop-admin.css

1023 ms

menu.js

menu.js

1023 ms

swiper-bundle.min.js

swiper-bundle.min.js

1221 ms

sp-common.js

sp-common.js

1061 ms

sp-index.js

sp-index.js

1075 ms

flexslider.css

flexslider.css

1023 ms

public.css

public.css

1024 ms

index.js

index.js

1034 ms

index.js

index.js

1141 ms

core.min.js

core.min.js

1141 ms

datepicker.min.js

datepicker.min.js

1195 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

1198 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

684 ms

gtm.js

gtm.js

136 ms

logo.png

logo.png

236 ms

search_btn.gif

search_btn.gif

263 ms

top-lang-jpn-hover.gif

top-lang-jpn-hover.gif

348 ms

top-lang-eng.gif

top-lang-eng.gif

282 ms

top-icons.png

top-icons.png

283 ms

divider.gif

divider.gif

875 ms

icon_fb.svg

icon_fb.svg

413 ms

main01.jpg

main01.jpg

1685 ms

main02.jpg

main02.jpg

1434 ms

sustainable1.png

sustainable1.png

620 ms

sustainable2.png

sustainable2.png

923 ms

sustainable3.png

sustainable3.png

773 ms

sustainable4.png

sustainable4.png

956 ms

icon_arrow_circle.svg

icon_arrow_circle.svg

952 ms

23ecd5b993cb1e13fddbc52c0520c634-145x145.jpg

23ecd5b993cb1e13fddbc52c0520c634-145x145.jpg

1048 ms

LA2020-145x145.jpg

LA2020-145x145.jpg

1102 ms

20141204_090833-1-145x145.jpg

20141204_090833-1-145x145.jpg

1130 ms

b4cc388705530b1bbe9f688c09fad951-1-145x145.jpg

b4cc388705530b1bbe9f688c09fad951-1-145x145.jpg

1129 ms

shouhisha-145x145.jpg

shouhisha-145x145.jpg

1219 ms

6949c2b27d8d2c2de8a61b816bf5b27f-145x145.jpg

6949c2b27d8d2c2de8a61b816bf5b27f-145x145.jpg

1281 ms

7db7787944a977e8010fe2c09558689e-145x145.jpg

7db7787944a977e8010fe2c09558689e-145x145.jpg

1301 ms

eb94a9805d16163bd8c9febbe483806c-145x145.jpg

eb94a9805d16163bd8c9febbe483806c-145x145.jpg

1308 ms

muji-145x145.jpg

muji-145x145.jpg

1390 ms

icon_arrow.svg

icon_arrow.svg

1457 ms

icon_db.svg

icon_db.svg

1472 ms

icon_free.svg

icon_free.svg

1484 ms

hand1s-1-145x145.jpg

hand1s-1-145x145.jpg

1560 ms

d8d06f55c170f20cd89aafcdba74fc54-1-145x145.jpg

d8d06f55c170f20cd89aafcdba74fc54-1-145x145.jpg

1603 ms

ecdb637f4f471ae68268469d3d977b9b-145x145.jpg

ecdb637f4f471ae68268469d3d977b9b-145x145.jpg

1634 ms

26b42ba288baff42548fc9d20606e749-145x145.jpg

26b42ba288baff42548fc9d20606e749-145x145.jpg

1643 ms

eac39e09370a5f54132d60382afb09b4-145x145.jpg

eac39e09370a5f54132d60382afb09b4-145x145.jpg

1609 ms

5a120119906aca5658d9b5b917531cdf-145x145.jpg

5a120119906aca5658d9b5b917531cdf-145x145.jpg

1678 ms

45611982679e65366c37aa746c34a1aa-145x145.jpg

45611982679e65366c37aa746c34a1aa-145x145.jpg

1729 ms

20aea827fd836e137f4349cbedff582d-145x145.jpg

20aea827fd836e137f4349cbedff582d-145x145.jpg

1701 ms

Ito-SDGs-3-145x145.jpg

Ito-SDGs-3-145x145.jpg

1702 ms

support_bnr_kaname.gif

support_bnr_kaname.gif

1694 ms

support_bnr_inax.gif

support_bnr_inax.gif

1660 ms

support_bnr_digijapan.gif

support_bnr_digijapan.gif

1645 ms

support_bnr_ishiibunseido.gif

support_bnr_ishiibunseido.gif

1680 ms

support_bnr_zendora.gif

support_bnr_zendora.gif

1711 ms

support_bnr_electrolux.gif

support_bnr_electrolux.gif

1641 ms

support_bnr_rakuna.gif

support_bnr_rakuna.gif

1607 ms

support_bnr_tosei.gif

support_bnr_tosei.gif

1457 ms

support_bnr_sankosha.gif

support_bnr_sankosha.gif

1303 ms

support_bnr_tokyows.gif

support_bnr_tokyows.gif

1257 ms

support_bnr_morri.gif

support_bnr_morri.gif

1237 ms

support_bnr_asahigm.gif

support_bnr_asahigm.gif

1217 ms

parts_arrow2.png

parts_arrow2.png

1241 ms

bg_direction_nav.png

bg_direction_nav.png

1200 ms

swiper-bundle.min.css

swiper-bundle.min.css

176 ms

Accessibility Review

textilecare.jp accessibility score

90

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

[id] attributes on active, focusable elements are not unique

High

Some elements have a [tabindex] value greater than 0

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

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

textilecare.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

textilecare.jp SEO score

97

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

textilecare.jp

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