Tools & Wizards About Us
acai.jp.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

acai.jp.net

Page Load Speed

5.4 sec in total

First Response

1.1 sec

Resources Loaded

4.1 sec

Page Rendered

177 ms

acai.jp.net screenshot

About Website

Click here to check amazing Acai content for Japan. Otherwise, check out these important facts you probably never knew about acai.jp.net

アマゾンフルーツアサイージュースのZolaオフィシャルサイト。有機JAS認定のカラダにいい商品をお届けします。

Visit acai.jp.net

Key Findings

We analyzed Acai.jp.net page load time and found that the first response time was 1.1 sec and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

acai.jp.net performance score

0

Network Requests Diagram

acai.jp.net

1129 ms

common.css

653 ms

top.css

690 ms

function.js

347 ms

styleswitcher.js

350 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 64% of them (44 requests) were addressed to the original Acai.jp.net, 14% (10 requests) were made to Static.xx.fbcdn.net and 10% (7 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Acai.jp.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 54.3 kB (8%)

Content Size

683.4 kB

After Optimization

629.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Acai.jp.net main page is 683.4 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. 40% of websites need less resources to load. Images take 603.5 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 18.6 kB

  • Original 24.9 kB
  • After minification 21.7 kB
  • After compression 6.4 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 3.3 kB, which is 13% 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 18.6 kB or 74% of the original size.

Image Optimization

-1%

Potential reduce by 3.7 kB

  • Original 603.5 kB
  • After minification 599.7 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. Acai images are well optimized though.

JavaScript Optimization

-26%

Potential reduce by 6.5 kB

  • Original 25.2 kB
  • After minification 22.3 kB
  • After compression 18.7 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 6.5 kB or 26% of the original size.

CSS Optimization

-86%

Potential reduce by 25.5 kB

  • Original 29.8 kB
  • After minification 20.8 kB
  • After compression 4.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. Acai.jp.net needs all CSS files to be minified and compressed as it can save up to 25.5 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

65

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Acai. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

acai.jp.net

acai.jp.net

1129 ms

common.css

common.css

653 ms

top.css

top.css

690 ms

function.js

function.js

347 ms

styleswitcher.js

styleswitcher.js

350 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

530 ms

headbg.jpg

headbg.jpg

180 ms

logo.gif

logo.gif

182 ms

index_05.jpg

index_05.jpg

526 ms

main_bg.jpg

main_bg.jpg

178 ms

index_button.gif

index_button.gif

170 ms

top_menu0.gif

top_menu0.gif

183 ms

top_menu1.gif

top_menu1.gif

334 ms

top_menu2.gif

top_menu2.gif

349 ms

top_menu3.gif

top_menu3.gif

353 ms

top_menu4.gif

top_menu4.gif

350 ms

header_menu1.gif

header_menu1.gif

356 ms

header_menu2.gif

header_menu2.gif

494 ms

header_menu3.gif

header_menu3.gif

523 ms

header_menu4.gif

header_menu4.gif

521 ms

header_menu5.gif

header_menu5.gif

529 ms

header_menu6.gif

header_menu6.gif

531 ms

common_mainbg.gif

common_mainbg.gif

655 ms

top_side1.gif

top_side1.gif

696 ms

top_side3.gif

top_side3.gif

698 ms

top_side4.jpg

top_side4.jpg

1242 ms

top_banner_m.png

top_banner_m.png

1670 ms

index_50.jpg

index_50.jpg

899 ms

index_52.jpg

index_52.jpg

1337 ms

index_56.jpg

index_56.jpg

1773 ms

side_bana_r4_1.jpg

side_bana_r4_1.jpg

1242 ms

side_bana_r3_1.jpg

side_bana_r3_1.jpg

1448 ms

side_bana_r2.gif

side_bana_r2.gif

1424 ms

s1ide_bana_r.gif

s1ide_bana_r.gif

1430 ms

side_bana_m1.jpg

side_bana_m1.jpg

1695 ms

media_bana.png

media_bana.png

1792 ms

side_bana_m2.gif

side_bana_m2.gif

1614 ms

side_bana_r5_1.jpg

side_bana_r5_1.jpg

1632 ms

gotop.gif

gotop.gif

1793 ms

common_contentsbg.gif

common_contentsbg.gif

1803 ms

top_voicemediabg.gif

top_voicemediabg.gif

1840 ms

all.js

all.js

11 ms

footer_bg.gif

footer_bg.gif

1847 ms

ga.js

ga.js

21 ms

129 ms

__utm.gif

__utm.gif

57 ms

xd_arbiter.php

xd_arbiter.php

39 ms

xd_arbiter.php

xd_arbiter.php

54 ms

images_usa.jpg

images_usa.jpg

1785 ms

Plain_wht_Right.gif

Plain_wht_Right.gif

1792 ms

ping

ping

45 ms

like_box.php

like_box.php

281 ms

hQThvcX2PmE.css

hQThvcX2PmE.css

47 ms

t3u7Vo4PVNb.css

t3u7Vo4PVNb.css

50 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

62 ms

ehA1CqzHyzE.js

ehA1CqzHyzE.js

61 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

59 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

56 ms

181449_453539684657742_542847256_n.jpg

181449_453539684657742_542847256_n.jpg

52 ms

523799_468487953162915_2110720779_n.jpg

523799_468487953162915_2110720779_n.jpg

41 ms

12391000_543315235837733_697066534991874205_n.jpg

12391000_543315235837733_697066534991874205_n.jpg

140 ms

198015_102340886603474_1419742070_n.jpg

198015_102340886603474_1419742070_n.jpg

28 ms

12313782_773813849430805_2506109649725769060_n.jpg

12313782_773813849430805_2506109649725769060_n.jpg

16 ms

180348_109196882491223_3155908_n.jpg

180348_109196882491223_3155908_n.jpg

12 ms

10411975_1632794233611605_8633436606906216639_n.jpg

10411975_1632794233611605_8633436606906216639_n.jpg

14 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

9 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

8 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

11 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

4 ms

SEO Factors

acai.jp.net SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Acai.jp.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Acai.jp.net main page’s claimed encoding is shift_jis. 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.

Social Sharing Optimization

acai.jp.net

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