Tools & Wizards About Us
jellybean.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

jellybean.jp

ロリポップ！レンタルサーバー | 利用実績170万人突破！無料SSLあり

Page Load Speed

11.7 sec in total

First Response

495 ms

Resources Loaded

10.8 sec

Page Rendered

356 ms

jellybean.jp screenshot

About Website

Visit jellybean.jp now to see the best up-to-date Jellybean content for Japan and also check out these interesting facts you probably never knew about jellybean.jp

ホームページ運営なら、ずっと使えるレンタルサーバー「ロリポップ！」簡単、無料SSL、充実サポート、高速性能で、初心者から商用サイトまで安心してご利用いただけます。WordPress、EC-CUBEもたったの60秒で設置可能。無料お試し10日間。

Visit jellybean.jp

Key Findings

We analyzed Jellybean.jp page load time and found that the first response time was 495 ms and then it took 11.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

jellybean.jp performance score

0

Network Requests Diagram

jellybean.jp

495 ms

lolipop.jp

1183 ms

default.css

309 ms

common.css

631 ms

background.css

488 ms

Our browser made a total of 133 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Jellybean.jp, 53% (71 requests) were made to Lolipop.jp and 8% (11 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (3.8 sec) relates to the external source Lolipop.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 440.4 kB (37%)

Content Size

1.2 MB

After Optimization

766.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jellybean.jp main page is 1.2 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 707.6 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 142.9 kB

  • Original 167.5 kB
  • After minification 157.4 kB
  • After compression 24.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. 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 142.9 kB or 85% of the original size.

Image Optimization

-18%

Potential reduce by 125.4 kB

  • Original 707.6 kB
  • After minification 582.1 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. Obviously, Jellybean needs image optimization as it can save up to 125.4 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-34%

Potential reduce by 73.7 kB

  • Original 214.9 kB
  • After minification 214.2 kB
  • After compression 141.3 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 73.7 kB or 34% of the original size.

CSS Optimization

-85%

Potential reduce by 98.4 kB

  • Original 116.5 kB
  • After minification 86.2 kB
  • After compression 18.0 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. Jellybean.jp needs all CSS files to be minified and compressed as it can save up to 98.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (55%)

Requests Now

114

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jellybean.jp

jellybean.jp

495 ms

lolipop.jp

lolipop.jp

1183 ms

default.css

default.css

309 ms

common.css

common.css

631 ms

background.css

background.css

488 ms

text_m.css

text_m.css

487 ms

home.css

home.css

492 ms

lightbox.css

lightbox.css

503 ms

owl.carousel.css

owl.carousel.css

1392 ms

jquery.min.js

jquery.min.js

83 ms

base.js

base.js

2410 ms

lightbox.min.js

lightbox.min.js

2253 ms

owl.carousel.min.js

owl.carousel.min.js

2426 ms

home.js

home.js

3236 ms

scrollReveal.min.js

scrollReveal.min.js

3227 ms

pixel.js

pixel.js

623 ms

mixpanel.js

mixpanel.js

3262 ms

fbds.js

fbds.js

171 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

249 ms

bg_body.gif

bg_body.gif

1983 ms

close.png

close.png

1989 ms

loading.gif

loading.gif

1992 ms

prev.png

prev.png

2127 ms

next.png

next.png

2140 ms

bg_content_side.png

bg_content_side.png

2183 ms

bg_main_bottom.gif

bg_main_bottom.gif

2187 ms

bg_main_1column.png

bg_main_1column.png

2488 ms

bg_submenu_top.gif

bg_submenu_top.gif

2514 ms

h2_home_title.png

h2_home_title.png

2832 ms

megaphone.svg

megaphone.svg

2528 ms

obj_home_plan_economy.svg

obj_home_plan_economy.svg

2520 ms

obj_home_plan_lite.svg

obj_home_plan_lite.svg

2574 ms

obj_home_plan_standard.svg

obj_home_plan_standard.svg

3033 ms

obj_home_plan_ribbon.svg

obj_home_plan_ribbon.svg

3036 ms

obj_home_plan_enterprise.svg

obj_home_plan_enterprise.svg

3028 ms

btn_home_plan_function_detail.png

btn_home_plan_function_detail.png

3162 ms

btn_home_plan_price_detail.png

btn_home_plan_price_detail.png

3031 ms

bnr_lolipop_nextgen_201601.png

bnr_lolipop_nextgen_201601.png

3474 ms

h3_home_title.png

h3_home_title.png

3609 ms

obj_home_feature_wordpress.png

obj_home_feature_wordpress.png

3459 ms

line_dot_11.gif

line_dot_11.gif

3146 ms

obj_home_feature_backup.png

obj_home_feature_backup.png

3553 ms

obj_home_feature_utilization.png

obj_home_feature_utilization.png

3471 ms

obj_home_feature_support.png

obj_home_feature_support.png

3662 ms

h3_home_functions.png

h3_home_functions.png

3620 ms

obj_home_functions_list.png

obj_home_functions_list.png

3794 ms

btn_feature._function_detail.png

btn_feature._function_detail.png

3636 ms

btn_infomation_more.png

btn_infomation_more.png

3738 ms

badge_light.png

badge_light.png

245 ms

widgets.js

widgets.js

73 ms

line_dot_02.gif

line_dot_02.gif

3665 ms

51 ms

25 ms

icon_star.gif

icon_star.gif

2806 ms

dc.js

dc.js

67 ms

btn_h_serch.png

btn_h_serch.png

2648 ms

line_dot_08.gif

line_dot_08.gif

2680 ms

__utm.gif

__utm.gif

23 ms

__utm.gif

__utm.gif

12 ms

__utm.gif

__utm.gif

21 ms

__utm.gif

__utm.gif

29 ms

btn_pagetop.gif

btn_pagetop.gif

1970 ms

obj_lolipop_logo.png

obj_lolipop_logo.png

2125 ms

obj_ojisan_normal.png

obj_ojisan_normal.png

2128 ms

obj_header_banner_text.png

obj_header_banner_text.png

2182 ms

btn_header_order.png

btn_header_order.png

2248 ms

bg_header_simple.png

bg_header_simple.png

2385 ms

obj_ppb_by_logo.png

obj_ppb_by_logo.png

1783 ms

obj_order_count_text.png

obj_order_count_text.png

1837 ms

obj_numbers.png

obj_numbers.png

1876 ms

menu_btn.png

menu_btn.png

2063 ms

menu_dot.gif

menu_dot.gif

1905 ms

pixel

pixel

152 ms

pixel

pixel

55 ms

Pug

Pug

84 ms

sync.ad-stir.com

sync.ad-stir.com

634 ms

sync

sync

55 ms

sync

sync

1103 ms

is

is

1205 ms

headerstyle.min.css

headerstyle.min.css

216 ms

pixel

pixel

22 ms

sd

sd

13 ms

google

google

202 ms

arrow_menu.gif

arrow_menu.gif

1698 ms

tag.js

tag.js

59 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

12 ms

obj_logo_ppb.png

obj_logo_ppb.png

1553 ms

obj_prev_item_icon.png

obj_prev_item_icon.png

1560 ms

obj_next_item_icon.png

obj_next_item_icon.png

1616 ms

obj_dhw_ac_jp_thumb.jpg

obj_dhw_ac_jp_thumb.jpg

1830 ms

tag

tag

42 ms

follow_button.6a78875565a912489e9aef879c881358.ja.html

follow_button.6a78875565a912489e9aef879c881358.ja.html

23 ms

obj_mtblanc_jp_thumb.jpg

obj_mtblanc_jp_thumb.jpg

1743 ms

obj_foresthuntingone_com_thumb.jpg

obj_foresthuntingone_com_thumb.jpg

1795 ms

jot

jot

89 ms

obj_sakelife_jp_thumb.jpg

obj_sakelife_jp_thumb.jpg

1452 ms

lolipop.jp

lolipop.jp

1476 ms

lolipop.jp

lolipop.jp

2739 ms

lolipop.jp

lolipop.jp

2003 ms

lolipop.jp

lolipop.jp

2215 ms

lolipop.jp

lolipop.jp

1013 ms

nr-768.min.js

nr-768.min.js

73 ms

roundtrip.js

roundtrip.js

41 ms

btn.png

btn.png

32 ms

conversion_async.js

conversion_async.js

59 ms

15 ms

logo201601.png

logo201601.png

53 ms

open_footer.png

open_footer.png

82 ms

close_footer.png

close_footer.png

111 ms

39 ms

conversion.js

conversion.js

975 ms

15936ac739

15936ac739

122 ms

QGNG2UAG2ZAKJNSEXUXBMN.js

QGNG2UAG2ZAKJNSEXUXBMN.js

106 ms

42 ms

out

out

14 ms

tr

tr

11 ms

out

out

10 ms

out

out

24 ms

out

out

26 ms

out

out

30 ms

out

out

28 ms

out

out

25 ms

out

out

31 ms

out

out

31 ms

29 ms

u.php

u.php

39 ms

sd

sd

14 ms

sd

sd

41 ms

Pug

Pug

28 ms

in

in

7 ms

377928.gif

377928.gif

7 ms

tap.php

tap.php

21 ms

in

in

6 ms

SEO Factors

jellybean.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

jellybean.jp

Open Graph data is detected on the main page of Jellybean. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: