Tools & Wizards About Us
wears.jp screenshot

Report Summary

  • 69

    Performance

    Renders faster than
    80% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

wears.jp

株式会社ウェアーズ公式サイト（WEARS INC）

Page Load Speed

5.2 sec in total

First Response

1.1 sec

Resources Loaded

4 sec

Page Rendered

109 ms

wears.jp screenshot

About Website

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

w closetなどを展開する株式会社ウェアーズの公式企業サイト。

Visit wears.jp

Key Findings

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

Performance Metrics

wears.jp performance score

69

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

71/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.297

40/100

15%

TTI (Time to Interactive)

Value3.4 s

92/100

10%

Network Requests Diagram

wears.jp

1102 ms

reset.css

291 ms

style.css

304 ms

jquery.bxslider.css

311 ms

index.css

375 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that all of those requests were addressed to Wears.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Wears.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 138.7 kB (22%)

Content Size

635.9 kB

After Optimization

497.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wears.jp main page is 635.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Images take 462.5 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 7.0 kB

  • Original 9.4 kB
  • After minification 9.2 kB
  • After compression 2.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 7.0 kB or 75% of the original size.

Image Optimization

-2%

Potential reduce by 11.6 kB

  • Original 462.5 kB
  • After minification 451.0 kB

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. WEARS images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 110.2 kB

  • Original 150.9 kB
  • After minification 124.4 kB
  • After compression 40.7 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 110.2 kB or 73% of the original size.

CSS Optimization

-76%

Potential reduce by 9.9 kB

  • Original 13.1 kB
  • After minification 9.9 kB
  • After compression 3.1 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. Wears.jp needs all CSS files to be minified and compressed as it can save up to 9.9 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (23%)

Requests Now

31

After Optimization

24

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wears.jp

wears.jp

1102 ms

reset.css

reset.css

291 ms

style.css

style.css

304 ms

jquery.bxslider.css

jquery.bxslider.css

311 ms

index.css

index.css

375 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

779 ms

jquery.fademover.js

jquery.fademover.js

313 ms

scrollsmoothly.js

scrollsmoothly.js

414 ms

base.js

base.js

441 ms

jquery.bxslider.js

jquery.bxslider.js

775 ms

logo.png

logo.png

176 ms

sp_menu.jpg

sp_menu.jpg

289 ms

btn_brand.png

btn_brand.png

333 ms

btn_online.png

btn_online.png

342 ms

btn_facebook.png

btn_facebook.png

341 ms

btn_twitter.png

btn_twitter.png

383 ms

btn_instagram.png

btn_instagram.png

482 ms

gnav_home.png

gnav_home.png

649 ms

gnav_news.png

gnav_news.png

671 ms

gnav_company.png

gnav_company.png

677 ms

gnav_recruit.png

gnav_recruit.png

690 ms

01.gif

01.gif

756 ms

02.jpg

02.jpg

1740 ms

03.jpg

03.jpg

1839 ms

04.jpg

04.jpg

1849 ms

ttl_news.png

ttl_news.png

1009 ms

go_top.png

go_top.png

1035 ms

sp_btn_facebook.png

sp_btn_facebook.png

1043 ms

sp_btn_twitter.png

sp_btn_twitter.png

1319 ms

sp_btn_instagram.png

sp_btn_instagram.png

1374 ms

sp_btn_brandsite.png

sp_btn_brandsite.png

1381 ms

sp_btn_onlineshop.png

sp_btn_onlineshop.png

1681 ms

bx_loader.gif

bx_loader.gif

2030 ms

controls.png

controls.png

2062 ms

Accessibility Review

wears.jp accessibility score

63

Accessibility Issues

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

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

wears.jp best practices score

67

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

High

Browser errors were logged to the console

SEO Factors

wears.jp SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wears.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 Wears.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

wears.jp

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