Tools & Wizards About Us
lilysilk.jp screenshot

Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

lilysilk.jp

シルク枕カバー、シルクナイトキャップ、シルクパジャマ、シルク寝具カバー、ファッション服 | リリーシルク（LILYSILK）

Page Load Speed

5.3 sec in total

First Response

41 ms

Resources Loaded

1.8 sec

Page Rendered

3.5 sec

lilysilk.jp screenshot

About Website

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

リリーシルク（LILYSILK）は贅沢な天然シルク枕カバー、高級なシルクパジャマ、人気のシルクナイトキャップ、シルク寝具カバー、ファッション服など様々な美肌アイテムで、皆様の快適ライフを応援いたします。

Visit lilysilk.jp

Key Findings

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

Performance Metrics

lilysilk.jp performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value44.4 s

0/100

25%

SI (Speed Index)

Value22.7 s

0/100

10%

TBT (Total Blocking Time)

Value11,160 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.855

4/100

15%

TTI (Time to Interactive)

Value62.6 s

0/100

10%

Network Requests Diagram

41 ms

calendar.css

22 ms

styles-m.css

45 ms

afterpay.css

40 ms

trustpilot.min.css

40 ms

Our browser made a total of 167 requests to load all elements on the main page. We found that 35% of them (58 requests) were addressed to the original Lilysilk.jp, 49% (82 requests) were made to Images.lilysilk.com and 5% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 514.3 kB (3%)

Content Size

15.8 MB

After Optimization

15.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lilysilk.jp main page is 15.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. Only a small number of websites need less resources to load. Images take 13.6 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 293.8 kB

  • Original 348.8 kB
  • After minification 295.8 kB
  • After compression 55.1 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 53.1 kB, which is 15% 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 293.8 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-3%

Potential reduce by 45.8 kB

  • Original 1.6 MB
  • After minification 1.6 MB
  • After compression 1.6 MB

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

-76%

Potential reduce by 174.7 kB

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

Requests Breakdown

Number of requests can be reduced by 74 (50%)

Requests Now

149

After Optimization

75

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

41 ms

calendar.css

calendar.css

22 ms

styles-m.css

styles-m.css

45 ms

afterpay.css

afterpay.css

40 ms

trustpilot.min.css

trustpilot.min.css

40 ms

autocomplete.css

autocomplete.css

39 ms

grid.css

grid.css

39 ms

algolia-reset.css

algolia-reset.css

41 ms

instantsearch.v3.css

instantsearch.v3.css

97 ms

style.css

style.css

96 ms

styles-l.css

styles-l.css

98 ms

css2

css2

140 ms

menu-white.svg

menu-white.svg

139 ms

Search.svg

Search.svg

90 ms

1.jpg

1.jpg

111 ms

1.jpg

1.jpg

111 ms

1.jpg

1.jpg

279 ms

1.jpg

1.jpg

113 ms

close.svg

close.svg

110 ms

hook.svg

hook.svg

112 ms

back.svg

back.svg

113 ms

success.svg

success.svg

114 ms

right-black.svg

right-black.svg

116 ms

shrink.svg

shrink.svg

117 ms

extend.svg

extend.svg

115 ms

menu-black.svg

menu-black.svg

152 ms

close-black.svg

close-black.svg

286 ms

search-white.svg

search-white.svg

285 ms

search-black.svg

search-black.svg

282 ms

logo-white.svg

logo-white.svg

287 ms

logo-black.svg

logo-black.svg

283 ms

account-white.svg

account-white.svg

285 ms

account-black.svg

account-black.svg

287 ms

cart-white.svg

cart-white.svg

288 ms

cart-black.svg

cart-black.svg

292 ms

logo-icon-white.svg

logo-icon-white.svg

290 ms

logo-icon-black.svg

logo-icon-black.svg

289 ms

organic-light.svg

organic-light.svg

291 ms

organic-regular.svg

organic-regular.svg

294 ms

Close.svg

Close.svg

111 ms

require.min.js

require.min.js

110 ms

requirejs-min-resolver.min.js

requirejs-min-resolver.min.js

109 ms

