Tools & Wizards About Us
moo.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

moo.jp

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

Page Load Speed

11.3 sec in total

First Response

536 ms

Resources Loaded

10.4 sec

Page Rendered

433 ms

moo.jp screenshot

About Website

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

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

Visit moo.jp

Key Findings

We analyzed Moo.jp page load time and found that the first response time was 536 ms and then it took 10.8 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

moo.jp performance score

0

Network Requests Diagram

moo.jp

536 ms

lolipop.jp

1433 ms

default.css

350 ms

common.css

660 ms

background.css

513 ms

Our browser made a total of 134 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Moo.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 sec) relates to the external source Lolipop.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 440.1 kB (36%)

Content Size

1.2 MB

After Optimization

778.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Moo.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. 45% 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 143.2 kB

  • Original 168.1 kB
  • After minification 158.0 kB
  • After compression 24.9 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 143.2 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, Moo 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

-32%

Potential reduce by 73.0 kB

  • Original 226.2 kB
  • After minification 225.4 kB
  • After compression 153.2 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.0 kB or 32% 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. Moo.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 65 (57%)

Requests Now

115

After Optimization

50

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

moo.jp

moo.jp

536 ms

lolipop.jp

lolipop.jp

1433 ms

default.css

default.css

350 ms

common.css

common.css

660 ms

background.css

background.css

513 ms

text_m.css

text_m.css

510 ms

home.css

home.css

707 ms

lightbox.css

lightbox.css

536 ms

owl.carousel.css

owl.carousel.css

551 ms

jquery.min.js

jquery.min.js

69 ms

base.js

base.js

721 ms

lightbox.min.js

lightbox.min.js

516 ms

owl.carousel.min.js

owl.carousel.min.js

743 ms

home.js

home.js

664 ms

scrollReveal.min.js

scrollReveal.min.js

665 ms

pixel.js

pixel.js

799 ms

mixpanel.js

mixpanel.js

722 ms

fbds.js

fbds.js

245 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

122 ms

bg_body.gif

bg_body.gif

184 ms

close.png

close.png

326 ms

loading.gif

loading.gif

268 ms

prev.png

prev.png

327 ms

next.png

next.png

326 ms

bg_content_side.png

bg_content_side.png

359 ms

bg_main_bottom.gif

bg_main_bottom.gif

364 ms

bg_main_1column.png

bg_main_1column.png

425 ms

bg_submenu_top.gif

bg_submenu_top.gif

464 ms

h2_home_title.png

h2_home_title.png

796 ms

megaphone.svg

megaphone.svg

464 ms

obj_home_plan_economy.svg

obj_home_plan_economy.svg

538 ms

obj_home_plan_lite.svg

obj_home_plan_lite.svg

542 ms

obj_home_plan_standard.svg

obj_home_plan_standard.svg

587 ms

obj_home_plan_ribbon.svg

obj_home_plan_ribbon.svg

646 ms

obj_home_plan_enterprise.svg

obj_home_plan_enterprise.svg

635 ms

btn_home_plan_function_detail.png

btn_home_plan_function_detail.png

1372 ms

btn_home_plan_price_detail.png

btn_home_plan_price_detail.png

1184 ms

bnr_lolipop_nextgen_201601.png

bnr_lolipop_nextgen_201601.png

1647 ms

h3_home_title.png

h3_home_title.png

1682 ms

obj_home_feature_wordpress.png

obj_home_feature_wordpress.png

1721 ms

line_dot_11.gif

line_dot_11.gif

1370 ms

obj_home_feature_backup.png

obj_home_feature_backup.png

1910 ms

obj_home_feature_utilization.png

obj_home_feature_utilization.png

1732 ms

obj_home_feature_support.png

obj_home_feature_support.png

1878 ms

h3_home_functions.png

h3_home_functions.png

2163 ms

obj_home_functions_list.png

obj_home_functions_list.png

2346 ms

btn_feature._function_detail.png

btn_feature._function_detail.png

2372 ms

btn_infomation_more.png

btn_infomation_more.png

2194 ms

line_dot_02.gif

line_dot_02.gif

2186 ms

badge_light.png

badge_light.png

147 ms

