Tools & Wizards About Us
e-biken.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

e-biken.co.jp

デイリーアロマジャパン｜創業35年。信頼と実績のアロマ専門メーカーです。

Page Load Speed

8.5 sec in total

First Response

1.6 sec

Resources Loaded

6.4 sec

Page Rendered

559 ms

e-biken.co.jp screenshot

About Website

Visit e-biken.co.jp now to see the best up-to-date E Biken content for Japan and also check out these interesting facts you probably never knew about e-biken.co.jp

信頼と実績のアロマ専門メーカーです。アロマオイル、ECOCERT認定のオーガニック商品、高知県産ゆず、瀬戸内レモン、北海道和ハッカシリーズやサロン用業務商品を、雑貨店様やアロマサロン、リラクゼーション、ネイルサロン、整体、美容室様に卸しています。

Visit e-biken.co.jp

Key Findings

We analyzed E-biken.co.jp page load time and found that the first response time was 1.6 sec and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

e-biken.co.jp performance score

0

Network Requests Diagram

www.e-biken.co.jp

1558 ms

style.css

378 ms

jquery.min.js

69 ms

jquery.min.js

585 ms

skel.min.js

329 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 95% of them (71 requests) were addressed to the original E-biken.co.jp, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain E-biken.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 281.9 kB (9%)

Content Size

3.0 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of E-biken.co.jp main page is 3.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. 60% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 28.5 kB

  • Original 34.6 kB
  • After minification 28.0 kB
  • After compression 6.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 6.6 kB, which is 19% 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 28.5 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 58.3 kB

  • Original 2.7 MB
  • After minification 2.6 MB

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. E Biken images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 80.7 kB

  • Original 137.2 kB
  • After minification 130.7 kB
  • After compression 56.5 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 80.7 kB or 59% of the original size.

CSS Optimization

-83%

Potential reduce by 114.3 kB

  • Original 137.2 kB
  • After minification 111.3 kB
  • After compression 22.9 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. E-biken.co.jp needs all CSS files to be minified and compressed as it can save up to 114.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (19%)

Requests Now

73

After Optimization

59

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E Biken. 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 from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.e-biken.co.jp

www.e-biken.co.jp

1558 ms

style.css

style.css

378 ms

jquery.min.js

jquery.min.js

69 ms

jquery.min.js

jquery.min.js

585 ms

skel.min.js

skel.min.js

329 ms

util.js

util.js

360 ms

main.js

main.js

350 ms

nav.js

nav.js

354 ms

font-awesome.min.css

font-awesome.min.css

461 ms

css

css

24 ms

reset.css

reset.css

319 ms

liquid.css

liquid.css

526 ms

head.css

head.css

536 ms

bacs.css

bacs.css

561 ms

set.css

set.css

710 ms

mobile.css

mobile.css

604 ms

ie8.css

ie8.css

670 ms

ga.js

ga.js

87 ms

head_rogo.png

head_rogo.png

197 ms

head_mail.png

head_mail.png

189 ms

head_tel.png

head_tel.png

179 ms

head_fax.png

head_fax.png

213 ms

main_v.jpg

main_v.jpg

1221 ms

news_ti.png

news_ti.png

356 ms

news_list.jpg

news_list.jpg

377 ms

lemon.jpg

lemon.jpg

390 ms

soup.jpg

soup.jpg

412 ms

tenjikai.jpg

tenjikai.jpg

422 ms

Chapter01_122.jpg

Chapter01_122.jpg

534 ms

lf.jpg

lf.jpg

564 ms

ae46b1f460ee46f789c27b264a6cb421.jpg

ae46b1f460ee46f789c27b264a6cb421.jpg

584 ms

0a106d3a1aa1923ae658eb6a1c4ce913-150x150.jpg

0a106d3a1aa1923ae658eb6a1c4ce913-150x150.jpg

618 ms

oil_ran11.jpg

oil_ran11.jpg

633 ms

nighttop2.jpg

nighttop2.jpg

887 ms

top_eco_bg.jpg

top_eco_bg.jpg

751 ms

top_ecocert.jpg

top_ecocert.jpg

778 ms

top_oil_m.jpg

top_oil_m.jpg

824 ms

top_oil_t.jpg

top_oil_t.jpg

844 ms

top_oil_img.jpg

top_oil_img.jpg

939 ms

top_oil_b.jpg

top_oil_b.jpg

972 ms

top_h2_new.jpg

top_h2_new.jpg

1028 ms

new.png

new.png

1054 ms

new_01.jpg

new_01.jpg

1631 ms

more.jpg

more.jpg

1126 ms

new_02.jpg

new_02.jpg

1359 ms

new_03.jpg

new_03.jpg

2055 ms

new_04.jpg

new_04.jpg

1685 ms

sesen_01.jpg

sesen_01.jpg

1876 ms

sesen_02.jpg

sesen_02.jpg

1565 ms

sesen_03.jpg

sesen_03.jpg

1748 ms

sesen_04.jpg

sesen_04.jpg

1913 ms

item_01.jpg

item_01.jpg

2162 ms

item_02.jpg

item_02.jpg

2324 ms

item_03.jpg

item_03.jpg

2073 ms

__utm.gif

__utm.gif

11 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2077 ms

item_04.jpg

item_04.jpg

2086 ms

item_05.jpg

item_05.jpg

2480 ms

item_06.jpg

item_06.jpg

2319 ms

item_07.jpg

item_07.jpg

2163 ms

item_08.jpg

item_08.jpg

2444 ms

item_09.jpg

item_09.jpg

2226 ms

item_10.jpg

item_10.jpg

2331 ms

item_11.jpg

item_11.jpg

2455 ms

item_12.jpg

item_12.jpg

2386 ms

overlay.png

overlay.png

2228 ms

bg02.png

bg02.png

2298 ms

rogo.png

rogo.png

2337 ms

ecocert_oil.png

ecocert_oil.png

2333 ms

side_mail.gif

side_mail.gif

2256 ms

side_tel.gif

side_tel.gif

2275 ms

side_salon.png

side_salon.png

2263 ms

side_online.png

side_online.png

2272 ms

side_member.png

side_member.png

2279 ms

side_newcatalog.jpg

side_newcatalog.jpg

2200 ms

SEO Factors

e-biken.co.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-biken.co.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 E-biken.co.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.

Social Sharing Optimization

e-biken.co.jp

Open Graph description is not detected on the main page of E Biken. 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: