5.3 sec in total
1 sec
3.9 sec
343 ms
Click here to check amazing EsLASH content. Otherwise, check out these important facts you probably never knew about es-lash.jp
まつげエクステ,エスラッシュ,esLASH
Visit es-lash.jpWe analyzed Es-lash.jp page load time and found that the first response time was 1 sec and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
es-lash.jp performance score
name
value
score
weighting
Value2.7 s
58/100
10%
Value20.7 s
0/100
25%
Value7.4 s
27/100
10%
Value110 ms
97/100
30%
Value0.423
23/100
15%
Value12.9 s
13/100
10%
1033 ms
357 ms
53 ms
395 ms
180 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 55% of them (51 requests) were addressed to the original Es-lash.jp, 14% (13 requests) were made to Es-nail.jp and 14% (13 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Es-lash.jp.
Page size can be reduced by 111.1 kB (12%)
960.5 kB
849.3 kB
In fact, the total size of Es-lash.jp main page is 960.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 905.7 kB which makes up the majority of the site volume.
Potential reduce by 13.2 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 13.2 kB or 80% of the original size.
Potential reduce by 81.4 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. EsLASH images are well optimized though.
Potential reduce by 231 B
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.
Potential reduce by 16.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. Es-lash.jp needs all CSS files to be minified and compressed as it can save up to 16.3 kB or 79% of the original size.
Number of requests can be reduced by 25 (27%)
91
66
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EsLASH. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
es-lash.jp
1033 ms
import.css
357 ms
jsapi
53 ms
ga.js
395 ms
default.css
180 ms
base.css
402 ms
jquery.min.js
63 ms
ga.js
87 ms
body_bg.png
193 ms
footer_shop_shibuya.jpg
1063 ms
eslash_logo.png
360 ms
grandopen011.png
1178 ms
gnav.png
346 ms
footlash_bn.jpg
1272 ms
170_207anshin.png
505 ms
170shibuya_bn.png
368 ms
170akihabara_bn.png
601 ms
170nakame_bn.png
599 ms
170shinjuku_bn.png
601 ms
170kamata_bn.png
671 ms
170omori_bn.png
688 ms
170ogikubo_bn.png
709 ms
170yokohama_bn.png
724 ms
170omiya_bn.png
839 ms
170chiba_bn.png
860 ms
170nagoya_bn.png
887 ms
170fukuoka_bn.png
903 ms
blog_bn.png
1846 ms
aikoblog_bn.png
1719 ms
footer_bg.gif
1065 ms
shibuya.png
1083 ms
shinjuku.png
1242 ms
ikebukuro.png
1262 ms
roppongi.png
1366 ms
kichijoji.png
1420 ms
omiya.png
1442 ms
nagoya.png
1667 ms
osaka.png
1563 ms
los.png
1598 ms
la.png
1621 ms
shibuya_lash.png
1759 ms
dogenzaka_lash.png
1776 ms
dogenzaka.png
2016 ms
nakameguro_lash.png
1839 ms
nakameguro.png
2230 ms
footer_shop_shinjuku.jpg
818 ms
footer_shop_ikebukuro.jpg
1025 ms
footer_shop_roppongi.jpg
1046 ms
footer_shop_kichijoji.jpg
865 ms
footer_shop_omiya.jpg
865 ms
footer_shop_nagoya.jpg
1376 ms
footer_shop_osaka.jpg
1460 ms
footer_shop_los.jpg
1237 ms
footer_shop_beverly.jpg
1334 ms
footer_lash_shibuya.png
1205 ms
footer_lash_omiya.png
1413 ms
footer_lash_nagoya.png
1383 ms
likebox.php
121 ms
__utm.gif
15 ms
kamata_lash.png
1841 ms
410ucuAGgaJ.css
172 ms
tSbl8xBI27R.css
214 ms
1kPfZUdGrka.js
297 ms
Yuj_Y8xNH2C.js
373 ms
Mpe38fuBVZ2.js
293 ms
n8qIhCw3vMx.js
292 ms
kamata.png
1838 ms
omori_lash.png
1668 ms
omori.png
1655 ms
ogikubo_lash.png
1660 ms
564096_456379181081303_907366395_n.png
380 ms
398229_453883171330904_1234174708_n.jpg
419 ms
12038025_149151075435162_4857110036252656102_n.jpg
460 ms
12107181_754968197967039_5639820298310275439_n.jpg
496 ms
1013532_928949877185206_2867052938296844327_n.jpg
498 ms
11220797_710821312353371_8493107818858055353_n.jpg
541 ms
1538716_459824950806302_173721649_n.jpg
498 ms
375469_207483732670470_19543031_n.jpg
496 ms
12079667_664930690316019_7903808833273109738_n.jpg
501 ms
12662567_1684791065132514_9001805855661045445_n.jpg
535 ms
12552506_167975746900964_7588726514059819203_n.jpg
538 ms
11701023_1455197868115171_680185776454617391_n.jpg
537 ms
734949_1712027709014176_889309491256434578_n.jpg
573 ms
wL6VQj7Ab77.png
47 ms
s7jcwEQH7Sx.png
46 ms
ogikubo.png
1589 ms
omiya_lash.png
1599 ms
chiba_lash.png
1605 ms
chiba.png
1689 ms
nagoya_lash.png
1670 ms
VXcANLwwL5J.js
50 ms
AmlxWlqMvlv.js
42 ms
es-lash.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
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
es-lash.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
es-lash.jp SEO score
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Es-lash.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 Es-lash.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.
es-lash.jp
Open Graph description is not detected on the main page of EsLASH. 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: