4.5 sec in total
561 ms
3.6 sec
350 ms
Click here to check amazing Lunerl content. Otherwise, check out these important facts you probably never knew about lunerl.jp
化粧品メーカーのLuNerL(ルネール)では、蜂の子配合美容液ハニードロップやエイジングケアクリームのリペアクリームなどBEAUL(ビュール)シリーズを展開しております。
Visit lunerl.jpWe analyzed Lunerl.jp page load time and found that the first response time was 561 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
lunerl.jp performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value8.1 s
2/100
25%
Value7.2 s
30/100
10%
Value290 ms
80/100
30%
Value0.282
43/100
15%
Value7.7 s
45/100
10%
561 ms
991 ms
513 ms
346 ms
10 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 92% of them (45 requests) were addressed to the original Lunerl.jp, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Lunerl.jp.
Page size can be reduced by 37.2 kB (2%)
1.6 MB
1.6 MB
In fact, the total size of Lunerl.jp main page is 1.6 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 1.5 MB which makes up the majority of the site volume.
Potential reduce by 10.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 2.8 kB, which is 20% 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 10.1 kB or 74% of the original size.
Potential reduce by 563 B
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. Lunerl images are well optimized though.
Potential reduce by 9.4 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 9.4 kB or 16% of the original size.
Potential reduce by 17.2 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. Lunerl.jp needs all CSS files to be minified and compressed as it can save up to 17.2 kB or 83% of the original size.
Number of requests can be reduced by 6 (13%)
47
41
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lunerl. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
lunerl.jp
561 ms
www.lunerl.jp
991 ms
base.css
513 ms
crossFader.css
346 ms
jquery.min.js
10 ms
jquery.crossFader.js
345 ms
rollover.js
348 ms
heightLine.js
350 ms
scrolltopcontrol.js
375 ms
analytics.js
73 ms
navi01.jpg
190 ms
navi02.jpg
176 ms
navi03.jpg
176 ms
logo.jpg
174 ms
navi04.jpg
173 ms
navi05.jpg
177 ms
navi06.jpg
344 ms
main_bg.jpg
346 ms
main01.jpg
1204 ms
main04.jpg
1044 ms
main_top.png
350 ms
top01.jpg
375 ms
top02.jpg
684 ms
top03.jpg
519 ms
top04.jpg
698 ms
top05.jpg
563 ms
top06.jpg
691 ms
top_bg.jpg
1499 ms
top07.jpg
1024 ms
top08.jpg
1206 ms
top09.jpg
873 ms
icon01.png
1049 ms
top10.jpg
1196 ms
top11.jpg
1216 ms
wn_icon02.jpg
1224 ms
detail_icon.jpg
1368 ms
wn_icon03.jpg
1374 ms
wn_icon04.jpg
1377 ms
wn_icon01.jpg
1390 ms
foot_logo.jpg
1398 ms
collect
32 ms
pagetop.png
1439 ms
js
64 ms
navi01_o.jpg
189 ms
navi02_o.jpg
174 ms
navi03_o.jpg
176 ms
navi04_o.jpg
174 ms
navi05_o.jpg
173 ms
navi06_o.jpg
177 ms
lunerl.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
Links do not have a discernible name
lunerl.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
lunerl.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
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lunerl.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 Lunerl.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.
lunerl.jp
Open Graph description is not detected on the main page of Lunerl. 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: