Tools & Wizards About Us
styleworks.jp screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

styleworks.jp

STYLE WORKS

Page Load Speed

6.8 sec in total

First Response

353 ms

Resources Loaded

5.9 sec

Page Rendered

489 ms

styleworks.jp screenshot

About Website

Click here to check amazing STYLE WORKS content. Otherwise, check out these important facts you probably never knew about styleworks.jp

メンズシャツのリーディングカンパニー山喜によるオリジナルレーベル＜STYLE WORKS＞。他には無い日本発の高品質な“シャツ”をお届けします。スタイルワークス│店舗情報│ドレスシャツ│オーダーシャツ

Visit styleworks.jp

Key Findings

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

Performance Metrics

styleworks.jp performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value4.7 s

68/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.441

21/100

15%

TTI (Time to Interactive)

Value5.1 s

75/100

10%

Network Requests Diagram

styleworks.jp

353 ms

boilerplate.css

136 ms

common.css

152 ms

grid.css

154 ms

top-only.css

156 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 90% of them (26 requests) were addressed to the original Styleworks.jp, 7% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (5.1 sec) belongs to the original domain Styleworks.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 41.7 kB (42%)

Content Size

99.5 kB

After Optimization

57.8 kB

  • HTML
  • JavaScript

In fact, the total size of Styleworks.jp main page is 99.5 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. 25% of websites need less resources to load. Javascripts take 86.3 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 9.7 kB

  • Original 13.1 kB
  • After minification 10.8 kB
  • After compression 3.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 2.3 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 9.7 kB or 74% of the original size.

JavaScript Optimization

-37%

Potential reduce by 32.0 kB

  • Original 86.3 kB
  • After minification 86.3 kB
  • After compression 54.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 32.0 kB or 37% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (31%)

Requests Now

26

After Optimization

18

  • Images
  • JavaScript
  • CSS

The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of STYLE WORKS. 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 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

styleworks.jp

styleworks.jp

353 ms

boilerplate.css

boilerplate.css

136 ms

common.css

common.css

152 ms

grid.css

grid.css

154 ms

top-only.css

top-only.css

156 ms

jquery.bxslider.css

jquery.bxslider.css

157 ms

respond.min.js

respond.min.js

160 ms

jquery.min.js

jquery.min.js

399 ms

jquery.min.js

jquery.min.js

10 ms

jquery.bxslider.js

jquery.bxslider.js

282 ms

analytics.js

analytics.js

19 ms

banner_01.gif

banner_01.gif

67 ms

header-bgimg-tone.png

header-bgimg-tone.png

69 ms

top-gray.gif

top-gray.gif

134 ms

topwhite.jpg

topwhite.jpg

5145 ms

icon.png

icon.png

394 ms

another.png

another.png

379 ms

ba001.jpg

ba001.jpg

960 ms

ba002.jpg

ba002.jpg

2560 ms

ba003.jpg

ba003.jpg

879 ms

ba004.jpg

ba004.jpg

1649 ms

tp_order.jpg

tp_order.jpg

1105 ms

tp_facebook.jpg

tp_facebook.jpg

1259 ms

footer_facebook.gif

footer_facebook.gif

1110 ms

footer_google.gif

footer_google.gif

1255 ms

footer_instagram.gif

footer_instagram.gif

1263 ms

footer_info1.gif

footer_info1.gif

1390 ms

collect

collect

11 ms

bx_loader.gif

bx_loader.gif

1357 ms

Accessibility Review

styleworks.jp accessibility score

64

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.

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

styleworks.jp best practices score

58

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

styleworks.jp SEO score

64

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

High

Document doesn't have a valid hreflang

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

styleworks.jp

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