Tools & Wizards About Us
sly.jp screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 70

    SEO

    Google-friendlier than
    30% of websites

sly.jp

SLY（スライ） | バロックジャパンリミテッド（BAROQUE）

Page Load Speed

7.4 sec in total

First Response

342 ms

Resources Loaded

4.9 sec

Page Rendered

2.2 sec

sly.jp screenshot

About Website

Click here to check amazing SLY content for Japan. Otherwise, check out these important facts you probably never knew about sly.jp

SLY [スライ] オフィシャルウェブサイト。「Casual」「Girly」「Mode」をベースに発信する、ディテールへのこだわりが詰まった、どこか必ず女性らしさを感じるアーバンスタイル。さまざまなエッセンスをミックスした、時代の空気を体現するコレクションを展開。

Visit sly.jp

Key Findings

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

sly.jp performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value1,490 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

Network Requests Diagram

sly.jp

342 ms

sly.jp

903 ms

js

71 ms

gtm.js

148 ms

js

148 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 30% of them (30 requests) were addressed to the original Sly.jp, 9% (9 requests) were made to Googletagmanager.com and 6% (6 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Sly.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 180.2 kB (9%)

Content Size

1.9 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-73%

Potential reduce by 25.9 kB

  • Original 35.7 kB
  • After minification 33.7 kB
  • After compression 9.7 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 25.9 kB or 73% of the original size.

Image Optimization

-3%

Potential reduce by 55.3 kB

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

JavaScript Optimization

-48%

Potential reduce by 61.1 kB

  • Original 127.1 kB
  • After minification 118.6 kB
  • After compression 65.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 61.1 kB or 48% of the original size.

CSS Optimization

-84%

Potential reduce by 37.8 kB

  • Original 44.8 kB
  • After minification 30.2 kB
  • After compression 7.0 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. Sly.jp needs all CSS files to be minified and compressed as it can save up to 37.8 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 62 (68%)

Requests Now

91

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sly.jp

sly.jp

342 ms

sly.jp

sly.jp

903 ms

js

js

71 ms

gtm.js

gtm.js

148 ms

js

js

148 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

36 ms

swiper.min.js

swiper.min.js

46 ms

swiper.min.css

swiper.min.css

55 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

351 ms

setting.js

setting.js

587 ms

lib.js

lib.js

732 ms

lib.css

lib.css

589 ms

base.css

base.css

724 ms

common.js

common.js

589 ms

temp.css

temp.css

583 ms

index.css

index.css

808 ms

js

js

117 ms

analytics.js

analytics.js

19 ms

collect

collect

78 ms

collect

collect

97 ms

collect

collect

235 ms

1121 ms

destination

destination

97 ms

collect

collect

216 ms

collect

collect

317 ms

destination

destination

130 ms

collect

collect

208 ms

destination

destination

120 ms

322 ms

js

js

136 ms

js

js

105 ms

loading.svg

loading.svg

491 ms

ig_sly.png

ig_sly.png

180 ms

ig_info.png

ig_info.png

182 ms

ig_throw.png

ig_throw.png

182 ms

journal.svg

journal.svg

332 ms

bnr.webp

bnr.webp

841 ms

catalog.svg

catalog.svg

346 ms

p01.jpg

p01.jpg

1013 ms

p01.jpg

p01.jpg

1008 ms

throw.svg

throw.svg

499 ms

bnr.jpg

bnr.jpg

1215 ms

visual.svg

visual.svg

655 ms

bnr.webp

bnr.webp

998 ms

collabo.svg

collabo.svg

982 ms

post_03_t.webp

post_03_t.webp

1007 ms

news.svg

news.svg

1150 ms

top.jpg

top.jpg

1337 ms

pixel.js

pixel.js

59 ms

base_pc.css

base_pc.css

1173 ms

temp_pc.css

temp_pc.css

1167 ms

collect

collect

26 ms

pv.js

pv.js

755 ms

so_sg.js

so_sg.js

129 ms

s_retargeting.js

s_retargeting.js

849 ms

115396.ct.js

115396.ct.js

87 ms

uwt.js

uwt.js

40 ms

fbevents.js

fbevents.js

50 ms

adsct

adsct

78 ms

adsct

adsct

104 ms

adsct

adsct

95 ms

adsct

adsct

147 ms

pixel

pixel

170 ms

bnr.webp

bnr.webp

1120 ms

js

js

720 ms

iframe

iframe

197 ms

conversion.js

conversion.js

685 ms

pixel

pixel

71 ms

Pug

Pug

43 ms

hs

hs

800 ms

sync.ad-stir.com

sync.ad-stir.com

717 ms

tap.php

tap.php

56 ms

sync

sync

905 ms

104 ms

cookiesync

cookiesync

720 ms

cs

cs

758 ms

sync.ad

sync.ad

264 ms

cs

cs

702 ms

sync

sync

274 ms

sync

sync

98 ms

google

google

192 ms

sync

sync

22 ms

bounce

bounce

13 ms

sd

sd

33 ms

conversion_async.js

conversion_async.js

922 ms

ytag.js

ytag.js

169 ms

sosync

sosync

182 ms

18 ms

pixel

pixel

14 ms

v2

v2

3 ms

sync

sync

686 ms

sync

sync

18 ms

16 ms

pixel

pixel

14 ms

sync

sync

819 ms

sd

sd

28 ms

Pug

Pug

5 ms

hs

hs

167 ms

um

um

47 ms

580 ms

tap.php

tap.php

4 ms

Accessibility Review

sly.jp accessibility score

86

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

sly.jp SEO score

70

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 doesn't use 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 Sly.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 Sly.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

sly.jp

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