bundle0.min.js

bundle0.min.js

131 ms

bundle1.min.js

bundle1.min.js

134 ms

bundle2.min.js

bundle2.min.js

131 ms

bundle3.min.js

bundle3.min.js

133 ms

bundle4.min.js

bundle4.min.js

127 ms

bundle5.min.js

bundle5.min.js

144 ms

bundle6.min.js

bundle6.min.js

139 ms

bundle7.min.js

bundle7.min.js

143 ms

static.min.js

static.min.js

143 ms

mixins.min.js

mixins.min.js

142 ms

requirejs-config.min.js

requirejs-config.min.js

145 ms

87401.js

87401.js

101 ms

lpcv.js

lpcv.js

1033 ms

a8sales.js

a8sales.js

111 ms

a8crossDomain.js

a8crossDomain.js

129 ms

lilysilk.min.js

lilysilk.min.js

103 ms

fashion2-jp.jpg

fashion2-jp.jpg

283 ms

fashion6-jp.jpg

fashion6-jp.jpg

285 ms

fashion1-jp.jpg

fashion1-jp.jpg

287 ms

fashion3-jp.jpg

fashion3-jp.jpg

287 ms

fashion4-jp.jpg

fashion4-jp.jpg

285 ms

sleepwear1-jp.jpg

sleepwear1-jp.jpg

289 ms

sleepwear2-jp.jpg

sleepwear2-jp.jpg

288 ms

sleepwear3-jp.jpg

sleepwear3-jp.jpg

287 ms

sleepwear4-jp.jpg

sleepwear4-jp.jpg

290 ms

sleepwear5-jp.jpg

sleepwear5-jp.jpg

291 ms

bedding1-jp.jpg

bedding1-jp.jpg

292 ms

bedding2-jp.jpg

bedding2-jp.jpg

293 ms

bedding3-jp.jpg

bedding3-jp.jpg

293 ms

bedding4-jp.jpg

bedding4-jp.jpg

294 ms

acc1-jp.jpg

acc1-jp.jpg

294 ms

acc2-jp.jpg

acc2-jp.jpg

301 ms

acc3-jp.jpg

acc3-jp.jpg

299 ms

acc4-jp.jpg

acc4-jp.jpg

296 ms

collection17-pc-jp.jpg

collection17-pc-jp.jpg

295 ms

collection17-mb-jp.jpg

collection17-mb-jp.jpg

297 ms

collection17-1-jp.jpg

collection17-1-jp.jpg

300 ms

polyfill.min.js

polyfill.min.js

140 ms

common.min.js

common.min.js

265 ms

instantsearch.min.js

instantsearch.min.js

122 ms

autocomplete.min.js

autocomplete.min.js

122 ms

insights.min.js

insights.min.js

200 ms

infinitehits.min.js

infinitehits.min.js

247 ms

plus.svg

plus.svg

244 ms

minus.svg

minus.svg

194 ms

css

css

66 ms

collection17-2-jp.jpg

collection17-2-jp.jpg

181 ms

collection16-pc-jp.jpg

collection16-pc-jp.jpg

162 ms

Graphik-Medium-Web.woff

Graphik-Medium-Web.woff

76 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf

234 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75s.ttf

970 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j75s.ttf

989 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEj75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEj75s.ttf

989 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEi75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEi75s.ttf

988 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFM8k75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFM8k75s.ttf

990 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf

989 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEk75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEk75s.ttf

1191 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFLgk75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFLgk75s.ttf

1059 ms

Futura-Medium.woff

Futura-Medium.woff

77 ms

js-translation.json

js-translation.json

194 ms

collection16-mb-jp.jpg

collection16-mb-jp.jpg

170 ms

collection16-1-jp.jpg

collection16-1-jp.jpg

169 ms

collection16-2-jp.jpg

collection16-2-jp.jpg

165 ms

collection15-pc-jp.jpg

collection15-pc-jp.jpg

168 ms

collection15-mb-jp.jpg

collection15-mb-jp.jpg

162 ms

collection15-1-jp.jpg

collection15-1-jp.jpg

164 ms

