6.7 sec in total
1 sec
5.4 sec
280 ms
Click here to check amazing EraL content for Japan. Otherwise, check out these important facts you probably never knew about eral.co.jp
イーラルは、植物と科学のチカラを徹底的に研究し、髪の美しさを土台から創り出すことを目的としたブランドです。頭皮と髪の内部※1まで水をめぐらせ、人が本来持つ機能を助け、なりたい質感に導きます。
Visit eral.co.jpWe analyzed Eral.co.jp page load time and found that the first response time was 1 sec and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
eral.co.jp performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value34.6 s
0/100
25%
Value19.9 s
0/100
10%
Value2,370 ms
5/100
30%
Value0.82
4/100
15%
Value44.1 s
0/100
10%
1013 ms
359 ms
571 ms
1347 ms
391 ms
Our browser made a total of 126 requests to load all elements on the main page. We found that 54% of them (68 requests) were addressed to the original Eral.co.jp, 17% (21 requests) were made to Static.xx.fbcdn.net and 8% (10 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Eral.co.jp.
Page size can be reduced by 214.4 kB (12%)
1.8 MB
1.6 MB
In fact, the total size of Eral.co.jp main page is 1.8 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. 70% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 33.6 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 6.2 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 33.6 kB or 77% of the original size.
Potential reduce by 20.3 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. EraL images are well optimized though.
Potential reduce by 127.0 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 127.0 kB or 63% of the original size.
Potential reduce by 33.5 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. Eral.co.jp needs all CSS files to be minified and compressed as it can save up to 33.5 kB or 83% of the original size.
Number of requests can be reduced by 56 (45%)
124
68
The browser has sent 124 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EraL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
eral.co.jp
1013 ms
import_new.css
359 ms
home_new.css
571 ms
jquery.js
1347 ms
common.js
391 ms
scrolltopcontrol.js
394 ms
smp.js
362 ms
slider.css
405 ms
jquery-latest.js
8 ms
easySlider1.7.js
997 ms
flexslider.css
719 ms
jquery.flexslider-min.js
736 ms
reset.css
400 ms
base_new2.css
849 ms
facebook.css
589 ms
goSalon.css
720 ms
widgets.js
83 ms
getseal
99 ms
plusone.js
65 ms
ga.js
33 ms
convert.js
596 ms
bg_body.gif
214 ms
button_business.gif
213 ms
main_premier.jpg
1019 ms
main_purehaire.jpg
831 ms
main_aquabalance.jpg
1001 ms
main_prime.jpg
1516 ms
3.jpg
1466 ms
info_banner02.jpg
941 ms
info_banner01.jpg
1032 ms
banner_salon.gif
1129 ms
title_saloninfo.gif
1194 ms
main.jpg
1411 ms
main.jpg
1419 ms
main.jpg
1497 ms
main.jpg
1578 ms
main.jpg
1799 ms
main.jpg
1801 ms
main.jpg
1822 ms
main.jpg
1862 ms
main.jpg
1886 ms
main.jpg
1965 ms
main.jpg
2190 ms
main.jpg
2181 ms
main.jpg
2178 ms
main.jpg
2228 ms
main.jpg
2260 ms
main.jpg
2351 ms
main.jpg
2361 ms
main.jpg
2375 ms
main.jpg
2387 ms
main.jpg
2595 ms
banner_voice.jpg
2452 ms
banner_aging.jpg
2549 ms
banner_care.jpg
2543 ms
button_new.gif
2568 ms
sdk.js
71 ms
top3.php
2612 ms
__utm.gif
24 ms
getseal
112 ms
cb=gapi.loaded_0
47 ms
cb=gapi.loaded_1
80 ms
fastbutton
117 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
148 ms
like.php
167 ms
160 ms
xd_arbiter.php
48 ms
xd_arbiter.php
72 ms
postmessageRelay
63 ms
flexslider-icon.woff
2434 ms
icon_pagetop.gif
2516 ms
cb=gapi.loaded_0
18 ms
cb=gapi.loaded_1
16 ms
page.php
331 ms
3193398744-postmessagerelay.js
22 ms
rpc:shindig_random.js
37 ms
cb=gapi.loaded_0
8 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
53 ms
qeKvIRsJabD.js
70 ms
LVx-xkvaJ0b.png
67 ms
jot
133 ms
SwWqNEM2GQB.css
23 ms
qfDTH5pB6Ut.css
10 ms
drXqyuWvz8i.css
26 ms
3FAK8vb1hBH.css
26 ms
q68gy-v_YMF.js
36 ms
ehA1CqzHyzE.js
53 ms
0wM5s1Khldu.js
49 ms
1bNoFZUdlYZ.js
48 ms
njO1TPvGzoR.js
32 ms
1QuX41zDRrx.js
65 ms
Oagsvfb4VWi.js
64 ms
LTv6ZK-5zxz.js
70 ms
1FCa-btixu2.js
62 ms
pv_beacon.gif
358 ms
581557_416407018371047_1744563593_n.jpg
99 ms
12794475_1132878173390591_7348110975471017698_n.jpg
75 ms
10342500_1130078650337210_7839162053588905035_n.jpg
14 ms
10628072_1130078643670544_8612636721328340826_n.jpg
13 ms
8453_1131527616858980_8399699493649280146_n.jpg
15 ms
12798940_1127163907295351_6692034702897400341_n.jpg
97 ms
1897973_1127163947295347_7513036705669104542_n.jpg
29 ms
12802962_1126748647336877_1671511677524722284_n.jpg
16 ms
12806255_1126748770670198_6680345777338003631_n.jpg
132 ms
12790925_1126748707336871_3975704921521923220_n.jpg
83 ms
wL6VQj7Ab77.png
10 ms
s7jcwEQH7Sx.png
7 ms
QDwYpIaRyfG.png
8 ms
K00K-UgnsKu.png
7 ms
logo_foot.gif
1917 ms
I6-MnjEovm5.js
4 ms
pQrUxxo5oQp.js
5 ms
page_bg.gif
1822 ms
logo2.gif
1784 ms
info_bg.gif
1797 ms
title_new.gif
1803 ms
bg_foot01.gif
1780 ms
bg_foot04.gif
1747 ms
bg_foot02.gif
1543 ms
slide_l.gif
1549 ms
slide_r.gif
1543 ms
newstop.css
404 ms
flexcrollstyles.css
470 ms
flexcroll.js
518 ms
bg_news.gif
186 ms
scrollbar2.gif
185 ms
eral.co.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
eral.co.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
eral.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eral.co.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 Eral.co.jp main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
eral.co.jp
Open Graph description is not detected on the main page of EraL. 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: