Tools & Wizards About Us
crystar.jp screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

crystar.jp

ミネラルクリスター

Page Load Speed

5.6 sec in total

First Response

541 ms

Resources Loaded

4.9 sec

Page Rendered

181 ms

crystar.jp screenshot

About Website

Click here to check amazing Crystar content. Otherwise, check out these important facts you probably never knew about crystar.jp

オールミネラル水化システム「ミネラルクリスター」で、暮らしのすべての水を「ミネラルウォーター”に。建物すべての蛇口からミネラルバランスのとれた水を供給します。

Visit crystar.jp

Key Findings

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

crystar.jp performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value12.9 s

0/100

25%

SI (Speed Index)

Value7.0 s

33/100

10%

TBT (Total Blocking Time)

Value800 ms

36/100

30%

CLS (Cumulative Layout Shift)

Value0.416

23/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

crystar.jp

541 ms

www.crystar.jp

531 ms

www.crystar.jp

720 ms

style.css

177 ms

style_pc.css

352 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 83% of them (78 requests) were addressed to the original Crystar.jp, 4% (4 requests) were made to Platform.twitter.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Crystar.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 293.4 kB (28%)

Content Size

1.1 MB

After Optimization

765.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Crystar.jp main page is 1.1 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. 50% of websites need less resources to load. Images take 961.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 21.2 kB

  • Original 26.7 kB
  • After minification 23.0 kB
  • After compression 5.5 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 3.7 kB, which is 14% 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 21.2 kB or 79% of the original size.

Image Optimization

-27%

Potential reduce by 256.5 kB

  • Original 961.7 kB
  • After minification 705.2 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. Obviously, Crystar needs image optimization as it can save up to 256.5 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-17%

Potential reduce by 8.4 kB

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

CSS Optimization

-34%

Potential reduce by 7.4 kB

  • Original 21.7 kB
  • After minification 21.7 kB
  • After compression 14.3 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. Crystar.jp needs all CSS files to be minified and compressed as it can save up to 7.4 kB or 34% of the original size.

Requests Breakdown

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

Requests Now

87

After Optimization

67

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

crystar.jp

crystar.jp

541 ms

www.crystar.jp

www.crystar.jp

531 ms

www.crystar.jp

www.crystar.jp

720 ms

style.css

style.css

177 ms

style_pc.css

style_pc.css

352 ms

article.css

article.css

512 ms

jquery.min.js

jquery.min.js

26 ms

jquery.easing.min.js

jquery.easing.min.js

40 ms

common2.js

common2.js

514 ms

jquery.cookie.js

jquery.cookie.js

515 ms

js

js

78 ms

inc_index.css

inc_index.css

517 ms

jquery.bxSlider.js

jquery.bxSlider.js

528 ms

widgets.js

widgets.js

28 ms

css

css

34 ms

css

css

17 ms

like.php

like.php

302 ms

bg_head.png

bg_head.png

177 ms

head_logo.png

head_logo.png

346 ms

bg_m.png

bg_m.png

171 ms

m_01.png

m_01.png

203 ms

m_01o.png

m_01o.png

172 ms

m_01c.png

m_01c.png

173 ms

bg_m_li.png

bg_m_li.png

341 ms

m_02.png

m_02.png

342 ms

m_02o.png

m_02o.png

346 ms

m_02c.png

m_02c.png

350 ms

m_03.png

m_03.png

379 ms

m_03o.png

m_03o.png

510 ms

m_03c.png

m_03c.png

511 ms

m_04.png

m_04.png

516 ms

m_04o.png

m_04o.png

517 ms

m_04c.png

m_04c.png

526 ms

m_05.png

m_05.png

558 ms

m_05o.png

m_05o.png

680 ms

m_05c.png

m_05c.png

681 ms

m_07.png

m_07.png

688 ms

m_07o.png

m_07o.png

688 ms

m_07c.png

m_07c.png

701 ms

head_nav_01.png

head_nav_01.png

735 ms

head_inq.png

head_inq.png

849 ms

head_nav_02.png

head_nav_02.png

850 ms

head_rec.png

head_rec.png

859 ms

head_fd_pc.png

head_fd_pc.png

860 ms

head_fd_sp.png

head_fd_sp.png

877 ms

head_em.png

head_em.png

913 ms

ind_crystar.png

ind_crystar.png

1019 ms

ind_insta.png

ind_insta.png

1189 ms

ind_ct.png

ind_ct.png

1030 ms

index_ban100.png

index_ban100.png

1206 ms

index_ban105.png

index_ban105.png

1052 ms

index_ban106.png

index_ban106.png

1090 ms

index_ban104.png

index_ban104.png

1190 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

23 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj35zS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj35zS1g.ttf

23 ms

xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bwxOtbHKrc.ttf

xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bwxOtbHKrc.ttf

80 ms

settings

settings

98 ms

crystar.woff

crystar.woff

1036 ms

icons.woff

icons.woff

1061 ms

index_ban103.png

index_ban103.png

1099 ms

index_ban101.png

index_ban101.png

1189 ms

index_ban95.png

index_ban95.png

1163 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

2 ms

embeds

embeds

30 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

12 ms

AcAvebb33yC.js

AcAvebb33yC.js

24 ms

FEppCFCt76d.png

FEppCFCt76d.png

18 ms

index_ban62.png

index_ban62.png

1210 ms

index_ban41.png

index_ban41.png

1038 ms

index_ban68.png

index_ban68.png

1063 ms

index_ban48.png

index_ban48.png

1104 ms

index_ban49.png

index_ban49.png

1184 ms

index_ban50.png

index_ban50.png

1155 ms

index.png

index.png

1213 ms

index_sp.png

index_sp.png

1248 ms

icons_01.png

icons_01.png

1110 ms

icons_02.png

icons_02.png

1188 ms

icons_03.png

icons_03.png

1178 ms

icons_04.png

icons_04.png

1163 ms

icons_05.png

icons_05.png

1126 ms

icons_06.png

icons_06.png

1193 ms

a_totop_01.png

a_totop_01.png

1186 ms

a_totop_02.png

a_totop_02.png

1205 ms

company.png

company.png

1193 ms

side_ban_01_close.gif

side_ban_01_close.gif

1198 ms

side_ban_04.png

side_ban_04.png

1488 ms

side_ban_01.png

side_ban_01.png

1194 ms

side_ban_05-half.png

side_ban_05-half.png

1186 ms

index_ban_bg.png

index_ban_bg.png

1546 ms

index_ban00.gif

index_ban00.gif

1189 ms

bg_m_curr.png

bg_m_curr.png

1196 ms

index_ban_l.png

index_ban_l.png

1193 ms

index_ban_r.png

index_ban_r.png

1183 ms

style_sp.css

style_sp.css

177 ms

Accessibility Review

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

Links do not have a discernible name

Best Practices

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

crystar.jp SEO score

92

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

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

crystar.jp

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