10.5 sec in total
1.3 sec
9 sec
292 ms
Click here to check amazing ROSETTE content for Japan. Otherwise, check out these important facts you probably never knew about rosette.jp
いつの時代もさまざまな肌悩みと向き合い、良質な商品を作り続けている化粧品メーカー「ロゼット株式会社」が運営する公式オンラインショップです。ロゼットの商品情報やキャンペーンなどのお役立ち情報をお届けし、ロゼットの商品をWEB・オンラインにて直接ご購入いただくことができます。
Visit rosette.jpWe analyzed Rosette.jp page load time and found that the first response time was 1.3 sec and then it took 9.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
rosette.jp performance score
name
value
score
weighting
Value7.3 s
1/100
10%
Value17.9 s
0/100
25%
Value10.3 s
8/100
10%
Value1,160 ms
22/100
30%
Value0.006
100/100
15%
Value12.5 s
14/100
10%
1291 ms
358 ms
393 ms
406 ms
421 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 67% of them (83 requests) were addressed to the original Rosette.jp, 6% (7 requests) were made to Pbs.twimg.com and 5% (6 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Rosette.jp.
Page size can be reduced by 286.3 kB (15%)
2.0 MB
1.7 MB
In fact, the total size of Rosette.jp main page is 2.0 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. 40% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 40.0 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 7.8 kB, which is 16% 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 40.0 kB or 80% of the original size.
Potential reduce by 52.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. ROSETTE images are well optimized though.
Potential reduce by 102.2 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 102.2 kB or 57% of the original size.
Potential reduce by 91.8 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. Rosette.jp needs all CSS files to be minified and compressed as it can save up to 91.8 kB or 85% of the original size.
Number of requests can be reduced by 62 (53%)
116
54
The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ROSETTE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
rosette.jp
1291 ms
import.css
358 ms
css.js
393 ms
navi.js
406 ms
win_op.js
421 ms
site.js
432 ms
jquery-1.4.2.min.js
1096 ms
smoothRollOver.js
761 ms
fontsize.js
791 ms
conversion.js
550 ms
s_retargeting.js
597 ms
conversion.js
20 ms
responsiveslides.min.js
623 ms
reset.css
489 ms
common.css
912 ms
contents.css
931 ms
table.css
810 ms
bloc.css
1013 ms
bloc_alpha.css
906 ms
popup.css
1091 ms
print.css
1195 ms
cleansingpaste2014.css
1340 ms
factory_report.css
1333 ms
rosetteDay.css
1395 ms
webantenna.js
489 ms
img
1039 ms
logo.gif
199 ms
font_small_off.gif
212 ms
font_mdl_off.gif
375 ms
font_large_off.gif
388 ms
icon_cart.gif
401 ms
btn_cart_header_off.gif
602 ms
gmenu_01_off.gif
591 ms
gmenu_02_off.gif
625 ms
gmenu_03_off.gif
768 ms
gmenu_04_off.gif
846 ms
gmenu_05_off.gif
821 ms
btn1.png
964 ms
bn960360_2016ss_sale.jpg
1769 ms
bn960360_rspwd_new.jpg
1710 ms
bn960360_goma_2016ss.jpg
2374 ms
bn960360_nb_2016ss.jpg
2720 ms
960360_newlife2016.jpg
1908 ms
title_01.gif
1369 ms
icon_facebook.gif
1768 ms
icon_twitter.gif
2147 ms
210210_2016ssnew.jpg
2310 ms
suhadabi_BRWASH2015.jpg
2379 ms
03010902_56d4dc2b0db83.gif
2520 ms
02081003_56b7e95564c05.jpg
2537 ms
title_02.gif
2693 ms
08191402_5211a6e08c57b.jpg
2752 ms
11261127_54753a9ff2f8d.jpg
2795 ms
12162100_5671524425f25.jpg
3282 ms
08191507_5211b61736a23.gif
2898 ms
02020845_56afedfc64d24.jpg
3270 ms
09020807_55e62faad0267.jpg
3279 ms
09020805_55e62f49a96e0.jpg
3358 ms
08181151_55d29dae4d47a.gif
3181 ms
title_03.gif
3274 ms
mediainfo_banner.png
4335 ms
02161618_56c2cd44406ef.gif
3641 ms
conversion.js
646 ms
01261055_56a6d2183f8c7.gif
3516 ms
05011559_5543246de3a00.gif
3512 ms
btn_bloc_login.png
3368 ms
btn_entry.png
3361 ms
bnr_detail_mypage_out.jpg
3614 ms
bnr_detail_guide.jpg
3520 ms
21590biginner.gif
3523 ms
215-90story2.gif
3472 ms
1072 ms
53 ms
50 ms
60 ms
57 ms
53 ms
widgets.js
82 ms
63 ms
64 ms
gtm.js
51 ms
62 ms
59 ms
59 ms
34 ms
1002 ms
_webantenna.png
167 ms
27 ms
16bb_215x90.jpg
3564 ms
analytics.js
20 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
136 ms
collect
13 ms
collect
6 ms
akmedi215-902.gif
3545 ms
160208orange_215x180.jpg
4030 ms
syndication
104 ms
387181011211014146
217 ms
footernavi_search.gif
3519 ms
2665.png
23 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
27 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
120 ms
LBNGo-jT_normal.png
144 ms
CX70rgdVAAALP7b.jpg:small
137 ms
CLP0_ETUsAAAnAx.jpg:small
139 ms
CI-3PLgUwAAoj-M.jpg:small
221 ms
B6oH7rCCYAMpd-Z.jpg:small
261 ms
B6lGU5XCUAIkSDg.jpg:small
303 ms
B5cfX1yCIAAhHPv.jpg:small
272 ms
home.png
3139 ms
jot
27 ms
pagetop.png
3009 ms
icon_login.gif
2984 ms
icon_mypage.gif
3010 ms
icon_submit.gif
2958 ms
icon_guide.gif
2766 ms
icon_sitemap.gif
2820 ms
search.png
2785 ms
marker.gif
2820 ms
footer_arrow.png
2718 ms
current.gif
2739 ms
standard.css
210 ms
small.css
398 ms
big.css
419 ms
rosette.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
rosette.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
rosette.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document doesn't use legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rosette.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 Rosette.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.
rosette.jp
Open Graph description is not detected on the main page of ROSETTE. 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: