Tools & Wizards About Us
charmy.co.jp screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

charmy.co.jp

CHARMY(チャーミー)【公式】結婚指輪・婚約指輪・ファッションジュエリー

Page Load Speed

7.5 sec in total

First Response

531 ms

Resources Loaded

5.4 sec

Page Rendered

1.6 sec

charmy.co.jp screenshot

About Website

Click here to check amazing CHARMY content. Otherwise, check out these important facts you probably never knew about charmy.co.jp

CHARMY（チャーミー）公式サイト。高い品質で末永く愛せる結婚指輪(マリッジリング)、婚約指輪(エンゲージリング)、ファッションジュエリーをご提供しています。｜横浜、東京、千葉、埼玉

Visit charmy.co.jp

Key Findings

We analyzed Charmy.co.jp page load time and found that the first response time was 531 ms and then it took 6.9 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

charmy.co.jp performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value15.6 s

0/100

25%

SI (Speed Index)

Value22.8 s

0/100

10%

TBT (Total Blocking Time)

Value2,860 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.071

96/100

15%

TTI (Time to Interactive)

Value72.6 s

0/100

10%

Network Requests Diagram

charmy.co.jp

531 ms

charmy.co.jp

1149 ms

snapwidget.js

47 ms

glottologist

421 ms

js

80 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 57% of them (56 requests) were addressed to the original Charmy.co.jp, 9% (9 requests) were made to Snapwidget.com and 6% (6 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 406.5 kB (2%)

Content Size

17.9 MB

After Optimization

17.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Charmy.co.jp main page is 17.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 17.5 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 63.9 kB

  • Original 78.7 kB
  • After minification 73.5 kB
  • After compression 14.8 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 63.9 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 311.2 kB

  • Original 17.5 MB
  • After minification 17.2 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. CHARMY images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 9.5 kB

  • Original 233.6 kB
  • After minification 233.6 kB
  • After compression 224.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

-18%

Potential reduce by 21.9 kB

  • Original 123.0 kB
  • After minification 122.9 kB
  • After compression 101.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. Charmy.co.jp needs all CSS files to be minified and compressed as it can save up to 21.9 kB or 18% of the original size.

Requests Breakdown

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

Requests Now

94

After Optimization

52

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

charmy.co.jp

charmy.co.jp

531 ms

charmy.co.jp

charmy.co.jp

1149 ms

snapwidget.js

snapwidget.js

47 ms

glottologist

glottologist

421 ms

js

js

80 ms

gtranslate-style16.css

gtranslate-style16.css

174 ms

style.min.css

style.min.css

352 ms

style.css

style.css

687 ms

animate.css

animate.css

516 ms

swiper.css

swiper.css

49 ms

jquery.min.js

jquery.min.js

686 ms

jquery-migrate.min.js

jquery-migrate.min.js

524 ms

wow.min.js

wow.min.js

526 ms

swiper.js

swiper.js

58 ms

jquery-3.6.0.js

jquery-3.6.0.js

47 ms

jquery.cookie.min.js

jquery.cookie.min.js

61 ms

script.js

script.js

525 ms

glottologist@2.0.3

glottologist@2.0.3

11 ms

glottologist.min.js

glottologist.min.js

10 ms

css2

css2

29 ms

logo_header.svg

logo_header.svg

190 ms

ico_facebook.png

ico_facebook.png

189 ms

ico_instagram.png

ico_instagram.png

189 ms

ico_twitter.png

ico_twitter.png

189 ms

ico_arrow_right.png

ico_arrow_right.png

186 ms

ico_reservation_close.png

ico_reservation_close.png

189 ms

ja.svg

ja.svg

579 ms

bg_fixed.jpeg

bg_fixed.jpeg

945 ms

pic_fv0.jpg

pic_fv0.jpg

621 ms

pic_fv1.jpg

pic_fv1.jpg

620 ms

pic_fv2.jpg

pic_fv2.jpg

874 ms

pic_fv3.jpg

pic_fv3.jpg

750 ms

pic_fv4.jpg

pic_fv4.jpg

750 ms

pic_fv5.jpg

pic_fv5.jpg

841 ms

pic_fv6.jpg

pic_fv6.jpg

929 ms

pic_brand01.jpg

pic_brand01.jpg

927 ms

pic_brand02.png

pic_brand02.png

1281 ms

pic_about01@2x.jpg

pic_about01@2x.jpg

1015 ms

ico_arrow_square.png

ico_arrow_square.png

1049 ms

pic_about02@2x.jpg

pic_about02@2x.jpg

1103 ms

pic_about03.jpg

pic_about03.jpg

1099 ms

pic_about04.jpg

pic_about04.jpg

1314 ms

pic_engagement_right.png

pic_engagement_right.png

1193 ms

pic_marriage_ring.png

pic_marriage_ring.png

1224 ms

pic_fashion@2x.png

pic_fashion@2x.png

2150 ms

image2.jpeg

image2.jpeg

1805 ms

1e5c1371810e09992c2e98b626151b5d.jpg

1e5c1371810e09992c2e98b626151b5d.jpg

2055 ms

pic_slider01.jpg

pic_slider01.jpg

2454 ms

pic_slider02.jpg

pic_slider02.jpg

1637 ms

pic_slider03.jpg

pic_slider03.jpg

1508 ms

pic_slider04.jpg

pic_slider04.jpg

1682 ms

pic_slider05.jpg

pic_slider05.jpg

1818 ms

pic_slider06.jpg

pic_slider06.jpg

1856 ms

pic_slider07.jpg

pic_slider07.jpg

1989 ms

pic_slider08.jpg

pic_slider08.jpg

2183 ms

pic_slider09.jpg

pic_slider09.jpg

2064 ms

element.js

element.js

97 ms

PyNZPvqbHZk

PyNZPvqbHZk

221 ms

1009708

1009708

103 ms

font

font

2804 ms

embed.vendor.min.760717b3f565c387.css

embed.vendor.min.760717b3f565c387.css

10 ms

embed.style.min.41abd7aaef93351c.css

embed.style.min.41abd7aaef93351c.css

24 ms

embed.grid.min.4069f6f840f9102b.css

embed.grid.min.4069f6f840f9102b.css

20 ms

js

js

46 ms

embed.vendor.min.2f17f0b14ee46c5a.js

embed.vendor.min.2f17f0b14ee46c5a.js

22 ms

embed.main.min.65b73ba9362828bd.js

embed.main.min.65b73ba9362828bd.js

17 ms

iframeResizer.contentWindow.min.0da4d54c7d115e53.js

iframeResizer.contentWindow.min.0da4d54c7d115e53.js

40 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

67 ms

analytics.js

analytics.js

46 ms

post_type_icons.png

post_type_icons.png

31 ms

ico_arrow_right_brown.png

ico_arrow_right_brown.png

1983 ms

bg_cta_button.png

bg_cta_button.png

2058 ms

bnr_sustainability_sp@2x.jpg

bnr_sustainability_sp@2x.jpg

2065 ms

bnr_sustainability@2x.jpg

bnr_sustainability@2x.jpg

2151 ms

bnr.png

bnr.png

2166 ms

button_sp_top.png

button_sp_top.png

2171 ms

collect

collect

11 ms

js

js

65 ms

www-player.css

www-player.css

9 ms

www-embed-player.js

www-embed-player.js

27 ms

base.js

base.js

52 ms

ad_status.js

ad_status.js

217 ms

HRWvHAg5u1ehCJtdrky-PNA-CjIWhbU7xrlveGXuadw.js

HRWvHAg5u1ehCJtdrky-PNA-CjIWhbU7xrlveGXuadw.js

139 ms

embed.js

embed.js

55 ms

wwB5Xk8KZqnn020CrhrtqvKqR4fCzPqKeAQ7xNIUCmO4kXhpdBVeBbTsS9kR2xanPN-dppSxtQ=s68-c-k-c0x00ffffff-no-rj

wwB5Xk8KZqnn020CrhrtqvKqR4fCzPqKeAQ7xNIUCmO4kXhpdBVeBbTsS9kR2xanPN-dppSxtQ=s68-c-k-c0x00ffffff-no-rj

173 ms

logo_footer.png

logo_footer.png

1837 ms

453270418_515547574343610_8674961481513108566_n.jpg

453270418_515547574343610_8674961481513108566_n.jpg

134 ms

453412050_18448654504025708_2003617894116886603_n.jpg

453412050_18448654504025708_2003617894116886603_n.jpg

226 ms

453477599_18448659103025708_7681744548708162908_n.jpg

453477599_18448659103025708_7681744548708162908_n.jpg

238 ms

453727394_18449208325025708_2842737136570424062_n.jpg

453727394_18449208325025708_2842737136570424062_n.jpg

230 ms

454153901_1921807504968084_5324648519666789175_n.jpg

454153901_1921807504968084_5324648519666789175_n.jpg

230 ms

454015528_18449543182025708_96240194812879470_n.jpg

454015528_18449543182025708_96240194812879470_n.jpg

246 ms

bg_pattern.png

bg_pattern.png

1811 ms

bg_pattern_white.png

bg_pattern_white.png

1894 ms

id

id

113 ms

Create

Create

89 ms

ico_arrow_right@2x.png

ico_arrow_right@2x.png

1780 ms

GenerateIT

GenerateIT

19 ms

log_event

log_event

15 ms

Accessibility Review

charmy.co.jp accessibility score

95

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

charmy.co.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

charmy.co.jp SEO score

88

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

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 Charmy.co.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 Charmy.co.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

charmy.co.jp

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