widgets.js

widgets.js

154 ms

icon_star.gif

icon_star.gif

2107 ms

btn_h_serch.png

btn_h_serch.png

2231 ms

line_dot_08.gif

line_dot_08.gif

2261 ms

33 ms

btn_pagetop.gif

btn_pagetop.gif

2222 ms

dc.js

dc.js

95 ms

obj_lolipop_logo.png

obj_lolipop_logo.png

2388 ms

obj_ojisan_normal.png

obj_ojisan_normal.png

2483 ms

obj_header_banner_text.png

obj_header_banner_text.png

2508 ms

126 ms

__utm.gif

__utm.gif

30 ms

__utm.gif

__utm.gif

12 ms

__utm.gif

__utm.gif

24 ms

__utm.gif

__utm.gif

31 ms

btn_header_order.png

btn_header_order.png

2692 ms

bg_header_simple.png

bg_header_simple.png

2995 ms

obj_ppb_by_logo.png

obj_ppb_by_logo.png

2643 ms

obj_order_count_text.png

obj_order_count_text.png

2726 ms

obj_numbers.png

obj_numbers.png

2729 ms

menu_btn.png

menu_btn.png

3007 ms

menu_dot.gif

menu_dot.gif

2677 ms

arrow_menu.gif

arrow_menu.gif

2649 ms

obj_logo_ppb.png

obj_logo_ppb.png

2735 ms

pixel

pixel

154 ms

pixel

pixel

65 ms

Pug

Pug

74 ms

sync.ad-stir.com

sync.ad-stir.com

623 ms

sync

sync

61 ms

sync

sync

1038 ms

is

is

1162 ms

headerstyle.min.css

headerstyle.min.css

165 ms

pixel

pixel

24 ms

google

google

152 ms

sd

sd

72 ms

tag.js

tag.js

89 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

29 ms

obj_prev_item_icon.png

obj_prev_item_icon.png

2121 ms

obj_next_item_icon.png

obj_next_item_icon.png

2135 ms

obj_dhw_ac_jp_thumb.jpg

obj_dhw_ac_jp_thumb.jpg

2321 ms

follow_button.6a78875565a912489e9aef879c881358.ja.html

follow_button.6a78875565a912489e9aef879c881358.ja.html

65 ms

tag

tag

39 ms

obj_mtblanc_jp_thumb.jpg

obj_mtblanc_jp_thumb.jpg

2308 ms

obj_foresthuntingone_com_thumb.jpg

obj_foresthuntingone_com_thumb.jpg

2359 ms

jot

jot

97 ms

obj_sakelife_jp_thumb.jpg

obj_sakelife_jp_thumb.jpg

2096 ms

lolipop.jp

lolipop.jp

1643 ms

lolipop.jp

lolipop.jp

2679 ms

lolipop.jp

lolipop.jp

2307 ms

lolipop.jp

lolipop.jp

1624 ms

lolipop.jp

lolipop.jp

1192 ms

nr-768.min.js

nr-768.min.js

76 ms

roundtrip.js

roundtrip.js

41 ms

btn.png

btn.png

30 ms

conversion_async.js

conversion_async.js

55 ms

51 ms

logo201601.png

logo201601.png

46 ms

open_footer.png

open_footer.png

82 ms

close_footer.png

close_footer.png

116 ms

63 ms

conversion.js

conversion.js

850 ms

15936ac739

15936ac739

124 ms

QGNG2UAG2ZAKJNSEXUXBMN.js

QGNG2UAG2ZAKJNSEXUXBMN.js

127 ms

39 ms

out

out

12 ms

tr

tr

49 ms

out

out

7 ms

out

out

14 ms

out

out

42 ms

out

out

42 ms

out

out

42 ms

out

out

41 ms

out

out

40 ms

out

out

41 ms

u.php

u.php

80 ms

sync

sync

31 ms

19 ms

sd

sd

42 ms

sd

sd

51 ms

in

in

10 ms

tap.php

tap.php

34 ms

377928.gif

377928.gif

12 ms

conversion.js

conversion.js

1500 ms

in

in

5 ms

SEO Factors

moo.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 Moo.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 Moo.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

moo.jp

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