collection15-2-jp.jpg

collection15-2-jp.jpg

168 ms

collection13-pc-jp.jpg

collection13-pc-jp.jpg

166 ms

collection13-mb-jp.jpg

collection13-mb-jp.jpg

166 ms

collection13-1-jp.jpg

collection13-1-jp.jpg

166 ms

collection13-2-jp.jpg

collection13-2-jp.jpg

166 ms

collection11-pc-jp.jpg

collection11-pc-jp.jpg

164 ms

collection11-mb-jp.jpg

collection11-mb-jp.jpg

165 ms

collection11-1-jp.jpg

collection11-1-jp.jpg

164 ms

collection11-2-jp.jpg

collection11-2-jp.jpg

164 ms

collection8-pc-jp.jpg

collection8-pc-jp.jpg

164 ms

collection8-mb-jp.jpg

collection8-mb-jp.jpg

165 ms

collection8-1-jp.jpg

collection8-1-jp.jpg

164 ms

collection8-2-jp.jpg

collection8-2-jp.jpg

164 ms

collection2-pc-jp.jpg

collection2-pc-jp.jpg

442 ms

collection2-mb-jp.jpg

collection2-mb-jp.jpg

168 ms

collection2-1-jp.jpg

collection2-1-jp.jpg

427 ms

collection2-2-jp.jpg

collection2-2-jp.jpg

424 ms

instagram.svg

instagram.svg

423 ms

instagram_hover.svg

instagram_hover.svg

421 ms

youtube.svg

youtube.svg

423 ms

youtube_hover.svg

youtube_hover.svg

528 ms

facebook.svg

facebook.svg

525 ms

facebook_hover.svg

facebook_hover.svg

530 ms

twitter.svg

twitter.svg

524 ms

twitter_hover.svg

twitter_hover.svg

526 ms

tiktok.svg

tiktok.svg

595 ms

tiktok_hover.svg

tiktok_hover.svg

628 ms

pinterest.svg

pinterest.svg

630 ms

pinterest_hover.svg

pinterest_hover.svg

630 ms

group.svg

group.svg

495 ms

print.css

print.css

283 ms

plus-white.svg

plus-white.svg

494 ms

minus-white.svg

minus-white.svg

515 ms

map.svg

map.svg

529 ms

placeholder.jpg

placeholder.jpg

529 ms

homebanner1-bg-pc-us.jpg

homebanner1-bg-pc-us.jpg

579 ms

Futura-Book.woff

Futura-Book.woff

174 ms

Futura-Demi.woff

Futura-Demi.woff

175 ms

GaramondClassico-Roman.woff

GaramondClassico-Roman.woff

164 ms

NotoSansKR-Regular.woff

NotoSansKR-Regular.woff

173 ms

FreightDispPro-Book.woff

FreightDispPro-Book.woff

172 ms

tp.widget.bootstrap.min.js

tp.widget.bootstrap.min.js

367 ms

tp.min.js

tp.min.js

349 ms

bat.js

bat.js

327 ms

v2.zopim.com

v2.zopim.com

349 ms

left-black.svg

left-black.svg

133 ms

homeslide1-jp.jpg

homeslide1-jp.jpg

315 ms

homeslide-2-jp.jpg

homeslide-2-jp.jpg

308 ms

homeslide3-jp.jpg

homeslide3-jp.jpg

304 ms

zxcvbn.min.js

zxcvbn.min.js

221 ms

ds.min.js

ds.min.js

280 ms

gtm.js

gtm.js

234 ms

225 ms

loader-1.gif

loader-1.gif

84 ms

messages-mixin.min.js

messages-mixin.min.js

50 ms

5176461.js

5176461.js

45 ms

index.js

index.js

68 ms

asset_composer.js

asset_composer.js

108 ms

index.js

index.js

53 ms

Accessibility Review

lilysilk.jp accessibility score

83

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.

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

High

<object> elements do not have alternate text

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

lilysilk.jp best practices score

83

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

Missing source maps for large first-party JavaScript

SEO Factors

lilysilk.jp SEO score

82

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

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

lilysilk.jp

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