6.4 sec in total
784 ms
5.3 sec
310 ms
Click here to check amazing LUCIDO content for Japan. Otherwise, check out these important facts you probably never knew about lucido.jp
40才からの「LUCIDO(ルシード)」公式サイト。商品情報と使い方、40才からの肌・ニオイ・スタイリング・白髪の変化や悩みにお応えします。
Visit lucido.jpWe analyzed Lucido.jp page load time and found that the first response time was 784 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
lucido.jp performance score
name
value
score
weighting
Value10.3 s
0/100
10%
Value13.7 s
0/100
25%
Value22.4 s
0/100
10%
Value15,890 ms
0/100
30%
Value0.545
13/100
15%
Value40.8 s
0/100
10%
784 ms
1223 ms
1238 ms
594 ms
597 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 38% of them (21 requests) were addressed to the original Lucido.jp, 7% (4 requests) were made to M.one.impact-ad.jp and 5% (3 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Lucido.jp.
Page size can be reduced by 540.6 kB (22%)
2.5 MB
2.0 MB
In fact, the total size of Lucido.jp main page is 2.5 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. 35% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 37.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 37.8 kB or 80% of the original size.
Potential reduce by 141.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. LUCIDO images are well optimized though.
Potential reduce by 217.3 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 217.3 kB or 67% of the original size.
Potential reduce by 144.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. Lucido.jp needs all CSS files to be minified and compressed as it can save up to 144.3 kB or 85% of the original size.
Number of requests can be reduced by 24 (49%)
49
25
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LUCIDO. 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 as a result speed up the page load time.
lucido.jp
784 ms
pc.css
1223 ms
vendor.js
1238 ms
common.js
594 ms
top.js
597 ms
matm.js
1094 ms
ir
348 ms
styling-large.jpg
462 ms
products-smellcare.jpg
596 ms
products-facecare.jpg
314 ms
products-styling.jpg
171 ms
products-hair_dye.jpg
598 ms
banner-styling.jpg
331 ms
banner-middlesmell.jpg
1032 ms
banner-extra.jpg
469 ms
sdk.js
25 ms
common-s8cd2f54202.png
483 ms
top-sd515c80424.png
2631 ms
widgets.js
31 ms
tracking.js
490 ms
118 ms
xd_arbiter.php
48 ms
xd_arbiter.php
52 ms
advmap.js
279 ms
mone.2eb31eff690_758.js
756 ms
RANDOM=51998826
365 ms
analytics.js
33 ms
sub_177.js
350 ms
combo
522 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
19 ms
1.jpg
993 ms
2.jpg
468 ms
3.jpg
783 ms
4.jpg
1003 ms
5.jpg
1772 ms
6.jpg
778 ms
linkid.js
16 ms
collect
13 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
12 ms
unsupportedbrowser
67 ms
jot
90 ms
pixel
20 ms
pixel
16 ms
pb.html
40 ms
pix
294 ms
pix
314 ms
pix
384 ms
pix
398 ms
pixel
15 ms
332 ms
665 ms
304 ms
161 ms
sync
16 ms
rep
147 ms
lucido.jp accessibility score
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
Links do not have a discernible name
lucido.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
lucido.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lucido.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lucido.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.
lucido.jp
Open Graph data is detected on the main page of LUCIDO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: